[Pkg-sysvinit-devel] sysv-rc: Multiple execution of /sbin/init ?
Michael
codejodler at gmx.ch
Fri Dec 4 12:02:56 UTC 2009
Thanks Petter for reply. Here's a new tarball with latest files, including /etc/inittab. But pls read on, maybe you can even spare to look at it.
I modified the tracker script a little bit so that it would work for any runlevel, and created a link
/etc/rcS.d/S60tracker (after mounts have settled, because the logfile is written to /tmp which is mounted on shm ramdisk here).
I had to name the logfiles differently now: (runlevel - command parameter)
RLS-start .... runlevel S tracker log
RL2-start .... runlevel 2 tracker log
RL2-rclocal .... runlevel 2, tracker execution via rc.local.
Questions:
- Why does the process env say it's sysvinit 2.86 when debian says it's 2.87 ?
- You said, Petter, that udev spans 1000 modprobe processes at boot; however, the 100 processes i catched were in rc2 not rcS. In rcS, you can see only 2.
- Is it possible that rc2 gets executed twice because there are 2 different init processes ?
btw, is it alright to have both 'sysvinit', and 'sysv-rc' installed ? There are dependencies, yes. I ask just in case each could trigger an own init process, under some circumstances...
To answer this quesation, let's look at rcS, then. (file: RLS-start)
Look at the full process list: You can see 'init boot' as first process with PID 1; and you can see it again with PID 453, way down.
At the end of that process list, you can also see that S60tracker gets started twice, with PID 1441 and 1443 !
Now at this point, a sidenote. I noticed these were pid 1271 and 1277 at the previous boot; also, the second init process had different pid (441). And i really wonder, why that's not always the same then. I mean, more than 150 additional processes in rcS (from 1271 to 1441) ?? What for ?
And another weirdness: In the rcS tracker log, only one run is logged .... ! Well ok i need to check if /tmp was already available in the first run. But it was S60, way after all mount scripts (and this is still the legacy boot)(but is it ??). It should work.
ok, anyway, two init processes. How is that possible ?
Latest logs and stuff attached.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2009-12-04.tar.bz2
Type: application/x-bzip
Size: 25886 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-sysvinit-devel/attachments/20091204/5f0c3510/attachment-0001.bin>
More information about the Pkg-sysvinit-devel
mailing list