Summary: | net-misc/dhcpcd-5.2.9 gives /sbin/rc-service: invalid option -- 'D' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | niv <nivw2008> |
Component: | [OLD] baselayout | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://roy.marples.name/archives/dhcpcd-discuss/2011/0272.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
niv
2011-01-04 23:25:47 UTC
*** Bug 350637 has been marked as a duplicate of this bug. *** I'd check your configuration files for dhcpcd, syntax has changed a bit. after establishing ppp0 I see that /etc/resolv.conf wasnt updated , so I manually run it: # resolvconf -a ppp0 </etc/resolv.conf.strongvpn /sbin/rc-service: invalid option -- 'D' Usage: rc-service [options] Options: [e:ilr:Chqv] -e, --exists <arg> tests if the service exists or not -i, --ifexists if the service exsits then run the command -l, --list list all available services -r, --resolve <arg> resolve the service name to an init script -h, --help Display this help output -C, --nocolor Disable color output -v, --verbose Run verbosely -q, --quiet Run quietly /sbin/rc-service: invalid option -- 'D' Usage: rc-service [options] Options: [e:ilr:Chqv] -e, --exists <arg> tests if the service exists or not -i, --ifexists if the service exsits then run the command -l, --list list all available services -r, --resolve <arg> resolve the service name to an init script -h, --help Display this help output -C, --nocolor Disable color output -v, --verbose Run verbosely -q, --quiet Run quietly 1. was it openresolv that caused this issue in the first place? 2. how can I find the cause to this? is there a debug flag? or should I set +x somewhere? this seems relevent http://bugs.gentoo.org/show_bug.cgi?id=349180 (In reply to comment #4) > this seems relevent > http://bugs.gentoo.org/show_bug.cgi?id=349180 > You're probably right. Test with new release. *** This bug has been marked as a duplicate of bug 349180 *** |