Someone asked for an example, here is one I've often seen when doing a
release upgrade on many webservers I administer: Apache will fail to
start. I don't recall if that currently causes Apache postinst to fail,
but if not, it really ought to continue.
Apache has a complicated config, and upst
On Sat, Sep 22, 2018 at 09:50:11AM +0200, Wouter Verhelst wrote:
> Nobody is arguing that if the init system or policy-rc.d block service
> starts, that then postinst should silently not start the daemon.
That should read:
Nobody is arguing that if the init system or policy-rc.d block service
st
Hi Tollef,
On Fri, Sep 21, 2018 at 09:53:13PM +0200, Tollef Fog Heen wrote:
> ]] Wouter Verhelst
>
> > On Tue, Sep 18, 2018 at 10:04:26PM +0200, Tollef Fog Heen wrote:
>
> [...]
>
> > > The API provided by a package being in the configured state is not
> > > whether the relevant daemon is runn
On Fri, Sep 21, 2018 at 10:07:31PM +0200, Tollef Fog Heen wrote:
> ]] Ian Jackson
>
> > Tollef Fog Heen writes ("Bug#904558: What should happen when maintscripts
> > fail to restart a service"):
>
> [...]
>
> > > This means that failure to start a daemon should generally not cause the
> > > p
4 matches
Mail list logo
