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
On Thu, 20 May 2010, Petter Reinholdtsen wrote:
> [Matthieu Castet]
> > 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 mode is
[Matthieu Castet]
>> Please remember that the messages seen on screen are not
>> in sync with the execution progresses of the jobs. Those
>> messages are buffered to avoid extremly mixed messages.
>
> Is that true for interactive process ?
Scripts flagged interactive run alone with direct connect
Hi,
Selon "Dr. Werner Fink" :
> On Fri, May 21, 2010 at 11:37:19AM +0200, Petter Reinholdtsen wrote:
> > Werner, any idea how startpar should handle ^c? This is the report in
> > http://bugs.debian.org/582442 >.
> >
> > > since last upgrade (makefile style migration ?) I got strange
> > > behavio
On Fri, May 21, 2010 at 11:37:19AM +0200, Petter Reinholdtsen wrote:
> Werner, any idea how startpar should handle ^c? This is the report in
> http://bugs.debian.org/582442 >.
>
> > since last upgrade (makefile style migration ?) I got strange
> > behaviour of the boot sequence.
> >
> > If I in
[Matthieu Castet]
> 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. :)
> Also on my system udev script hang at the end (until there is a
> timeout). I often hit ctrl+c to avoid waiting the timeout. T
Package: sysvinit
Version: 2.88dsf-5
Severity: normal
Tags: sid
Hi,
since last upgrade (makefile style migration ?) I got strange
behaviour of the boot sequence.
If I interupt some script with ctrl+c, the dependency are lost (not fs
mounted, no network, ...).
With the previous version this work
10 matches
Mail list logo
