▲ | ac29 4 hours ago | ||||||||||||||||
> just developing their own workaround that requires users to learn another unnecessary custom way to edit a plain text file. There's no need to use systemctl edit to make or edit an override file, its just a convenience shortcut | |||||||||||||||||
▲ | wtallis 3 hours ago | parent [-] | ||||||||||||||||
> There's no need to use systemctl edit to make or edit an override file, its just a convenience shortcut Do you think anyone who's reached this point in the thread has missed out on that? Yes, obviously those steps can be done manually. But that's not what's being recommended here, and it's more steps to learn and remember, and it doesn't really matter whether accomplishing this task requires one extra command or several when it either shouldn't need to be done at all, or should work the same for any config file that needs to be protected, not just systemd service definitions. It's almost like one of the systemd developers looked at visudo and forgot that sudo should probably never be used as an example of the right way to do things. | |||||||||||||||||
|