> and/or failing. Imho, one shouldn't be killing journald, when it is otherwise obviously
> operating fine (aka waiting to be run).
@xnox: How do you tell if there is no live lock and it is operating fine despite it timed out on a 3 minute timer?
> 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.
If we drop the watchdog we won't get any new journal entries if it enters/tricked into an infinite loop. I don't think that would be wise.
> and/or failing. Imho, one shouldn't be killing journald, when it is otherwise obviously
> operating fine (aka waiting to be run).
@xnox: How do you tell if there is no live lock and it is operating fine despite it timed out on a 3 minute timer?
> 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.
If we drop the watchdog we won't get any new journal entries if it enters/tricked into an infinite loop. I don't think that would be wise.
There are upstream bugs with too little information for similar issues: /github. com/systemd/ systemd/ issues/ 2899 /github. com/systemd/ systemd/ issues/ 2924
https:/
https:/
@xnox Do you have links with enough info for debugging?