FS#33608 - [netcfg] systemd unit starts when there is no eth0

Attached to Project: Arch Linux
Opened by Maciej Mazur (mamciek) - Monday, 28 January 2013, 12:26 GMT
Last edited by Eric Belanger (Snowman) - Tuesday, 30 April 2013, 01:02 GMT
Task Type Bug Report
Category Arch Projects
Status Closed
Assigned To Jouke Witteveen (jouke)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:

Often (after powering the system off and starting it again) the systemd unit fails with message:

sty 28 10:16:55 ktr-mmazur netcfg-daemon[306]: :: wire up Interface eth0 does not exist
sty 28 10:16:55 ktr-mmazur netcfg-daemon[306]: [fail]

In unit file there is "Before=network.target", bu i guess it is too early sometimes

Additional info:
* package version(s): 3.0-1
This task depends upon

Closed by  Eric Belanger (Snowman)
Tuesday, 30 April 2013, 01:02 GMT
Reason for closing:  Won't fix
Additional comments about closing:  netcfg has been moved to AUR
Comment by Jason Russell (jrussell) - Monday, 28 January 2013, 17:07 GMT
Have the same problem, happens occasionally, threads:

https://bbs.archlinux.org/viewtopic.php?pid=1222274
https://bbs.archlinux.org/viewtopic.php?pid=1217841
Comment by Maciej Mazur (mamciek) - Monday, 28 January 2013, 17:27 GMT
Thanks.

I must mention that after I login there is always eth0 (ip link) available. In given threads people claims that sometimes eth0 just don't show up at all - this is not the case in my situation

Loading...