Package: sysvinit Version: 2.86.ds1-20 Severity: normal I got used to the fact that "init 2" in single user mode properly trnasitioned to multi-user. No more: now it doesn't kill the shell from which it was started, apparently. I actually get the shell _and_ a new getty running on the same tty. Imagine the chaos.
I know that there is a well documented procedure to do what I want (exit the shell), but habits die hard. I don't see why the shell is immune to the sending of SIGTERMs? One funny thing about the machine is that root shell is bash-static. I haven't tried to undo that yet, but I might if you can't reproduce this and you ask politely. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-9custom1 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages sysvinit depends on: ii initscripts 2.86.ds1-20 Scripts for initializing and shutt ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libselinux1 1.30.28-2 SELinux shared libraries ii libsepol1 1.12.26-2 Security Enhanced Linux policy lib ii sysv-rc 2.86.ds1-20 System-V-like runlevel change mech sysvinit recommends no packages. -- no debconf information _______________________________________________ Pkg-sysvinit-devel mailing list Pkg-sysvinit-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-sysvinit-devel
