On Thu, 29 Mar 2018 21:31:16 +0000, bob prohaska wrote:

> To my surprise, I looked in /usr/local/etc and found it empty. Thank you
> for the warning!
>
And another point:

There is one special case for configuration files: its getting more
common for utility programs with configurations that are often heavily
modified to have a master configuration file that holds the main
configuration statements and then references a directory which is where
you are expected to put site-specific tweaks instead of editing the
master config file.

The iconic example is /etc/profile, which configures the bash shell.
You'll probably never need to modify /etc/profile because after its
contents have been applied it looks in /etc/profile.d and also applies
the contents of all the config files in that directory. In the case of
bash, this means setting up environment variables that affect the screen
display and modify the behavior of common commandline utilities, e.g.
less and tidy.

Its a common pattern: the linked directory is in the same place as the
configuration file and shares the same name but with a '.d' suffix. The
names of files in the linked directory generally don't matter unless the
order they are applied in is important - if this is the case their names
usually start with two digits.


--
Martin    | martin at
Gregorie  | gregorie dot org

--- SoupGate-Win32 v1.05