On Montag, 6. März 2017 13:20:57 CET Michal Suchánek wrote:
On Mon, 27 Feb 2017 19:52:28 +0100
Perhaps it is the systemd mechanism by which services in /usrsomething can be superseded by placing the same service file under /etcsomething. Erasing those files on /etc would revert to factory settings, no?
And it also allows the admin to replicate the changes easily on another machine, and to do updates without local modifications being erased.
That also means updates without service updates being applied.
Because you copy the *WHOLE* service, make changes, and any updates to the service are lost on update.
Sane services are configurable so you put a file in /etc/ that configures the service and do not change the service itself unless you need to fix some error in the service definition.
But nobody writes systemd services that accept configuration so you have to fix the service definition to be configurable and only then you can configure it /o\
Why are the systemd haters always claiming stuff without once reading the man pages? man systemd.unit: EXAMPLES ... Example 2. Overriding vendor settings [...] Suppose there is a vendor-supplied unit /usr/lib/systemd/system/ httpd.service with the following contents: [...] The first possibility is to copy the unit file to /etc/systemd/system/httpd.service and change the chosen settings: [...] Alternatively, the administrator could create a drop-in file /etc/systemd/system/httpd.service.d/local.conf with the following contents: [...] Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org