[systemd-devel] Nspawn / getty restart loop

[Meech]

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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20141206/caff7313/attachment.html>