> Well, let's start with something. What about this patch, that reuses
> /etc/default/halt? I believe it is, maybe not most principal, but
> solution to bug at hand.
Looks good to me
--
Pierre Ynard
[2019-03-09 17:59] Pierre Ynard
>
> part text/plain1139
> > > My opinion is that /etc/init.d/reboot should honor NETDOWN, and
> > > source it from /etc/default/halt. And then NETDOWN should be
> > > documented in /etc/default/halt, as requested in #703844.
> >
> > Actually,
> > My opinion is that /etc/init.d/reboot should honor NETDOWN, and
> > source it from /etc/default/halt. And then NETDOWN should be
> > documented in /etc/default/halt, as requested in #703844.
>
> Actually, #696910 suggests that NETDOWN could also be disabled if
> iSCSI is detected.
Sorry for
tags 696910 patch
retitle 499796 initscripts: reboot called with -i hangs on iSCSI root
severity 499796 normal
merge 499796 696910
thanks
> My opinion is that /etc/init.d/reboot should honor NETDOWN, and source
> it from /etc/default/halt. And then NETDOWN should be documented in
>
> On other hand, introducing REBOOT_OPTS in /etc/default/reboot is easy.
> Do we want it? Or we want to introduce more restricted version, NETDOWN,
> like in /etc/default/halt. Or maybe we want to reuse /etc/default/halt
> for `reboot' script?
My opinion is that /etc/init.d/reboot should honor
[2011-04-14 09:46] "Bastian Blywis"
> The following problem happens reproducible in a network of 100 virtual
> machines and a network of 120 "real" machines that mount their rootfs
> over nfs.
>
> When /etc/init.d/reboot is run and "reboot -d -f -i" called, in about
> 2-4% of the cases, the
Hi,
Which can change wake-over-lan behaviour on various NICs, so it is not
something we can do lightly.
Wouldn't solution 2 be viable? You can leave the -i as default but everyone
who is experiencing problems can make persistent modifications.
Although documenting this is a damn good idea.
On Thu, 14 Apr 2011, Bastian Blywis wrote:
When /etc/init.d/reboot is run and reboot -d -f -i called, in about
2-4% of the cases, the system will deadlock because the network
interfaces are shut down but the kernel still wants to read/write
something on the nfs export. The message nfs server
Package: initscripts
Version: 2.88dsf-13.1
Severity: normal
The following problem happens reproducible in a network of 100 virtual
machines and a network of 120 real machines that mount their rootfs
over nfs.
When /etc/init.d/reboot is run and reboot -d -f -i called, in about
2-4% of the cases,
9 matches
Mail list logo
