/etc/conf.d/net or /etc/conf.d/net.*

[Element Dave]

I've created separate net.{var} files in /etc/conf.d to correspond to the net.{var} symlinks in /etc/init.d. For example, /etc/conf.d/{{eth,bridge,bond}n}. Putting everything in "net" won't work for my purpose, because I'd be applying conflicting configurations to interfaces, or affected interfaces I want left alone.

Networking behaves closer to how I'd like with separate interface configuration files, but I'd really appreciate it if someone in the know would let me know whether per-interface configuration files are "officially" supported/recommended, or a temporary compatibility hack. I'd prefer to avoid future breakage. I can't find any proper documentation -- not a word (I discount the "example" files) -- which is very discouraging for such a critical service. I may just use my own networking scripts for now. Thanks in advance.

[NeddySeagoon]

Element Dave,

You should put everything in /etc/conf.d/net.

I would be interested to understand why this won't work for you and what you think is missing from /usr/share/doc/openrc-<version>/net.example.bz2
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.