[systemd-devel] getty : how to run getty on every ttyX

[Gao feng]

Hello Mantas,

On 12/13/2013 04:17 PM, Mantas Mikulėnas wrote:
> 
> On Dec 13, 2013 10:09 AM, "Gao feng" <gaofeng at cn.fujitsu.com <mailto:gaofeng at cn.fujitsu.com>> wrote:
>>
>> Hi,
>>
>> 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 ;)

> Anyway, just enable more instances of getty at .service for all devices you need, just like getty at tty1.service 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.
> 

getty at tty1.service under /etc/systemd/system/getty.target.wants/ is linked to /usr/lib/systemd/system/getty at .service,
so I create getty at tty2.service which links to /usr/lib/systemd/system/getty at .service too. is this right?

In libvirt lxc, the ttyX actually is pts devices.

[root at localhost getty.target.wants]# ll
total 0
lrwxrwxrwx 1 root root 38 Dec 13 02:49 getty at tty1.service -> /usr/lib/systemd/system/getty at .service
lrwxrwxrwx 1 root root 38 Dec 13 03:22 getty at tty2.service -> /usr/lib/systemd/system/getty at .service

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.