bug-cfengine
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Cfengine] Resolv oddities (cfengine 2.0.6 on HP-UX 11.0)


From: Mark . Burgess
Subject: Re: [Cfengine] Resolv oddities (cfengine 2.0.6 on HP-UX 11.0)
Date: Thu, 15 May 2003 21:27:40 +0200 (MEST)

Fixed in 2.0.7 - bad patch

M

On 15 May, Tjeerd Hes wrote:
> Fredrik Jagenheim wrote:
>> Hi,
>> 
>> Our cf.resolv looks like this (Not really, but you get the idea):
>> 
>> 192.168.1.3
>> 192.168.1.4
>> "domain ourdomain.net"
>> "search ourdomain.net thatdomain.org"
>> 
>> However, the /etc/resolv.conf ends up looking like this:
>> 
>> nameserver 192.168.1.3
>> nameserver 192.168.1.4
>> domain ourdomain.net
>> search ourdomain.net thatdomain.org
>> search ourdomain.net
>> 
>> Note the last bit added, causing our resolver to ignore searching
>> 'thatdomain.org'.
>>
> 
> Works as designed.
> from a man page `man resolv.conf`  (checked solaris + fbsd);
> 
>       The  domain and  search keywords are mutually exclusive.  If
>       more  than  one  instance  of these keywords is present, the
>       last instance takes precedence.
> 
> 
>> AFAIK, this problem didn't exist on 2.0.4.
>> 
>> I did read up on the resolv action, and thought that somehow the
>> 'search ourdomain.net' had appeared from somewhere else and since
>> the resolv action doesn't delete lines, it would just stick around.
>> However, after doing a quickfix for this problem (DeleteLinesMatching
>> in a editfile action) I always got the message that the editfile
>> action had deleted the line, even if I knew it shouldn't be there.
>> 
>> Anyone got some clues they'd like to share?
>> 
>> //F
>> 
> 
> Regards,
> Tjeerd.



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Work: +47 22453272            Email:  address@hidden
Fax : +47 22453205            WWW  :  http://www.iu.hio.no/~mark
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~





reply via email to

[Prev in Thread] Current Thread [Next in Thread]