On 2020-02-25, The Natural Philosopher wrote:

> On 25/02/2020 15:56, Adam Funk wrote:
>> On 2020-02-25, Joe Beanfish wrote:
>>
>>> On Tue, 25 Feb 2020 09:40:16 +0000, Adam Funk wrote:
>>>
>>>> On 2020-02-24, Richard Kettlewell wrote:
>>>>
>>>>> Adam Funk  writes:
>>>>>> On 2020-02-24, Richard Kettlewell wrote:
>>>>>>> Adam Funk  writes:
>>>>>>>> On 2020-02-20, Richard Kettlewell wrote:
>>>>>>>>> You stopped reading too early:
>>>>>>>> ...
>>>>>>>>> Start with ‘man systemd.timer’ for the syntax & meaning of the
>>>>>>>>> timer file, and look for ‘Overriding vendor settings’ in ‘man
>>>>>>>>> systemd.unit’
>>>>>>>>> for how to modify its behavior.
>>>>>>>>
>>>>>>>> Thanks --- I think I'm getting closer, but not successful yet.  I
>>>>>>>> found a symlink from
>>>>>>>> /etc/systemd/system/timers.target.wants/anacron.timer to
>>>>>>>> /lib/systemd/system/anacron.timer, deleted it, copied the linked
>>>>>>>> file
>>>>>>>                                       ^^^^^^^^^^
>>>>>>>
>>>>>>> I have no idea why you would do that.
>>>>>>
>>>>>> Some stuff in the documentation led to believe that customized files
>>>>>> should go straight in etc --- should I restore the symlink and edit
>>>>>> the file in /lib/systemd/...?
>>>>>
>>>>> The symlinks needs to still be there but point to the new file.
>>>>
>>>> So restore the symlinnk from
>>>> /etc/systemd/system/timers.target.wants/anacron.timer to
>>>> /lib/systemd/system/anacron.timer & edit the latter (regular) file?
>>>>
>>>> (It just seems weird to me to edit something in /lib rather than in
>>>> /etc!)
>>>>
>>>> Thanks.
>>>
>>> The "files" in etc are just symlinks to the files in lib. Systemd
>>> creates/deletes the links when you do systemctl enable/disable.
>>> Similar to how traditional init used init.d and rc* directories.
>>> You can edit in either place to the same effect, as long as you
>>> don't break the link.
>>>
>>> One thing about editing those files tho. Chances are your changes
>>> will get overwritten if/when you update the system package
>>> containing them. So document what you did so you can do it again.
>>
>> I'm used to the upgrade process (on Debian-based systems) warning me
>> that a config file has changed upstream & giving me the options: keep
>> my own file (with a copy of the new upstream file beside it, so I can
>> deal with it later); install the new file (and rename my own file, so
>> I can deal with it later); or show the diff & repeat the options.
>>
>> Are you telling me systemd is going to break that?
>>
>>
> its broken everything else...

To be fair, this is the first problem I've had with it.  In principle,
I like the idea of proper config files rather than enormous shells
scripts; but I'd prefer it if this followed the easier way fail2ban &
some other things work, where you copy /etc/foo.conf to /etc/foo.local
or foo.conf.local & delete everything except what you want to change.


--
"It is the role of librarians to keep government running in difficult
times," replied Dramoren.  "Librarians are the last line of defence
against chaos."                                       (McMullen 2001)

--- SoupGate-Win32 v1.05