Your message dated Wed, 26 Dec 2007 22:27:25 +0100
with message-id <[EMAIL PROTECTED]>
and subject line sysvinit: init 2 no longer works right in SUM
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Version: 2.86.ds1-37
> 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.
This bug was fixed in version 2.86.ds1-37. This was the fix:
* Replace 66_init_emerg_tty patch with one only creating a new
session group when sulogin is called directly from init, and not
as part of the runlevel start scripts, to avoid leaving the single
user shell behind when switching runlevel. Updated patch from Samuel
Thibault. (Closes:406587)
Happy hacking,
--
Petter Reinholdtsen
--- End Message ---
