Comment 8 for bug 1696970

I see more chatter about journald aborting upstream and on the mailing lists. Imho, just because journald was not scheduled to run kind of means that maybe it has too low of a priority, or the system is overloaded. It does not show that journald is actually at fault here, and/or failing. Imho, one shouldn't be killing journald, when it is otherwise obviously operating fine (aka waiting to be run).

I'm concerned as to why there is a watchdog on journald now. It should be rocksolid, and either work or crash, there is no need to crash it on a fixed schedule just because.