Not a "bloated, monolithic system"? [LWN.net]

Not a "bloated, monolithic system"?

Posted Feb 1, 2019 14:14 UTC (Fri) by zblaxell (subscriber, #26385)
In reply to: Not a "bloated, monolithic system"? by Cyberax
Parent article: Systemd as tragedy

> It was not restarted.

Not the bug I was looking for, but a bug nonetheless.

to post comments

Not a "bloated, monolithic system"?

Posted Feb 1, 2019 20:15 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (3 responses)

> Not the bug I was looking for, but a bug nonetheless.
Uhm, why? A service that can't be SIGKILL-ed is clearly not safe to be restarted.

Not a "bloated, monolithic system"?

Posted Feb 1, 2019 22:11 UTC (Fri) by zblaxell (subscriber, #26385) [Link] (2 responses)

>A service that can't be SIGKILL-ed is clearly not safe to be restarted.

Look up the page a little: long-running processes that take a long time to exit after SIGKILL, but eventually get there. You want to restart them, but only after they exit, and there's a big time gap between KILL and exit.

Not a "bloated, monolithic system"?

Posted Feb 1, 2019 23:23 UTC (Fri) by Cyberax (✭ supporter ✭, #52523) [Link] (1 responses)

Then create a separate service responsible for the restart. Activate it on initial service's failure.

Duh.

Not a "bloated, monolithic system"?

Posted Feb 9, 2019 22:38 UTC (Sat) by nix (subscriber, #2304) [Link]

I'm sorry, but could you possibly be a little more contemptuous? It's not unpleasant enough to read this comment thread yet.