Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

3
  • 3
    This is the kind of concise and direct answer I would expect to find; more useful to me than a copy-paste from the manual. Commented Aug 11, 2024 at 1:25
  • 2
    You should NEVER change files in /lib/systemd/system! That path is reserved for package installed units systemctl edit creates local overrides in /etc/systemd/system/servicename.override.d/servicename: /etc is where machine/admin conf should go! If you are not overriding partly, you can pass --full to edit, and it will create the file /etc/systemd/system/servicename, that masks the one in lib. If you are changing files in /lib you are asking to be burnt anyway, as package update will silently overwrite your changes anyway, and decent postinstalls reloads the systemd daemon... Commented May 10 at 22:09
  • 1
    If you are arguing that you are editing non-package-installed unit files, then what in the hell those files are doing in /lib. Use /usr/local/lib/systemd for ones installed from other-than-repo sources (or built locally) FHS has its merits, alhough most distributions doesn't respect it as they should, and much less the admins... Commented May 10 at 22:14