Summary: | systemd services accessing /etc/resolv.conf need to run after systemd-resolved.service | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Reuben Martin <reuben.m> |
Component: | [OLD] Core system | Assignee: | Gentoo systemd Team <systemd> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Reuben Martin
2015-08-03 21:33:16 UTC
nss-lookup.target seems like a better fit for this. nss-lookup.target A target that should be used as synchronization point for all host/network name service lookups. Note that this is independent of user/group name lookups for which nss-user-lookup.target should be used. All services for which the availability of full host/network name resolution is essential should be ordered after this target, but not pull it in. systemd automatically adds dependencies of type After= for this target unit to all SysV init script service units with an LSB header referring to the "$named" facility. However, systemd-resolved.service is not ordered before nss-lookup.target, so this seems to be broken. That's an issue you might want to ask about upstream. filed upstream: https://github.com/systemd/systemd/issues/848 Re-reading this, I guess we should distinguish between programs that directly access resolv.conf and those that simply do hostname lookups via glibc. For the former, After=systemd-resolved.service may indeed be a better choice. |