Your message dated Sat, 01 Jan 2011 05:47:35 +
with message-id
and subject line Bug#582442: fixed in sysvinit 2.88dsf-13.1
has caused the Debian Bug report #582442,
regarding sysvinit: Failing to interrupt some script after upgrade
to be marked as done.
This means that you claim that the
On Tue, Dec 28, 2010 at 11:30:35AM -0200, Henrique de Moraes Holschuh wrote:
> On Wed, 15 Dec 2010, Tommy van Leeuwen wrote:
> > Is there any workaround available for this bug? We really need to be
> > able to interrupt the boot process.
>
> Yes, disable concurrent boot.
If I understand this issu
On Wed, 15 Dec 2010, Tommy van Leeuwen wrote:
> Is there any workaround available for this bug? We really need to be
> able to interrupt the boot process.
Yes, disable concurrent boot. It is what I have done on all my boxes and
set as policy for all servers at work. Right now, it is more trouble
Is there any workaround available for this bug? We really need to be
able to interrupt the boot process.
We have some daemons hanging if we don't have a network or dns server
available. So we want to interrupt those.
We tried trapping the signal, setting stty, but nothing really works.
Add me to
On Sun, 23 May 2010 00:36:20 -0300, Henrique de Moraes Holschuh wrote:
> > > I interrupt sometimes fsck (when I don't want to wait), now this
> > > doesn't work.
> > Wow. You are braver than me. I never considered that use case. :)
> It is quite common. Interrupting fsck if it is not in repair
5 matches
Mail list logo
