On 03/12/2015 03:21 PM, Felix Miata wrote:
If you're more interested in making problem go away than finding out why the problem, you could do what I've been doing for over a year, switching from on-demand gettys to always ready gettys:
# /bin/bash cd /etc/systemd/system/getty.target.wants cp -a ../../../../usr/lib/systemd/system/getty@.service ../../../../usr/lib/systemd/system/getty@tty1.service sed -i 's/TTYVTDisallocate=yes/TTYVTDisallocate=no/' ../../../../usr/lib/systemd/system/getty@tty1.service ln -sf ../../../../usr/lib/systemd/system/getty@tty1.service ./getty@tty1.service systemctl start getty@tty1.service
Er-um.. I have that. That's what I've beet talking about lrwxrwxrwx 1 root root 38 Nov 6 2013 /etc/systemd/system/getty.target.wants/getty@tty1.service -> /usr/lib/systemd/system/getty@.service # systemctl status getty@tty1.service getty@tty1.service - Getty on tty1 Loaded: loaded (/usr/lib/systemd/system/getty@.service; enabled) Drop-In: /usr/lib/systemd/system/getty@tty1.service.d âânoclear.conf Active: active (running) since Mon 2015-03-09 09:53:23 EDT; 3 days ago Docs: man:agetty(8) man:systemd-getty-generator(8) http://0pointer.de/blog/projects/serial-console.html Main PID: 1692 (login) CGroup: /system.slice/system-getty.slice/getty@tty1.service ⣠1692 login -- root Similar for tty2 and so on. Switching between 1&2 or 1&12 (where the log goes to, not 10) is rapid by comparison.
I do think latency issues generally have grown more widespread since a release or three back, maybe around the time the last vestiges of sysvinit began being purged.
Within 13.1? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org