Summary: | sys-apps/openrc: arping.sh can trigger an infinite loop | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | kouyu <ckyoog> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | roy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
kouyu
2008-04-21 03:16:59 UTC
openrc I'm using is openrc-0.2.2 instead of posting specific versions, you should be posting `emerge --info` Actually, you'll find all local examples of config_$IFACE using multiline. However, this does raise an interesting issue about configs :) config_eth0="1.2.3.4 netmask 255.255.0.0 4.5.6.7 netmask 255.0.0.0" config_eth0="1.2.3.4/16 4.5.6.7/8" Obviously the two are the same, aside from syntax. One is mulitline as the config syntax for a single entry *requires* spaces (thank you ifconfig and bash arrays). In my efforts to ensure we work on non bash shells, maybe I've been to religious in trying to keep existing syntax working. Maybe we should move to this address_eth0="1.2.3.4/18 4.5.6.7/8" ifconfig_eth0="custom ifconfig commands here" ip_eth0="custom ip commands here" intead of doing everything through the config_eth0 variable. Or in another way, keep config_foo as it is, but encourage new address setup as single words only. Old config setup? or new config setup? I don't care. I just hope the config has only one style, one explicit style. And so, how do you plan for this bug? Don't you intend to add one-line-config support to function arping_start? Or you will force user to use multi-line-config. (forget one-line-config?) You will need to update your configuration just like any program out there that comes out with a new version. The migration guide covers certain cases when you need to update your configs and the changes required are documented. |