I had famd init script displayng [!!] at shutdown/reboot or on "/etc/init.d/famd stop". I found that the reason why famd couldn't get stopped, was that it never really got started during boot: although it said "[ok]" on the boot screen and the init-script told it was started, looking at processes with "ps -A" soon after logging-in showed no "famd" process running, and that was why gnome's nautilus didn't "auto-refresh" file-lists. I modified famd's init script (/etc/init.d/famd), removing "--background" from the line that originally stated... [code]start-stop-daemon --start --quiet --exec /usr/sbin/famd --background \[/code] ...and this worked for me. However, I don't know why... :) ... : "--background" is a start-stop-daemon's option to force to background those programs which don't have this option of their own; although famd doesn't seem to need to be called with the "--background" option (since it goes background by default, unless you start it with "-f" option), "--background" could be "redundant", not fatal; *and* when famd gets called *manually* (ie after logging-in) via start-stop-daemon *with* the "--background" option, it starts no problem. The "--background" option seems to "break it" only when the init script is called automatically during boot... don't know why. Reproducible: Always Steps to Reproduce: 1."rc-update add famd default" 2.reboot 3.try "ps -A|grep famd" and "/etc/init.d/famd stop" Actual Results: I got no output from "ps -A|grep famd" :) and "/etc/init.d/famd stop" gave "[!!]" Expected Results: "ps -A|grep famd" should have returned something like "5650 ? 00:00:00 famd" and "/etc/init.d/famd stop" should have said it was all [Ok] :)
*** Bug 64030 has been marked as a duplicate of this bug. ***
looks like there's some merit in this suggestion, there's no need for --background since famd does switch into the background unlike the old fam.
I also have the same problem. I tried removing the --background and that seemed to stop my famd from dying. I noticed it dies when I access nfs shares from a remote machine otherwise. -- I only did some minor tests, so I dont know if removing --background really prevents it -- definitely doesnt hurt though. This seems quite a blocker really. Everytime famd dies, I get flooded with "famd[10233]: connect: Connection refused" in /var/log/messages and its just a pain in the ass :)
removed --background from the init script, think it was a left-over from older times.
famd died after this afternoon again :( -- I guess this is unrelated, but any pointers of how to track issue would be nice.
