Craig Sanders wrote:
> On Sun, Mar 16, 2008 at 03:14:58AM +0100, Michael Biebl wrote:
>
>> 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)
>>
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
On Tue, Mar 18, 2008 at 04:01:05AM +0100, Michael Biebl wrote:
> Craig Sanders wrote:
> > On Sun, Mar 16, 2008 at 03:14:58AM +0100, Michael Biebl wrote:
>
> > > Second, if you replace files while the daemon is still running,
> > > this can lead to all sorts of subtle failures, e.g. daemons that
>
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 preferen
On Sun, Mar 16, 2008 at 03:14:58AM +0100, Michael Biebl wrote:
> 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 repl
On Sun, Mar 16, 2008 at 03:00:49AM +0100, Michael Biebl wrote:
> Craig Sanders wrote:
> > On Sun, Mar 16, 2008 at 01:16:22AM +0100, Michael Biebl wrote:
>
> >
> >> grep "invoke-rc.d .* stop" *.prerm
> >
> > 1. the fact that some other packages have the same or similar broken
> > behaviour as you
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
Craig Sanders wrote:
> On Sun, Mar 16, 2008 at 01:16:22AM +0100, Michael Biebl wrote:
>
>> grep "invoke-rc.d .* stop" *.prerm
>
> 1. the fact that some other packages have the same or similar broken
> behaviour as yours does not excuse or justify your package being broken.
You are talking about
On Sun, Mar 16, 2008 at 01:16:22AM +0100, Michael Biebl wrote:
> Craig Sanders wrote:
> > severity 471051 critical
> > thanks
> >
> > this bug can not be downgraded to normal because it is a bug that
> > results in a loss of important and irreplacable data. that is one of the
> > defining characte
Craig Sanders wrote:
> severity 471051 critical
> thanks
>
> this bug can not be downgraded to normal because it is a bug that
> results in a loss of important and irreplacable data. that is one of the
> defining characteristics of a critical bug. loss of logging also has
> security implications,
severity 471051 critical
thanks
this bug can not be downgraded to normal because it is a bug that
results in a loss of important and irreplacable data. that is one of the
defining characteristics of a critical bug. loss of logging also has
security implications, which is also a critical issue.
On
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 s
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
in the postinst, just resta
13 matches
Mail list logo
