Hello,
In Guix, we need to create /etc/resolv.conf before the nscd service/daemon runs --that's done so that nscd can use inotify on the pre-existing resolv.conf file (if it doesn't exist, it does not monitor changes). This can't currently be done with openresolv -u as it wants to restart nscd itself, leading to some circular dependency in the services graph.
So the best I've found is to create the file "by hand", with the right comment signature that openresolv wants to know its responsible for it (# Generated by resolvconf).
Perhaps there could be a new option added to resolvconf, to create a dummy file with its comment, that would not attempt restarting nscd ? Or some explicit flag to tell it to not do that for a particular invocation?
Thanks.
Hello,
In Guix, we need to create /etc/resolv.conf before the
nscdservice/daemon runs --that's done so thatnscdcan useinotifyon the pre-existing resolv.conf file (if it doesn't exist, it does not monitor changes). This can't currently be done withopenresolv -uas it wants to restartnscditself, leading to some circular dependency in the services graph.So the best I've found is to create the file "by hand", with the right comment signature that openresolv wants to know its responsible for it (
# Generated by resolvconf).Perhaps there could be a new option added to resolvconf, to create a dummy file with its comment, that would not attempt restarting
nscd? Or some explicit flag to tell it to not do that for a particular invocation?Thanks.