severity 471051 normal thanks Craig Sanders wrote: > Package: rsyslog > Version: 2.0.3-1 > Severity: critical > Justification: causes serious data loss > > > rsyslog shuts down at the start of the upgrade and only gets restarted > when the package is configured. > > this is broken. instead of stopping rsyslog in the prerm and starting it
Well, this is standard behaviour on Debian: daemons are stopped before upgrade and started after the upgrade. With your reasoning, you'd have to file bug reports against all of them (say mysql, postgresql, you name it). One of the reasons, why it is done this way, ist that you can't guarantee a clean shutdown of the daemon, when you have replaced it's files, while it is still running. So stopping the old daemon in prerm and starting the new one in postinst, seems like the "more correct" solution to me. Example: The current rsyslog package uses a separate binary "rklogd" to log the kernel messages. This binary is started/stopped via /etc/init.d/rsyslog. The next major release of rsyslog will implement the kernel log functionality as loadable modules, so there is no more rklogd. That means, I have to stop rsyslog with the correct (i.e. old) init script, to cleanly shutdown rsyslogd and rklogd and start the new rsyslogd with the new init script. 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
