Your message dated Sun, 11 May 2014 18:52:50 +0200
with message-id <[email protected]>
and subject line Re: Bug#747742: systemd does not honour /etc/inittab
has caused the Debian Bug report #747742,
regarding systemd does not honour /etc/inittab
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
747742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747742
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 204-10
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Dear Maintainer,
I do not need a whole bunch of tty's so I disabled all but one in runlevel 5
and enabled only 3 in my text-only runlevels 3 and 2 (excerpt from
/etc/inittab):
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
#4:23:respawn:/sbin/getty 38400 tty4
#5:23:respawn:/sbin/getty 38400 tty5
#6:23:respawn:/sbin/getty 38400 tty6
But when I use systemd and are e.g in runlevel 5 I can go to tty2, 3, ... and
will get tty's. Even when I am in runlevel 3, used e.g. 3 tty's and then
switch to runlevel 5, there are still 3 tty's open and not only just one tty,
tty1 as it is described by /etc/inittab.
With best regards,
Julian Wollrath
- -- Package-specific info:
- -- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.15.0-rc5 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-1
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53
ii libacl1 2.2.52-1
ii libaudit1 1:2.3.6-1
ii libc6 2.18-5
ii libcap2 1:2.22-1.2
ii libcap2-bin 1:2.22-1.2
ii libcryptsetup4 2:1.6.4-4
ii libdbus-1-3 1.8.2-1
ii libgcrypt11 1.5.3-4
ii libkmod2 17-2
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-3
ii libselinux1 2.2.2-2
ii libsystemd-daemon0 204-10
ii libsystemd-journal0 204-10
ii libsystemd-login0 204-10
ii libudev1 204-10
ii libwrap0 7.6.q-25
ii sysv-rc 2.88dsf-53
ii udev 204-10
ii util-linux 2.20.1-5.7
Versions of packages systemd recommends:
pn libpam-systemd <none>
Versions of packages systemd suggests:
pn systemd-ui <none>
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBCAAGBQJTb4DwAAoJEFl2dmpRMS8z5aQH/0bXfL484MdlTqJOw4bKmt8V
0T0fiFZwIjVowWxybnXoTaVhuy6fc4VxMviP+RN7bMox18/Qiuwb1CENg8/g+nr2
RGvIwwvoKSHVlY3VtGem6Glj9+5jIesCAwbSGF2I7zr1b5kmkNbWh1CSnGMnGbfR
1/IA2CwOYe3y/5rBKk4VJmkxy2xG64gk/AEamF6YOZh6+cKGici31/eVTQgfLem9
NX4crN8cC28CNuxTrJE4A0fMOdCTVLAE5CL56GKWuu2KyKBXDCHSDIJp5hlf5vOi
+D9rVJ81jyPFitK3kTrjaHP8e6LSMo80tdRpvGo4Wh/8IxvWLDTNEB+KeONHUow=
=Hoed
-----END PGP SIGNATURE-----
[OVERRIDDEN] /etc/systemd/system/sockets.target.wants →
/lib/systemd/system/sockets.target.wants
Only in /etc/systemd/system/sockets.target.wants: acpid.socket
Only in /etc/systemd/system/sockets.target.wants: cups.socket
Only in /lib/systemd/system/sockets.target.wants: dbus.socket
Only in /etc/systemd/system/sockets.target.wants: lvm2-lvmetad.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-initctl.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-journald.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-shutdownd.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-udevd-control.socket
Only in /lib/systemd/system/sockets.target.wants: systemd-udevd-kernel.socket
[OVERRIDDEN] /etc/systemd/system/multi-user.target.wants →
/lib/systemd/system/multi-user.target.wants
Only in /etc/systemd/system/multi-user.target.wants: cups.path
Only in /lib/systemd/system/multi-user.target.wants: dbus.service
Only in /lib/systemd/system/multi-user.target.wants: getty.target
Only in /etc/systemd/system/multi-user.target.wants: remote-fs.target
Only in /etc/systemd/system/multi-user.target.wants: rsyslog.service
Only in /etc/systemd/system/multi-user.target.wants: ssh.service
Only in /lib/systemd/system/multi-user.target.wants:
systemd-ask-password-wall.path
Only in /lib/systemd/system/multi-user.target.wants: systemd-logind.service
Only in /lib/systemd/system/multi-user.target.wants:
systemd-user-sessions.service
[OVERRIDDEN] /etc/systemd/system/local-fs.target.wants →
/lib/systemd/system/local-fs.target.wants
Only in /etc/systemd/system/local-fs.target.wants: lvm2-activation-early.service
Only in /etc/systemd/system/local-fs.target.wants: lvm2-activation.service
Only in /lib/systemd/system/local-fs.target.wants: run-lock.mount
Only in /lib/systemd/system/local-fs.target.wants: run-user.mount
Only in /lib/systemd/system/local-fs.target.wants: systemd-fsck-root.service
Only in /lib/systemd/system/local-fs.target.wants: systemd-remount-fs.service
3 overridden configuration files found.
==> /var/lib/systemd/deb-systemd-helper-enabled/rsyslog.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
/etc/systemd/system/multi-user.target.wants/rsyslog.service
/etc/systemd/system/syslog.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/rsyslog.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/ssh.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/multi-user.target.wants/cups.path
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/syslog.service <==
==>
/var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation.service.dsh-also <==
/etc/systemd/system/local-fs.target.wants/lvm2-activation.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/local-fs.target.wants/lvm2-activation-early.service
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/lvm2-activation-early.service.dsh-also
<==
/etc/systemd/system/local-fs.target.wants/lvm2-activation-early.service
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/ssh.socket
==> /var/lib/systemd/deb-systemd-helper-enabled/ssh.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/ssh.service
/etc/systemd/system/sshd.service
==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-lvmetad.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/lvm2-lvmetad.socket
==>
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/lvm2-lvmetad.socket
<==
==>
/var/lib/systemd/deb-systemd-helper-enabled/sockets.target.wants/cups.socket <==
==> /var/lib/systemd/deb-systemd-helper-enabled/cups.service.dsh-also <==
/etc/systemd/system/sockets.target.wants/cups.socket
/etc/systemd/system/multi-user.target.wants/cups.path
/etc/systemd/system/printer.target.wants/cups.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/printer.target.wants/cups.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/cups.path.dsh-also <==
/etc/systemd/system/multi-user.target.wants/cups.path
==> /var/lib/systemd/deb-systemd-helper-enabled/cups.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/cups.socket
==> /var/lib/systemd/deb-systemd-helper-enabled/bluetooth.service.dsh-also <==
/etc/systemd/system/bluetooth.target.wants/bluetooth.service
/etc/systemd/system/dbus-org.bluez.service
==>
/var/lib/systemd/deb-systemd-helper-enabled/bluetooth.target.wants/bluetooth.service
<==
==> /var/lib/systemd/deb-systemd-helper-enabled/dbus-org.bluez.service <==
==> /var/lib/systemd/deb-systemd-helper-enabled/sshd.service <==
--- End Message ---
--- Begin Message ---
]] Julian Wollrath
> I do not need a whole bunch of tty's so I disabled all but one in runlevel 5
> and enabled only 3 in my text-only runlevels 3 and 2 (excerpt from
> /etc/inittab):
/etc/inittab is only used by sysvinit, so you're correct, systemd
doesn't use that. It's by design and not going to change.
systemd also spawns getty as needed on ttys, so you shouldn't need to do
the explicit management of getty as you've done in the past.
--
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
