In addition to /etc/rc.conf.local you can also place smaller
configuration files for each rc(8) script in the /etc/rc.conf.d directory
or <dir>/rc.conf.d directories specified in local_startup, which will be
included by the load_rc_config function.
$ grep local_startup /etc/defaults/rc.conf
local_startup="/usr/local/etc/rc.d" # startup script dirs.
Never tried it but it might work if you name the file /etc/rc.conf.d/netif as it's the/etc/rc.conf.d/net
netif
'service' that sets the IP addresses. As far as I know the rc.conf.d file needs to be named the same as the service it applies to.For a given service foo, it is possible to have a per-ser-
vice configuration file in /etc/rc.conf.d/foo, which is
read after /etc/rc.conf.
Ah, so knowledge of each rc.d scripts is required for fine-grained configuration, then.Never tried it but it might work if you name the file /etc/rc.conf.d/netif as it's thenetif
'service' that sets the IP addresses. As far as I know the rc.conf.d file needs to be named the same as the service it applies to.
For jail configurations you could use the file /etc/rc.conf.d/jail to store jail-specific configuration options.
jail
" here means "For /etc/rc.d/jail".You are right, thank you.Never tried it but it might work if you name the file /etc/rc.conf.d/netif as it's thenetif
'service' that sets the IP addresses. As far as I know the rc.conf.d file needs to be named the same as the service it applies to.
They contain good information in any case. Even if you don't use rc.conf.dso knowledge of each rc.d scripts is required for fine-grained configuration