but a call of /etc/init.d/iptables says the opposite. Reproducible: Always
Absolutely no clue what are you talking about. There's no reference to /etc/rc.conf in iptables init script.
Please look at <------------------ tfoerste@n22 ~ $ /etc/init.d/iptables Usage: iptables [ flags ] < options > Normal Options: start stop restart pause zap Default init.d options. Additional Options: save reload panic Extra options supported by this init.d script. Flags: --quiet Suppress output to stdout, except if: 1) It is a warning, then output to stdout 2) It is an error, then output to stderr --verbose Output extra information --debug Output debug information --nocolor Suppress the use of colors Configuration files: /etc/conf.d/iptables /etc/rc.conf <------------------ For more info, please run '/etc/init.d/iptables help'.
$ grep -Rni rc.conf /usr/portage/net-firewall/iptables/ $
I changed the topic of the bug report with respect to the culprit, b/c /etc/rc.conf seems no longer be the central configuration file sn't it ?
the purpose of the output is to show all files that are actually involved ... /etc/rc.conf, while not the main file, is involved and thus is listed should actually list *more* files ... like /etc/conf.d/rc and (if it exists), /etc/conf.d/${service}.${softlevel}
The actual order goes like so /etc/conf.d/rc.$softlevel || /etc/conf.d/rc /etc/conf.d/$service.$softlevel || /etc/conf.d/$service /etc/rc.conf
i wasnt referring to order, but i can update it so order is included
I'm not sure what the exact issue is here - /etc/rc.conf is there to override everything.
