Bug#824779: container getty-static.service causes lxcfs high cpu usage
Michael Biebl
biebl at debian.org
Wed Jul 20 17:55:34 BST 2016
Am 20.07.2016 um 17:37 schrieb Wang Jian:
> # diff -u /lib/systemd/system/getty at .service /etc/systemd/system/getty at .service
> --- /lib/systemd/system/getty at .service 2016-04-25 17:32:15.000000000 +0800
> +++ /etc/systemd/system/getty at .service 2015-05-17 20:28:50.253964583 +0800
> @@ -21,7 +21,7 @@
> # On systems without virtual consoles, don't start any getty. Note
> # that serial gettys are covered by serial-getty at .service, not this
> # unit.
> -ConditionPathExists=/dev/tty0
> +# ConditionPathExists=/dev/tty0
>
> [Service]
> # the VT is cleared by TTYVTDisallocate
>
> # cat /lib/systemd/system/getty-static.service
> [Unit]
> Description=getty on tty2-tty6 if dbus and logind are not available
> ConditionPathExists=/dev/tty2
> ConditionPathExists=!/lib/systemd/system/dbus.service
>
> [Service]
> Type=oneshot
> ExecStart=/bin/systemctl --no-block start getty at tty2.service
> getty at tty3.service getty at tty4.service getty at tty5.service
> getty at tty6.service
> RemainAfterExit=true
As I expected, getty at .service was overridden but getty-static.service
was not. This is strictly a misconfiguration error, maybe a local one or
one created by lxc-create. But not by the systemd package itself.
That said, we now changed the check in getty-static.service to use
ConditionPathExists=/dev/tty0
I.e. we do not event attempt to start it if no working VC subsystem is
available.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160720/c39c17db/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list