[Bug 804158] New: systemd: tty is always cleared after logout
https://bugzilla.novell.com/show_bug.cgi?id=804158 https://bugzilla.novell.com/show_bug.cgi?id=804158#c0 Summary: systemd: tty is always cleared after logout Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: fcrozat@suse.com ReportedBy: jengelh@inai.de QAContact: qa-bugs@suse.de Found By: Beta-Customer Blocker: --- ttys are always cleared after logout, despite --noclear: ExecStart=-/sbin/agetty --noclear %I 38400 linux The culprit is: TTYVTDisallocate=yes Removing this line brings back the well-known behavior of not clearing the tty. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c1
Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c2
--- Comment #2 from Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c3
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c4
--- Comment #4 from Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c5
--- Comment #5 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c6
--- Comment #6 from Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c7
--- Comment #7 from Jan Engelhardt
There is no reason to modify getty@.service for implementing tty1 to get --no-clear, please don't touch this file. I prefer we stay as close as possible to upstream (even if people insist on getting --no-clear on tty1)
getty@.service is modified to match the pre-systemd behavior for tty*, which was not to deallocate the VT. (Because once deallocated, /dev/vcs* no longer what was on it) getty@tty1.service is then subsequently added to implement the pre-systemd tty1 semantics.
Don't replace macros (%makeinstall) which are doing what is expected to do.
They don't do the same on all distros, which is why %makeinstall is a bad idea. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c8
--- Comment #8 from Frederic Crozat
There is no reason to modify getty@.service for implementing tty1 to get --no-clear, please don't touch this file. I prefer we stay as close as possible to upstream (even if people insist on getting --no-clear on tty1)
getty@.service is modified to match the pre-systemd behavior for tty*, which was not to deallocate the VT. (Because once deallocated, /dev/vcs* no longer what was on it)
Except systemd expects on VT deallocation to flushback scrollbuffers (see 6ea832a20700f5282c08c70f38422c6ab290a0b5 ).
getty@tty1.service is then subsequently added to implement the pre-systemd tty1 semantics.
Don't replace macros (%makeinstall) which are doing what is expected to do.
They don't do the same on all distros, which is why %makeinstall is a bad idea.
I'm packaging systemd for openSUSE where this macro has a define value. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c9
Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c10
--- Comment #10 from Jan Engelhardt
Except systemd expects on VT deallocation to flushback scrollbuffers
Reading through the bugzilla report, the way it looks is that Fedora wanted that behavior for its distro. systemd itself does not expect it (say, for finishing a log file or something). But ok. So how is the changeset supposed to look? We certainly need a getty@tty1.service, to remove TTYVTDisallocate. As for getty@.service, having both --noclear and TTYVTDisallocate is a confusion. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c11
--- Comment #11 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c
Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c12
--- Comment #12 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c13
Olaf Hering
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c14
--- Comment #14 from Jan Engelhardt
https://bugzilla.novell.com/show_bug.cgi?id=804158
https://bugzilla.novell.com/show_bug.cgi?id=804158#c15
--- Comment #15 from Olaf Hering
participants (1)
-
bugzilla_noreply@novell.com