Your message dated Sat, 9 Sep 2017 11:40:42 +0200
with message-id <[email protected]>
and subject line Re: Bug#855209: systemd ignores configuration for getty when
switching and autostarting a new vt
has caused the Debian Bug report #855209,
regarding systemd ignores configuration for getty when switching and
autostarting a new vt
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.)
--
855209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855209
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 232-18
Severity: normal
Dear Maintainer,
I want to have logs on tty6, rather than a login shell.
I created a file called /etc/systemd/system/[email protected]
What happens is that if I press ctrl+alt+f6, I get a login shell.
However, if after that I give
# service getty@tty6 stop
# service getty@tty6 start
and then switch again to tty6 with ctrl+alt+f6, then I will see
the wanted tail of logs.
I tried with daemon-reload, but the issue remains present, when switching
to a vt that doesn't exist, systemd always uses the generic [email protected]
file, ignoring the instance specific configuration.
Attaching my .service file
Best
-- Package-specific info:
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to it_IT.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages systemd depends on:
ii adduser 3.115
ii libacl1 2.2.52-3
ii libapparmor1 2.11.0-2
ii libaudit1 1:2.6.7-1
ii libblkid1 2.29.1-1
ii libc6 2.24-9
ii libcap2 1:2.25-1
ii libcryptsetup4 2:1.7.3-3
ii libgcrypt20 1.7.6-1
ii libgpg-error0 1.26-2
ii libidn11 1.33-1
ii libip4tc0 1.6.0+snapshot20161117-5
ii libkmod2 23-2
ii liblz4-1 0.0~r131-2
ii liblzma5 5.2.2-1.2
ii libmount1 2.29.1-1
ii libpam0g 1.1.8-3.5
ii libseccomp2 2.3.1-2.1
ii libselinux1 2.6-3
ii libsystemd0 232-18
ii mount 2.29.1-1
ii util-linux 2.29.1-1
Versions of packages systemd recommends:
ii dbus 1.10.14-1
ii libpam-systemd 232-18
Versions of packages systemd suggests:
ii policykit-1 0.105-17
pn systemd-container <none>
pn systemd-ui <none>
Versions of packages systemd is related to:
pn dracut <none>
ii initramfs-tools 0.127
ii udev 232-18
-- no debconf information
# This file is part of systemd.
#
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
[Unit]
Description=tty logger on %I
After=systemd-user-sessions.service plymouth-quit-wait.service
After=rc-local.service
# If additional gettys are spawned during boot then we should make
# sure that this is synchronized before getty.target, even though
# getty.target didn't actually pull it in.
Before=getty.target
IgnoreOnIsolate=yes
# IgnoreOnIsolate causes issues with sulogin, if someone isolates
# rescue.target or starts rescue.service from multi-user.target or
# graphical.target.
Conflicts=rescue.service
Before=rescue.service
# On systems without virtual consoles, don't start any getty. Note
# that serial gettys are covered by [email protected], not this
# unit.
ConditionPathExists=/dev/tty0
[Service]
Type=simple
ExecStart=/bin/journalctl -f
StandardOutput=tty
UtmpIdentifier=%I
TTYPath=/dev/%I
TTYReset=no
TTYVHangup=no
TTYVTDisallocate=no
KillMode=process
IgnoreSIGPIPE=no
SendSIGHUP=no
# Unset locale for the console getty since the console has problems
# displaying some internationalized messages.
Environment=LANG= LANGUAGE= LC_CTYPE= LC_NUMERIC= LC_TIME= LC_COLLATE=
LC_MONETARY= LC_MESSAGES= LC_PAPER= LC_NAME= LC_ADDRESS= LC_TELEPHONE=
LC_MEASUREMENT= LC_IDENTIFICATION=
[Install]
WantedBy=getty.target
DefaultInstance=tty6
--- End Message ---
--- Begin Message ---
On Wed, 15 Feb 2017 12:49:25 -0300 Felipe Sateler <[email protected]>
wrote:
> On Wed, Feb 15, 2017 at 11:28 AM, Salvo Tomaselli <[email protected]> wrote:
> > Package: systemd
> > Version: 232-18
> > Severity: normal
> >
> > Dear Maintainer,
> > I want to have logs on tty6, rather than a login shell.
> >
> > I created a file called /etc/systemd/system/[email protected]
> >
> > What happens is that if I press ctrl+alt+f6, I get a login shell.
> >
> > However, if after that I give
> >
> > # service getty@tty6 stop
> > # service getty@tty6 start
> >
> > and then switch again to tty6 with ctrl+alt+f6, then I will see
> > the wanted tail of logs.
>
> I think the problem is that logind actually tries to start
> autovt@tty6. Thus the chain is:
>
> autovt@tty6
> => resolved as instance of autovt@
> => resolved as alias of getty@
>
> The whole alias thing is very weird , as aliasing depends on load
> orer. There is discussion upstream of better handling but not fixed
> yet.
>
> In the meantime, you should be able to fix the issue via `ln -s
> [email protected] /etc/systemd/system/[email protected]`
It's fine to name the unit
/etc/systemd/system/[email protected]
but then make sure to start it manually as you did. If you want to have
it started on boot, you can symlink it into
/etc/systemd/system/getty.target.wants
If you want to have it autostarted by logind, use the name suggested by
Felipe.
As I don't see at bug here I'm hereby closing this report.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
