Lennart Poettering <lenn...@poettering.net> schrieb: > [...] Finally, if something is logged > at priorities EMERG, ALERT or CRIT we will sync immediately (which > actually should never happen in real-life, unless something is really > broken -- a simple way to check if anything like this got written is > "journalctl -p crit"). [...] > Hmm, the only way I see that that would happen is if a lot of stuff is > logged at these super-high log levels mentioned above. But then again, > that never really should happen in real-life.
Unless you use those HP utilities: # journalctl -p crit -- Logs begin at Mo 2014-05-05 02:26:26 CEST, end at Di 2014-06-17 23:33:48 CEST. -- Mai 20 10:17:21 jupiter hp-systray[1366]: hp-systray[1366]: error: option -s not recognized -- Reboot -- Mai 22 22:37:15 jupiter hp-systray[1413]: hp-systray[1413]: error: option -s not recognized -- Reboot -- Jun 03 08:49:17 jupiter hp-systray[1501]: hp-systray[1501]: error: option -s not recognized -- Reboot -- Jun 09 13:45:31 jupiter hp-systray[1397]: hp-systray[1397]: error: option -s not recognized -- Reboot -- Jun 11 00:21:16 jupiter hp-systray[1405]: hp-systray[1405]: error: option -s not recognized -- Reboot -- Jun 14 00:30:49 jupiter hp-systray[1434]: hp-systray[1434]: error: option -s not recognized -- Reboot -- Jun 14 22:54:43 jupiter hp-systray[1416]: hp-systray[1416]: error: option -s not recognized -- Reboot -- Jun 14 23:11:11 jupiter hp-systray[1437]: hp-systray[1437]: error: option -s not recognized -- Reboot -- Jun 15 14:53:44 jupiter hp-systray[1447]: hp-systray[1447]: error: option -s not recognized -- Reboot -- Jun 15 16:53:39 jupiter hp-systray[1404]: hp-systray[1404]: error: option -s not recognized -- Reboot -- Jun 15 17:38:40 jupiter hp-systray[1397]: hp-systray[1397]: error: option -s not recognized -- Reboot -- Jun 15 18:34:37 jupiter hp-systray[1375]: hp-systray[1375]: error: option -s not recognized -- Reboot -- Jun 17 20:38:32 jupiter hp-systray[1406]: hp-systray[1406]: error: option -s not recognized > Could anyone who's expereiencing the slowdowns have a look on the > journalctl output menionted above? Do you have more than a few lines > printed like that? Nasty message but no slowdowns. But it's printed just during desktop session start so it's no problem. Still, I wonder what this utility tries to do (seems to put itself into autostart with an "-s" switch but without supporting it, probably a packaging and/or KDE issue). At least HP thinks: Oh boy - that's really critical! Whoohoo. Why not let the system explode? :~) -- Replies to list only preferred. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel