Am 05.03.2017 um 18:38 schrieb Jan Engelhardt:
On Sunday 2017-03-05 18:32, Stefan Seyfried wrote:
server:~ # time systemctl status ntpd.service Mär 05 09:16:49 server sntp[1645]: sntp 4.2.8p9@1.3265-o Mon Dec 19 17:18:19 UTC 2016 (1) [...] Mär 05 09:16:50 server start-ntpd[1622]: Starting network time protocol daemon (NTPD) Hint: Some lines were ellipsized, use -l to show in full.
real 0m3.199s user 0m0.009s sys 0m0.113s
This machine has journal on a bcache backed device, so it's not really rotating rust only.
In all fairness, grepping through 4 GB of syslog text logs would equally take as much time, I'd argue.
This is not the "journal non-persistent on a 4GB ramdisk" machine. server:~ # journalctl --disk-usage Archived and active journals take up 1.3G on disk. And in all fai The 4GB ramdisk journal machine greps very fast through 4rness, if systemctl goes through the whole stored journal data to find the last 10 lines of output, then I'd really question its benefits over plain old syslog ;-) Interesting though, that the 1.3GB of journal storage amount to only about one tenth of log message text: server:~ # journalctl -m | wc -c 150200227 So it seems that journal's efficiency is -- ahem -- suboptimal (I always thought it would be stored compressed and indexed for fast access, but it doesn't look like it is implemented like that). -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org