On Fri, 24 Jul 2009, Petter Reinholdtsen wrote:
> I guess we could extend init/runlevel to track this information.
> Would have to extend /dev/initctl protocol and make runlevel suid
> root, I guess. Do init know about the previous runlevel? If not, it
> would have to be extended to have this inf
[Petter Reinholdtsen]
> I believe runlevel uses /var/run/*tmp, and guess its content is bogus.
> Any idea what could mess up the utmp/wtmp files?
It is calling setutent()/getutent() to find the runlevel information,
and this reads /var/run/utmp to get the current status. No idea what
could mess u
On Mon, 16 Feb 2009, Petter Reinholdtsen wrote:
> [Martin F Krafft]
> > /sbin/runlevel is obviously confused, while /sbin/init seems to know
> > precisely what the runlevel is:
>
> I believe runlevel uses /var/run/*tmp, and guess its content is bogus.
> Any idea what could mess up the utmp/wtmp fi
[Martin F Krafft]
> /sbin/runlevel is obviously confused, while /sbin/init seems to know
> precisely what the runlevel is:
I believe runlevel uses /var/run/*tmp, and guess its content is bogus.
Any idea what could mess up the utmp/wtmp files?
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUB
Package: sysvinit
Version: 2.86.ds1-61
Severity: important
File: /sbin/runlevel
/sbin/runlevel is obviously confused, while /sbin/init seems to know
precisely what the runlevel is:
piper:/var/run# strace -fo /tmp/runlevel.strace /sbin/runlevel
unknown
piper:/var/run# ps -fp1
UIDPI
5 matches
Mail list logo
