dhcpcd-discuss

Re: Suggestions: configuration file flexibility

Langlois, Maxime

Mon Apr 15 17:13:52 2019

>  From dhcpcd(8)
> 
>       -f, --config file
>               Specify a config to load instead of
> /etc/dhcpcd.conf.  dhcpcd
>               always processes the config file before any command
> line 
> options.

My bad here, seems I was looking at an old man page... :(


> > Another great addition would be allowing modular configuration. In
> > other terms, allow splitting the configuration in separate files
> > under
> > a common directory (i.e. /etc/dhcpcd.d/*.conf). Keeping dhcpcd.conf
> > for
> > daemon's specific and common configuration and adding an optional
> > setting for specifying a path for additional configs. This would
> > allow
> > separation of daemon's specific and common configuration from
> > interface's specific configuration. One could even split each
> > interface's configuation in its own file.
> Not sure much gain would be had here unless you had many interfaces
> or profiles.
> I would imagine that your gain would be to have a smaller per device 
> modification of some king?

I would see the separation of daemon's configuration from interface's
configuration something that would be nice anyway. Since probably most
people only need to deal with interfaces configuration, this would hide
the "under the hood" settings from most and would make cleaner config
files.
But yes, with a quite complex network configuration with multiple
interfaces to manage, which is my situation, it certainly would help
simplify the management (exposing & modifying) of the network
interfaces settings.

Thanks,
Maxime

**********************************************************************
DISCLAIMER:
Privileged and/or Confidential information may be contained in this message. If you are not the addressee of this message, you may not copy, use or deliver this message to anyone. In such event, you should destroy the message and kindly notify the sender by reply e-mail. It is understood that opinions or conclusions that do not relate to the official business of the company are neither given nor endorsed by the company. Thank You.

References:
static routers not exposed in hooksLanglois, Maxime
Re: static routers not exposed in hooksRoy Marples
Suggestions: configuration file flexibilityLanglois, Maxime
Re: Suggestions: configuration file flexibilityRoy Marples
Archive administrator: postmaster@marples.name