Summary: | systemd-journal consumes 100% cpu (lxc-container with getty.target) | ||
---|---|---|---|
Product: | systemd | Reporter: | Urs Helmig <urs> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED NOTABUG | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | ARM | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Urs Helmig
2014-06-13 20:34:35 UTC
You are creating a log loop, journald reads kmsg, logs that to console, you loop that back to kmsg. YOu really should believe mounting /dev/console to kmsg was a good idea. THey are very different devices, /dev/kmsg isn't even a tty. Similar for /dev/tty1, you cannot just mount any pts there, since the VT api means you have a number of files in /sys/class/tty that match it, it means that you also have /dev/vcsa1, it means you can send a special set of ansi sequences to it, and it means that you can issue some special ioctls on it. Nothing of that is provided by simply mounting a pseudo tty on top, and logind will not work if you ignore that. Also see: http://www.freedesktop.org/wiki/Software/systemd/ContainerInterface/ |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.