Re: Bug in resolve?

[Wil Cooley]

On Mon, 2005-04-18 at 22:03 +0200, Pip Oomen wrote:
> Is the following a known issue? Or is there something wrong in my
> configuration?

Kinda both.  The ":" is the list separator, so the 'options timeout' and
'1' are taken as separate configuration items and since the latter is a
number, it is assumed to be a nameserver address.  Eric Sorenson
prepared a patch for me to add a '${colon}', which would let you use
'options timeout${colon}1', but unfortunately I never got around to
testing it and I don't think he submitted it.  You can redefine the list
separator (but you'll also need to choose one that you don't expect to
use in a string and you'll have to change any existing lists).

OTOH, you can just create a site-wide resolv.conf and use 'copy' to
distribute it.  I started using 'resolve', but it seemed to be largely
redundant and I had a few problems keeping it up (not to mention kept
having to refer to the manual for yet another thing), so I just dumped
it and used 'copy'.

Honestly, I don't think 'resolve' really needs to exist, unless there's
something really special that I'm missing.  From what I can tell, it's
just more syntactical baggage, like many of the directives.  Looking
over the cfagent directives listed in the reference manual, there are
33, 15 of which I actually use.  Another 4 or 5 I could imagine using.
But then again, I'm managing fewer than 20 machines over a couple
different customer sites; maybe if I managed a larger individual network
that other 1/3 would seem more useful.

Wil
-- 
Wil Cooley                                 address@hidden
Naked Ape Consulting                        http://nakedape.cc
* * * * Linux, UNIX, Networking and Security Solutions * * * *

signature.asc
Description: This is a digitally signed message part