cloginrc and multiple matching directives

Hopper, Faron W. faron.hopper at
Sat Sep 10 04:48:54 UTC 2005

Ed, you are quite right.  It is amazing that things, once asked, seem to be right in front of you.  I am grateful for your time and for pointing that out.  After staring at the same screen for a while, it seems like it all blurred together.  Thank you for your patience and your answers.

Faron Hopper
Network Engineer
3315 N. Oak Trfy
Kansas City, MO 64116

-----Original Message-----
From: Ed Ravin [mailto:eravin at]
Sent: Fri 9/9/2005 3:53 PM
To: Hopper, Faron  W.
Cc: rancid-discuss at
Subject: cloginrc and multiple matching directives

On Fri, Sep 09, 2005 at 04:31:06PM -0400, Hopper, Faron  W. wrote:
> So, my last line, 206.245.31.* {pass2}, does this work in
> conjunction with the line add password  *  {pass}?  So everything
> that is NOT 206.245.31.* will get pass and everything with 206.245.31.*
> will get pass2?  Is there anything else that I should be aware of
> when defining these devices?  Like should I add all of my specific
> devices first and then add the wild card?  Or what about the pattern
> matching piece of the puzzle.  If I specify cg* and then have 2
> devices say, cgk01 and 01cg will it find both of those, or just
> the cgk01?

See "man cloginrc", in particular this part:

     As  .cloginrc  is  searched  for a directive matching a hostname, it is
     always the first matching instance of a directive, one  whose hostname
     glob  expression  matches  the  hostname,  which is used.  For example;
     looking up the "password" directive for hostname  foo  in  a ..cloginrc
     file containing

               add password *   {bar} {table}
               add password foo {bar} {table}

     would  return the first line, even though the second is an exact match.

More information about the Rancid-discuss mailing list