Package: runit-run Version: 0.8.0 Severity: normal c.f. http://article.gmane.org/gmane.comp.sysutils.supervision.general/1193
I can confirm this; my Debian systems running 2.6.16 kernel images are
unaffected, while those running 2.6.17 exhibit this behavior:
$ ps -t tty1
PID TTY TIME CMD
1 tty1 00:00:00 runit
when logging in on getty-1, bash prints the following message:
-bash: no job control in this shell
and pressing Control-C on this terminal causes runit to halt the
machine.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages runit-run depends on:
ii runit 1.6.0-1 a UNIX init scheme with service su
ii sysv-rc 2.86.ds1-15 System-V-like runlevel change mech
Versions of packages runit-run recommends:
pn fgetty <none> (no description available)
-- no debconf information
--
Robert Edmonds
[EMAIL PROTECTED]
signature.asc
Description: Digital signature
