Re:Etckeeper lets you store changes in /etc to git
by ibotty on Monday April 29, 2013 @03:21AM
(#5624550)
inotify consumes resources (ram), which a hook into a package manager does not. you cannot watch all subdirectories within /etc with one handle, so you will have to recursively setup handles for all subdirectories. then, you might run into the max_user_watches limit (see sysctl fs.inotify.max_user_watches).
Re:Etckeeper lets you store changes in /etc to git
by tankenmate on Monday April 29, 2013 @05:28AM
(#5624983)
Acutally, using fanotify() you can watch a whole filesystem with one watcher; use FAN_MARK_MOUNT (inotify and fanotify both use the fsnotify subsystem in the kernel). So then you set a watch on either /etc (if it is separately mounted) or watch / and then ignore any paths that aren't in /etc.
Re:Etckeeper lets you store changes in /etc to git
by NickNameNick on Sunday April 28, 2013 @11:38PM
(#5623945)
Wouldn't that commit as soon as any file was changed, no matter who or what changed it, denying users the ability to supply a meaningful commit message?
Re:Etckeeper lets you store changes in /etc to git
by jared314 on Sunday April 28, 2013 @11:58PM
(#5623990)
That depends on the filesystem events you tie into (Open, Close, Write, Delete, etc) and what your responding script does. But, at the point where you want to put the entire system under some kind of change management, why not use something designed for that, like NixOS[0]?
[0] http://linux.die.net/man/1/inotifywait