Gregory's Server|
5 comments
 @c0dec0dec0de @luis_in_brief @ariadne auto-reload only makes sense if every possible change you could do touches a single file only. That might be fine for trivial services. But for anything even remotely more complex than hello world you might need to edit two config files, a service file or two, and you really don't want anything to load the cfg while you are just half-way done. Explicit configuration reload is a *good* thing, it allows you to schedule application of multiple changes as one  @pid_eins @c0dec0dec0de @luis_in_brief @ariadne Not only that, I also reflexively save multiple times while editing config files, often with them in unworkable intermediate states.  @dalias @pid_eins good points, I wasn’t wholly serious, but these are valid arguments.  @luis_in_brief @ariadne @pid_eins If you think argumenting against systemd is argumenting for hacky shell scripts (like debian still does *today*), you really should look at what the alternatives look like and where they are going (more and more declarative in the case of openrc).
|
@luis_in_brief 😭:but I have to run systemctl daemon-reload after I edit a config file for the changes to take effect.
Someone should make a systemd file watch package that automatically does it just for those particular nerds.
@ariadne @pid_eins