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!
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!
FS#32279 - miredo.service fails if network is down
Attached to Project:
Community Packages
Opened by Lauri Kenttä (LK) - Monday, 29 October 2012, 15:44 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 30 October 2012, 09:25 GMT
Opened by Lauri Kenttä (LK) - Monday, 29 October 2012, 15:44 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 30 October 2012, 09:25 GMT
|
DetailsDescription:
If network is down, miredo.service won't start, because ExecStartPre=/usr/sbin/miredo-checkconf gives Temporary failure in name resolution. This is a problem at least with net-auto-wireless, as it takes some time to find the WLAN and by then miredo.service has already failed. Removing the ExecStartPre line fixes the problem, because the actual miredo daemon will just retry periodically. Additional info: * package version(s): miredo 1.2.5-2, systemd 195-2, netcfg 3.0-1 Steps to reproduce: Disconnect network. Start miredo.service. Check status. |
This task depends upon