Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#25671 - [initscripts] network daemon fails

Attached to Project: Arch Linux
Opened by James Campos (aeosynth) - Friday, 19 August 2011, 09:27 GMT
Last edited by Tom Gundersen (tomegun) - Saturday, 20 August 2011, 14:39 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Dave Reisner (falconindy)
Tom Gundersen (tomegun)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

# ./network start
:: Starting Network [BUSY] Cannot find device "up"
[DONE]

# ./network stop
:: Stopping Network [BUSY] Command line is not complete. Try option "help"
[DONE]

manually running dhcpcd works just fine. this is off a fresh net install.
This task depends upon

Closed by  Tom Gundersen (tomegun)
Saturday, 20 August 2011, 14:39 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Friday, 19 August 2011, 09:55 GMT
This is probably a configuration issue. Please post your network settings from rc.conf.
Comment by James Campos (aeosynth) - Friday, 19 August 2011, 10:09 GMT
Oops, fixed by setting `interface=eth0` in rc.conf. The daemon should probably state `interface required but not set` or something.
Comment by Tobias Powalowski (tpowa) - Friday, 19 August 2011, 10:31 GMT
Problem here is that the default rc.conf file no entry provides.
Comment by Gerardo Exequiel Pozzi (djgera) - Friday, 19 August 2011, 14:44 GMT
I see three options here:
1) Keep things like now.
2) Show a warning about no network is configured (empty interface= but network is enabled).
3) Make default rc.conf self-consistent, if by default interface= is empty then also network should be disabled. (I proposed this some time ago, but not accepted)
Comment by Tom Gundersen (tomegun) - Friday, 19 August 2011, 17:11 GMT
Ideally we should verify that the input we get is valid (i.e. $interface should be an existing network device, not just a random string) before using it.

If it is invalid (e.g. empty) we should warn and fail.
Comment by Dave Reisner (falconindy) - Friday, 19 August 2011, 17:32 GMT
https://github.com/falconindy/initscripts-arch/commit/3ee7b326ad6d60b0d713cfd5c958c18e111b9e28
Comment by Tom Gundersen (tomegun) - Friday, 19 August 2011, 17:49 GMT
@falconindy: thanks.

Loading...