[Michael Biebl] > Even if rsyslog is installed into /usr, it should be able to stop it > later during shutdown, currently it is stopped at K90.
I suspect it need to stop before /usr/ is umounted, to avoid blocking umount of /usr/ if some libraries in /usr/lib/ is used, but as long as that is ok, it should be able to stop later. > Given that more and more services remove it's stop symlinks and are > thus killed by S20sendsigs, we don't get their shutdown messages. > > So I was thinking about moving the rsyslog stop symlink to > S30rsyslog, just before S40umountnfs.sh. > > What do you think about that? Do you see any problems with this? Not sure about the sequence numbers any more. I normally use dependency based boot sequencing. > How could I achieve that with insserv (stopping after sendsigs right > befor umountfs.sh)? To survive sendsigs, it need to add its pid to the list of pids to survive sendsigs, and to start just before umountfs, it should probably have stop dependency on $local_fs. But I suspect it should have stop dependency on umountnfs, to make sure it stops before /usr/ is umounted if /usr/ is on NFS. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
