On 01/11/14 19:21, Martinx - ジェームズ wrote:
After a week of tests, I realized that `systemd-journal` is not ready for prime time. A lot of times, it consumes 100% of CPU, making the system almost unusable. Debian Jessie should not activate `systemd-journal` by default (for logging), even when with systemd = PID1.
Excellent. What's the reproducible method of causing this outcome, and which Debian (or upstream) bug number is associated with your findings?