| |||||||||||||
Poettering: systemd for Administrators, Part VIIIPoettering: systemd for Administrators, Part VIIIPosted Apr 21, 2011 18:04 UTC (Thu) by marcH (subscriber, #57642)In reply to: Poettering: systemd for Administrators, Part VIII by jimparis Parent article: Poettering: systemd for Administrators, Part VIII
> I'm a huge fan of .d directories.
I'm only a fan of "foo.d/*.sh" (or "foo.d/*.conf",...) lists.
A number of .d implementations (used to?) try to source absolutely everything in the .d/ directory. They miserably and sometimes mysteriously fail on .orig and *~ backup files, *,v histories, RCS/ subdirectories, etc. etc.
(Log in to post comments)
Poettering: systemd for Administrators, Part VIII Posted Apr 21, 2011 21:28 UTC (Thu) by djf_jeff (subscriber, #62173) [Link]
I am with you on this.
I have hit this bug more than once but that was long ago. Things seems to have been fixed since then and require a special extension to be included.
I personally like this way of changing the configuration because it's quick to see how the system differ from the stock configuration.
|
|||||||||||||