tags 479867 +pending thanks On Wed 2008-05-07 00:52:18 -0400, Soeren Sonnenburg wrote:
> when one has djbdns installed and its dnscache configured as forwared
> (but marked down), then resolvconf will try to restart dnscache even if it
> is down and fail. The reason is in /etc/resolvconf/update.d/dnscache
> and the fix is to add a [ ! -f "$SVC/down" ] to the if like here:
Good catch, Soeren. I've applied your patch, so it should hopefully
make it into 1.41. I'm not entirely sure it's the right thing to do,
but i'm happy to go with your suggestion for now since you raised the
concern.
I'd be curious to know what you think about the following alternative
strategy for handling this:
Instead of avoiding a "down" forwarding dnscache entirely, we could
update its root/servers/@ as before, but simply decline to restart the
service. This way, if the administrator later decides to bring up the
dnscache instance after bringing up the interface, it will be properly
configured.
Would this break your use case or cause other misbehavior you can
think of?
Thanks for the report,
--dkg
pgpinbzULGsL1.pgp
Description: PGP signature
