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#5922 - Stopping network fails on shutdown

Attached to Project: Arch Linux
Opened by Dawid Wróbel (cromo) - Saturday, 02 December 2006, 18:37 GMT
Last edited by Aaron Griffin (phrakture) - Friday, 14 December 2007, 23:26 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

I noticed this behaviour some time ago. When shutting the system down I get following on the screen:
:: Stopping Network [BUSY] SIOCDELRT: No such process
## [FAIL]

I guess that's the reason for the shutting down taking some time, as it has to kill the processes later with SIGHUP.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Friday, 14 December 2007, 23:26 GMT
Reason for closing:  Fixed
Additional comments about closing:  No response to status request. Likely fixed.
Comment by Dawid Wróbel (cromo) - Saturday, 02 December 2006, 19:18 GMT
Also, I tried under console:

cromo@kromka:~/download$ sudo /etc/rc.d/network stop
:: Stopping Network [DONE]
cromo@kromka:~/download$ sudo /etc/rc.d/network start
:: Starting Network [BUSY] SIOCADDRT: File exists

Same problem.
Comment by Roman Kyrylych (Romashka) - Sunday, 03 December 2006, 00:43 GMT
Ehm, what type of network do you have?
Comment by Dawid Wróbel (cromo) - Sunday, 03 December 2006, 20:07 GMT
INTERFACES=(lo eth0 !ath)
The latter is controlled by networkmanager.
Comment by Allan McRae (Allan) - Saturday, 10 November 2007, 16:19 GMT
Apparently, this resulted from eth0 and eth1 randomly switching places with each other with certain chipsets. Googling for the error messages finds no new threads for quite a while - is this fixed?

Loading...