Hi! Earlier today, I did a »apt-get dist-upgrade«, including sysvinit 2.88dsf-38, which I found hanging at the configuration stage after unpacking, due to »pidof /sbin/init« hanging. I killed the latter and package configuration resumed:
sysvinit: creating /run/initctl
sysvinit: restarting...init: timeout opening/writing control channel
/run/initctl
.init: timeout opening/writing control channel /run/initctl
.init: timeout opening/writing control channel /run/initctl
.init: timeout opening/writing control channel /run/initctl
.init: timeout opening/writing control channel /run/initctl
.init: timeout opening/writing control channel /run/initctl
.init: timeout opening/writing control channel /run/initctl
.init: timeout opening/writing control channel /run/initctl
failed.
[other packages following]
What happened at the same time:
PID UID PPID PGrp Sess TH Vmem RSS %CPU User System Args
3323 0 1 3323 3323 2 147M 1.63M 0.0 0:00.01 0:00.01
/bin/bash /etc/hurd/runsystem.gnu
3326 0 3323 3323 3323 2 147M 1.59M 0.0 0:00.00 0:00.00
/bin/bash /etc/hurd/rc autoboot
3327 0 3 1 1 4 130M 972K 0.0 0:00.00 0:00.01
/hurd/fifo
3332 0 3326 3323 3323 2 146M 916K 0.0 0:00.01 0:00.00
/sbin/fsck -p -A
3776 0 3332 3323 3323 2 137M 6.67M 4.6 0:03.74 0:01.28
fsck.ext2 -p /dev/hd2s2
This of course is not so good in a live system (with hd2s2 mounted) -- I
think we don't have proper locking of used device nodes yet. I killed
that fsck process, early enough before it could do any harm, as it seems.
No idea if that all has just been a peculiarity of my system, though.
Grüße,
Thomas
pgp5eraF4x4ja.pgp
Description: PGP signature
