On Tue, Mar 18, 2008 at 04:21:55AM +0100, Michael Biebl wrote: > You could summarise it like: > Either optimise for minimal downtime or maximum safety. > > Your preference seems to be the former, mine the latter.
no, your straw-man dichotomy is nothing like what i have been saying. your preference guarantees maximum downtime and maximum data loss. mine (i.e. the correct behaviour, restart in postinst) minimises both. i've experienced and reported ACTUAL data loss from the current upgrade behaviour of rsyslog. a couple of hours worth of syslog data from several machines gone - never logged to disk because rsyslog was down during the upgrade, and the upgrade was waiting for me to answer a question about another package's config files. data that would NOT have been lost if rsyslog had done the right thing and stayed up until it was restarted in the postinst. you've posited a far-fetched HYPOTHETICAL scenario where rsyslog MAY lose data due to some unexplained circumstances and some hand-waving about incompatible data files (which rsyslog doesn't even have). possibly confusing it to the point that it crashes practice trumps theory, and reality trumps imagination. craig -- craig sanders <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
