Summary: | journalctl -b -<boot#>: very slow startup on slow filesystems, large journals | ||
---|---|---|---|
Product: | systemd | Reporter: | Alain Kalker <a.c.kalker> |
Component: | general | Assignee: | systemd-bugs |
Status: | RESOLVED FIXED | QA Contact: | systemd-bugs |
Severity: | normal | ||
Priority: | medium | CC: | a.c.kalker, david, radek |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Alain Kalker
2013-12-11 15:57:37 UTC
Update: after suffering a graphics driver issue on my main desktop, I noticed that: $ journalctl -b -1 took almost 40(!) seconds to begin displaying log entries. (As may be obvious, this machine has rebooted lots of times, and the journal dir takes up quite a lot of disk space.) If journalctl is to seriously take on the competition of logrotated syslog, then IMHO fixing this delay should be high priority. In some cases (the proverbial printer being on fire, but in particular CPUs overheating in a server rack, etc), quick access to the logs is very important. same issue, systemd-215 Does this patch help? http://lists.freedesktop.org/archives/systemd-devel/2015-April/030050.html Jan Janssen's patches that improve this have been merged now. Hence closing. |
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.