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#42837 - [polipo] service needs to start after systemd-resolved.service
Attached to Project:
Community Packages
Opened by Eric Wang (enihcam) - Wednesday, 19 November 2014, 04:30 GMT
Last edited by Thorsten Töpper (Atsutane) - Sunday, 09 August 2015, 06:21 GMT
Opened by Eric Wang (enihcam) - Wednesday, 19 November 2014, 04:30 GMT
Last edited by Thorsten Töpper (Atsutane) - Sunday, 09 August 2015, 06:21 GMT
|
DetailsDescription:
polipo service needs to start after systemd-resolved.service, or you will see the following error: [code] polipo[233]: DNS: couldn't open /etc/resolv.conf: No such file or directory [/code] This is because when you use systemd-resolved.service rather than dhcpcd/dhcpclient, /etc/resolv.conf will be linked to /run/systemd/resolve/resolv.conf, which is dynamic file created after systemd-resolved.service starts up. Additional info: * package version(s) Any * config and/or log files etc. Steps to reproduce: 1. Setup and enable systemd-resolved.service 2. Make sure /etc/resolv.conf is linked to /run/systemd/resolve/resolv.conf 3. Enable polipo.service 4. Reboot 5. See 'journalctl -b' |
This task depends upon
Closed by Thorsten Töpper (Atsutane)
Sunday, 09 August 2015, 06:21 GMT
Reason for closing: Won't implement
Additional comments about closing: Silence for 9 months. Seems the proposed .service file works.
Sunday, 09 August 2015, 06:21 GMT
Reason for closing: Won't implement
Additional comments about closing: Silence for 9 months. Seems the proposed .service file works.
@Jelle Editing the service file will be undo after package upgrade?
Eric, when you copy the file to the folder /etc/systemd/system/multi-user.target.wants/ and don't create a symlink using "systemctl enable polipo.service" you have a stable service file that won't be touched by any updates.