You are not logged in.
Pages: 1
FAM can get installed as a dependency of some package, and if user doesn't know about it, he can never figure out why file alteration monitoring doesn't work (as FAM isn't in daemons array).
Since gamin is superior and doesn't require daemon, it should be used as a dependency, and FAM should be dropped.
Last edited by Mad Fish (2011-06-11 13:15:20)
Offline
This topic comes up fairly regularly here. I can't remember why, but so far the devs have always said no.
Offline
We figure the user is not stupid so can figure out how to use daemons or make the choice to use gamin as necessary...
Offline
We figure the user is not stupid so can figure out how to use daemons or make the choice to use gamin as necessary...
User may just not notice this (that's exactly what happened to my friend). And what's the point of having choice when choice is obvious? ![]()
Offline
Mad Fish, if you come across specific packages that use FAM, and you are certain that they can use Gamin instead without losing functionality or introduce other problems, you can open a bug report for them on Flyspray for consideration.
ᶘ ᵒᴥᵒᶅ
Offline
If fam gets dropped, we should just drop it, not replace it. Inotify has been around for years now and the only reason why you would use fam is because it can do remote file monitoring on NFS. Replacing it with an inotify->fam wrapper like gamin is will not bring that functionality back, so there's no reason to use fam if the implementation is just an inotify wrapper.
Offline
Does FAM not also play well with Postfix and Courier IMAP or can Gamin replace this too?
Last edited by jack.mitchell (2011-06-13 08:22:41)
Offline
Pages: 1