On Sat, 06.12.14 09:49, Meech (meech...@gmail.com) wrote:
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@mycontainer)
When nobody is logged in, the journal
On Sun, 07.12.14 09:20, Meech (meech...@gmail.com) wrote:
Disabling seems to have no effect, it's a static service:
console-getty.service disabled
container-getty@.service static
getty@.service enabled
serial-getty@.service
I created a fresh container by following the steps here
https://wiki.archlinux.org/index.php/Arch_systemd_container using the
command
pacstrap -i -c -d ~/MyContainer base
Not sure what is pulling it in. Nor how to find out.
If I start it via systemd, the journal is quiet until I log in (via
On Mon, 08.12.14 09:29, Meech (meech...@gmail.com) wrote:
I created a fresh container by following the steps here
https://wiki.archlinux.org/index.php/Arch_systemd_container using the
command
pacstrap -i -c -d ~/MyContainer base
Not sure what is pulling it in. Nor how to find out.
If
Disabling seems to have no effect, it's a static service:
console-getty.service disabled
container-getty@.service static
getty@.service enabled
serial-getty@.service disabled
However, I think adding this to
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@mycontainer)
When nobody is logged in, the journal is spammed every 10 seconds with
agetty errors. How can I
the container-getty@.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 meech...@gmail.com:
Running Arch64 / Systemd 217. I have a barebones container initialized
with pacstrap. The conatiner is stored in /var/lib
