Petter Reinholdtsen wrote: > [Michael Biebl] >> Isn't this problematic (at least for start), as rsyslogd is in /usr >> (because it uses libz)? > > Yes. You are right. For starting, it should depend on $remote_fs as > long as it need a mounted /usr/. I did not think of that. But to > make sure it can start before /usr/ is mounted and after it is > umounted, I would recommend moving it to /(s)bin/. >
Hi Petter, I was thinking more about this bug report. Even if rsyslog is installed into /usr, it should be able to stop it later during shutdown, currently it is stopped at K90. 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? How could I achieve that with insserv (stopping after sendsigs right befor umountfs.sh)? Should rsyslog ever move to /sbin, we can still move it even later in the shutdown process to S39 (right before S40umountfs) Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature