Craig Sanders wrote: > On Sun, Mar 16, 2008 at 01:16:22AM +0100, Michael Biebl wrote:
> >>>> 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. >>> name one daemon where that's a case. >> I already gave you one. > > no, you didn't. you made an assertion without any evidence, not even a > single example. Again: Imo a service should be stopped by the init script which was written for this specific version, because the maintainer can only test it for this version. The alternative would be, that the maintainer tests the upgrade path from any previous version and adds a lot of special casing to the maintainer script (which *will* lead to errors, believe me). Second, if you replace files while the daemon is still running, this can lead to all sorts of subtle failures, e.g. daemons that dynamically load functionality via shared modules (as rsyslog does) might crash. 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
