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#33816 - [netcfg] bahaves unstable under systemd (doesn't wait for interface creation?)

Attached to Project: Arch Linux
Opened by Marek Kozlowski (guayasil) - Monday, 11 February 2013, 17:01 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 30 April 2013, 01:03 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

netcfg.service with ethernet-dhcp
Sorry, I cannot describe the problem precisely. The workstation was restarted 10 times. 3 times it started OK, 4 times netcfg failed, 3 times it faileda nd after I while I started.

In case of failure journalctl messages are like this:
Feb 01 17:25:58 localhost netcfg-daemon[236]: :: ethernet-dhcp up Interface eth0 does not exist
Feb 01 17:25:58 localhost netcfg-daemon[236]: [fail]
Feb 01 17:25:58 localhost systemd[1]: netcfg.service: main process exited, code=exited, status=1/FAILURE
Feb 01 17:25:58 localhost systemd[1]: Failed to start Netcfg multi-profile daemon.
Feb 01 17:25:58 localhost systemd[1]: Unit netcfg.service entered failed state

Seems like, for unknown reason it starts without waiting for proper creation and initialization of network interfaces. Because systemd allows parallel startup sometimes the interface is ready while sometimes - not.
This task depends upon

Closed by  Eric Belanger (Snowman)
Tuesday, 30 April 2013, 01:03 GMT
Reason for closing:  Won't fix
Additional comments about closing:  netcfg has been moved to AUR

Loading...