is there a better solution than "killall -9 journalctl"?
adamwill at fedoraproject.org
Mon Jul 14 18:04:14 UTC 2014
On Mon, 2014-07-14 at 13:27 -0400, Robert P. J. Day wrote:
> > When one of these journalctl processes is running, 'systemctl status
> > (pid of that process)' may tell you what service is spawning it. --
> i'll set aside some time this evening to look at this, but i just
> want to confirm that i'm not the only person seeing this -- that is,
> i have a quad core i7 with hyperthreading so i have 8 possible CPUs
> and, without messing with any kind of related configuration, i've seen
> this system with 7 journalctl processes running, each one pegged at
> 98-99% CPU. and that's more than enough to have the fans on this thing
> running full blast to keep it from melting down. :-(
> and doing a "systemctl restart abrtd" didn't appear to solve the
> problem. more this evening after some testing ...
I asked at the meeting this morning, and nirik said he'd seen it but
only once, could not reproduce it any more. The rest of us aren't seeing
it (or at least haven't *noticed* it).
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
More information about the test