> Damn! I admit I haven't had any trouble with autofs crashing or being killed
> randomly, but I always hate it when I have to reboot a machine (or close
> enough: kill all the processes using some of the submounts) just because
> I somehow killed the automounter. And even tho as I said I haven't seen autofs
> die, you can't dismiss the possibility.
> Also, not being able to kill autofs without nasty side effects means that you
> cannot upgrade autofs without those nasty side effects.
> Being able to kill/restart daemons seems very important to me. AutoFS is no
> exception here. I have no idea how hard it might be to provide such a feature,
> and I'm not going to code it up any time soon, so I'll just stop whining.
Yes ! In my oppinion it is very important to have an ability to kill
every daemon. I remember in earlier Kernel-Versions ive used a timeout
for my cdrom of 5 seconds. Some processes are using my cdrom and
sometimes it happens that the cdrom keeps being locked. I dont know why
this happened, and i couldnt reproduce it. Maybe it is fixed. Unmounting
doesnt work cause unmount believes the path is being used ("busy"), but
fuser outputs no users. Restarting of the daemon fails. The daemon was
killed but could not be started again, cause the system believes the
directory is mounted by the old daemon. The only way get my cdrom out,
is rebooting the system ;). And i really hate rebooting my system. And i
would have been really happy if a were able to start a new daemon taking
over the control of the old one.
Percy
