FS#47685 - [pdnsd] systemd service fails to load pdnsd *after* the interface is up
Attached to Project:
Community Packages
Opened by Vorbote (vorbote) - Sunday, 10 January 2016, 01:13 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 19 January 2016, 15:17 GMT
Opened by Vorbote (vorbote) - Sunday, 10 January 2016, 01:13 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 19 January 2016, 15:17 GMT
|
Details
Description:
The systemd service fails to load the pdnsd daemon *after* the interface is up with NetworkManager The reason for this is that the service depends on network.target, not on network-online.target and it neither waits for network-online.target to be finished. As is, pdnsd starts but has no access to the datalink because it starts after pdnsd. To obtain DNS resolution, you need to restart pdnsd by hand Rating high because it breaks functionality. This service file works as expected: ################################################################## [Unit] Description=proxy name server Wants=network-online.target After=network-online.target [Service] ExecStart=/usr/bin/pdnsd [Install] WantedBy=multi-user.target ################################################################## |
This task depends upon
I suggest you to use
$ systemctl edit pdnsd
to adjust pdnsd deps
What is worrying is that NM upstream has decided in all its wisdom to enable NetworkManager-wait-online system-wide. I still prefer GNOME (or GNOME-i3) but I'm starting to feel they are shoving NM down our collective throats. *Sigh*