On Tue, 19 Dec 2017 07:25:46 -0500 Tom Horsley wrote:
> On Tue, 19 Dec 2017 20:16:51 +0800
>> FWIW, are you aware that you shouldn't make changes to
>> /usr/lib/systemd/system/* files? These can be overwritten up
>> updates.
Yes yes, but we are debugging.
>> If you want to make changes you should created a file with the same
>> name in /etc/systemd/system.
There is now (at least since F21) a better way. search for drop-in in
the man of systemd.unit, see below.
> And when you do that, and they utterly redesign the original
> service file, you spend weeks trying to figure out why the
> service no longer works at all because you forgot you made
> the copy :-).
Except if you look at the output of "systemctl cat X.service"
that shows clearly what you did. Example:
# /usr/lib/systemd/system/X.service
...
# /etc/systemd/system/X.service.d/Y.conf
Environment="OPTIONS=..."
This is far better and easier to maintain than patching
/etc/sysconfig/X config files that are protected against updates by
RPM.
--
Francis
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
