Hey,
On 17/05/2011 Christoph Anton Mitterer wrote:
> On Mon, 16 May 2011 22:35:12 -0300, Henrique de Moraes Holschuh
> wrote:
> > Then, 'stop' tries to close all managed crypto devices and aborts *with
> > an error* if it cannot. 'Start' tries to open all managed crypto
> > devices, and aborts *
On Mon, 16 May 2011 22:25:45 -0300, Henrique de Moraes Holschuh
wrote:
> Because the initscript returned status 0 when there were still
> cryptsetup-managed dm-crypt devices active? If it does that, it is
> broken.
AFAIU just this happens right now.
> Because the package allowed itself to be un
On Tue, 17 May 2011, Christoph Anton Mitterer wrote:
> > For that reason, the situation that initscripts are
> > still around but the daemon/application they start/stop/whatever isn't,
> > is quite common. And it would be absurd if initscripts would exit wit $?
> > != 0 in that case.
> Here the pr
Christoph Anton Mitterer
writes:
> Phew I guess there are already some requests against the policy open,..
> both for this config-file-weirdness and for adhering to the (not so
> unreasonable) LSB exit codes.
> I've followed this some time and most arguments against these changes
> seemed (at le
On Tue, 2011-05-17 at 00:24 +0200, Jonas Meurer wrote:
> I think that one is the trouble spot. Christoph doesn't agree with the
> way, Debian manages initscripts. They're handled as conffiles by dpkg,
> and for that reason aren't removed at 'apt-get remove', only if the
> package is purged.
Yes I d
5 matches
Mail list logo
