[systemd-devel] Nspawn / getty restart loop

[Florian Koch]

the container-getty at .service only needs to be present, not enabled,
you can disable the unit, then the logs go away

2014-12-06 15:49 GMT+01:00 Meech <meechman at gmail.com>:
> Running Arch64 / Systemd 217.   I have a barebones container initialized
> with pacstrap.   The conatiner is stored in /var/lib and started via systemd
> (systemctl start systemd-nspawn at mycontainer)
>
> When nobody is logged in, the journal is spammed every 10 seconds with
> agetty errors.   How can I prevent this?   It seems like it's in a never
> ending restart loop until somebody is logged in.
>
>
> Dec 06 00:13:53 vpn agetty[1582]: /dev/pts/0: No such file or directory
> Dec 06 00:14:03 vpn systemd[1]: container-getty at 0.service has no holdoff
> time, scheduling restart.
> Dec 06 00:14:03 vpn systemd[1]: Stopping Container Getty on /dev/pts/0...
> Dec 06 00:14:03 vpn systemd[1]: Starting Container Getty on /dev/pts/0...
> Dec 06 00:14:03 vpn systemd[1]: Started Container Getty on /dev/pts/0.
> Dec 06 00:14:03 vpn agetty[1583]: /dev/pts/0: No such file or directory
> Dec 06 00:14:13 vpn systemd[1]: container-getty at 0.service has no holdoff
> time, scheduling restart.
> Dec 06 00:14:13 vpn systemd[1]: Stopping Container Getty on /dev/pts/0...
> Dec 06 00:14:13 vpn systemd[1]: Starting Container Getty on /dev/pts/0...
> Dec 06 00:14:13 vpn systemd[1]: Started Container Getty on /dev/pts/0.
>
> Thanks.
>
> _______________________________________________
> systemd-devel mailing list
> systemd-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
>