Petter Reinholdtsen [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
For one thing because there is no such thing as an omitpid feature
in killall5. Only pidof has it.
Hm.
I just tested it, and it worked for me. How are you testing it? I
changed init.d/klogd stop location to be after
Petter Reinholdtsen [EMAIL PROTECTED] writes:
[Goswin von Brederlow]
we use fuse-unionfs for /etc and /usr on a pool of systems. When
rebooting killall5 will kill all processes execpt init and itself
causing the fuse filesystems to be killed without umount. In our
case the next access to
[Goswin von Brederlow]
For one thing because there is no such thing as an omitpid feature
in killall5. Only pidof has it.
Hm.
I just tested it, and it worked for me. How are you testing it? I
changed init.d/klogd stop location to be after sendsigs and made sure
klogd made a symlink to the
[Goswin von Brederlow]
we use fuse-unionfs for /etc and /usr on a pool of systems. When
rebooting killall5 will kill all processes execpt init and itself
causing the fuse filesystems to be killed without umount. In our
case the next access to /etc or /usr will block because there will
be no
Package: sysvinit-utils
Version: 2.86.ds1-56
Severity: wishlist
Tags: patch
Hi,
we use fuse-unionfs for /etc and /usr on a pool of systems. When
rebooting killall5 will kill all processes execpt init and itself
causing the fuse filesystems to be killed without umount. In our case
the next access
5 matches
Mail list logo
