Michael Biebl wrote: > The difference is, that a crashing daemon might lead to data corruption, > which is much worse than a slightly longer downtime. > > FWIW, if it is correct, that postfix behaves the way you describe, than > this is broken. > postfix can be combined with several other daemons (getting user data > from mysql, postgresql, virus scanning, spam scanning etc). > postfix itself can't control how those daemons are started. > If postfix is not stopped, before those are services are stopped, this > will lead to much worse results than a downtime which is a bit longer > (emails not getting virus-scanned, rejected emails because user data is > not available (db down),...). The only reasonable and safe choice is, to > stop postfix in prerm before those other services. >
You could summarise it like: Either optimise for minimal downtime or maximum safety. Your preference seems to be the former, mine the latter. 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
