also sprach Petter Reinholdtsen [EMAIL PROTECTED] [2007.12.26.1724 +0100]:
Can you test this patch to see if it solve your problem?
I am having a hard time reproducing this; the only machine where
I still see the behaviour is the gateway in my parent's place, and
I can't work on that remotely.
I tested a bit, to see if there is a way to detect the runlevel when
the scripts in /etc/rcS.d/ is being executed, and the closest thing I
could find is the init argument as reported by ps.
It is 'init boot' while /etc/rcS.d/ is executed, and 'init [2]' etc
when a real runlevel is entered. The
[Martin F Krafft]
I can't help but think that a simple hack like
[...]
would solve the problem.
It would solve this problem, and might create a new one. With such
change, invoke-rc.d would no longer complain when invoked during the
shutdown sequence. I'm not sure about the impact of this
also sprach Petter Reinholdtsen [EMAIL PROTECTED] [2006.11.26.1755 +]:
It fetches the info from utmp. Perhaps that file have incorrect
information in it? I suspect runlevel 'S' isn't treated by init
as a real runlevel, and this make who and runlevel believe the
current runlevel is the
[Martin F Krafft]
first off, I have no idea why you're escaping the space,
Me neither. Probably historical reasons. :)
and second, unfortunately, the result is not always correct; as a
consequence, invoke-rc.d complains about being invoked during
shutdown during system startup, because I
Package: sysv-rc
Version: 2.86.ds1-33
Severity: normal
File: /usr/sbin/invoke-rc.d
invoke-rc.d determines the runlevel when invoked, using
/sbin/runlevel | sed 's/.*\ //'
first off, I have no idea why you're escaping the space, and second,
unfortunately, the result is not always correct; as a
6 matches
Mail list logo
