5 ms·

I've always preferred daemontools and runit's ideology here. If a service dies, wait one second, then try starting it. Do this forever. The last thing I ne

I've always preferred daemontools and runit's ideology here. If a service dies, wait one second, then try starting it. Do this forever. The last thing I need is emergent behavior out of my service manager.

freedomben 3y ago
Systemd can do that exactly that. it just doesn't do that by default. But if that's what you want, it's trivial
- akira2501 3y ago
  Is it possible to do this system wide? Or do I have to do it for each individual service? It may be a trivial amount of work but if the configuration is fragile, I've gained nothing.
  - izacus 3y ago
    It's literally described in the article.
    - akira2501 3y ago
      They're literally rhetorical questions. So, yes, you can set /defaults/, but you can't /force/ the configuration globally. Which means you still need to examine every single configuration file to understand the behavior of your system as a whole. Hence.. why I called it a fragile mechanism.
      - MadnessASAP 3y ago
        It's trivial to grep all system service files for the relevant lines to see if they override the default. It is also easy to override that override to set it to whatever you like of so desired.
        akira2501 3y ago
        Then watch for changes. Or remember to do this on more than one system. Or work with a team of people all credentialed to make work related system level changes to the fleet. Yes, there are ways to deal with anything, but less is more, this is unix afterall. I can't love having a bunch of options, in several places, that may override each other, most of which I would never use for any practical reason anyways. Reminds me of the type of systems I abandoned in favor of linux.
      - tick_tock_tick 3y ago
        It takes a tenth of a second to run over every unit file in the system and change/set the restart policy.
      - lmz 3y ago
        It's funny how some people call systemd overcomplicated and here we have someone complaining because it only has two levels (default/specific) for config instead of three (default/specific/forced default).
        akira2501 3y ago
        You've got the argument wrong. I'm suggesting you don't need two, you only need one. Unconfigurable forced default.
        lmz 3y ago
        That would be a bit hard to swallow for a general purpose supervisor.
- rconti 3y ago
  ... and how many of us knew this before the article?
  - otterley 3y ago
    Anyone who read its documentation, which is comprehensive and clear.
    - marcosdumay 3y ago
      Comprehensive, yes.
    - freedomben 3y ago
      Indeed, if I hadn't written my own .service file then I probably wouldn't know, but when you write a service file I don't think it's unreasonable to expect that the writer looks up the possible settings to make sure they're configuring it optimally. It's fairly easy to find a list and (IMHO) the parameter names are very self-descriptive

freedomben 3y ago

Systemd can do that exactly that. it just doesn't do that by default. But if that's what you want, it's trivial

akira2501 3y ago
Is it possible to do this system wide? Or do I have to do it for each individual service? It may be a trivial amount of work but if the configuration is fragile, I've gained nothing.
- izacus 3y ago
  It's literally described in the article.
  - akira2501 3y ago
    They're literally rhetorical questions. So, yes, you can set /defaults/, but you can't /force/ the configuration globally. Which means you still need to examine every single configuration file to understand the behavior of your system as a whole. Hence.. why I called it a fragile mechanism.
    - MadnessASAP 3y ago
      It's trivial to grep all system service files for the relevant lines to see if they override the default. It is also easy to override that override to set it to whatever you like of so desired.
      - akira2501 3y ago
        Then watch for changes. Or remember to do this on more than one system. Or work with a team of people all credentialed to make work related system level changes to the fleet. Yes, there are ways to deal with anything, but less is more, this is unix afterall. I can't love having a bunch of options, in several places, that may override each other, most of which I would never use for any practical reason anyways. Reminds me of the type of systems I abandoned in favor of linux.
    - tick_tock_tick 3y ago
      It takes a tenth of a second to run over every unit file in the system and change/set the restart policy.
    - lmz 3y ago
      It's funny how some people call systemd overcomplicated and here we have someone complaining because it only has two levels (default/specific) for config instead of three (default/specific/forced default).
      - akira2501 3y ago
        You've got the argument wrong. I'm suggesting you don't need two, you only need one. Unconfigurable forced default.
        lmz 3y ago
        That would be a bit hard to swallow for a general purpose supervisor.
rconti 3y ago
... and how many of us knew this before the article?
- otterley 3y ago
  Anyone who read its documentation, which is comprehensive and clear.
  - marcosdumay 3y ago
    Comprehensive, yes.
  - freedomben 3y ago
    Indeed, if I hadn't written my own .service file then I probably wouldn't know, but when you write a service file I don't think it's unreasonable to expect that the writer looks up the possible settings to make sure they're configuring it optimally. It's fairly easy to find a list and (IMHO) the parameter names are very self-descriptive