On Fri, 13.12.13 16:34, Gao feng ([email protected]) wrote: > >> As we know, systemd only forks getty on ttyX when we press ctrl + alt + FX. > >> I whould like to let systemd forks server gettys on all of tty deivces by > >> default. > >> this is very useful in container environment, since we can't use > >> ctrl+alt+FX > >> to trigger getty in container. > > > > ...do containers even have such devices? > > > > pts device ;)
This will not work. Unlike VT ttys which exist continously and perpetuously on a system ptys only exist when an application allocates them, like for example xterm or ssh. However, for them its xterm's or ssh's job to spawn a shall as backend. > > Anyway, just enable more instances of [email protected] for all devices you > > need, just like [email protected] is started by default. > > > > The autostart that you mention is part of logind and all it does is just > > start the same services via systemd, no magic. > > > > [email protected] under /etc/systemd/system/getty.target.wants/ is linked to > /usr/lib/systemd/system/[email protected], > so I create [email protected] which links to > /usr/lib/systemd/system/[email protected] too. is this right? > > In libvirt lxc, the ttyX actually is pts devices. > > [root@localhost getty.target.wants]# ll > total 0 > lrwxrwxrwx 1 root root 38 Dec 13 02:49 [email protected] -> > /usr/lib/systemd/system/[email protected] > lrwxrwxrwx 1 root root 38 Dec 13 03:22 [email protected] -> > /usr/lib/systemd/system/[email protected] > > seems like in my container, agetty listens on /dev/console, not tty1 or tty2 > /sbin/agetty --noclear --keep-baud console 115200 38400 9600 > > it seems getty-generator does the extra job. /dev/tty1, /dev/tty2, ... make no sense in containers as there is no virtual console. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
