Status Locally Modified

Zhang, Anchi AZhang at reliant.com
Thu May 9 19:07:23 UTC 2002


I run do-diffs once a day and I modify router.db whenever a new device is added to the network.  I have never had the need to run cvs commit router.db.

Anchi

-----Original Message-----
From: 'john heasley' [mailto:heas at shrubbery.net]
Sent: Thursday, May 09, 2002 2:01 PM
To: Elliott, Andrew
Cc: Poetzel, Christopher J.; rancid-discuss at shrubbery.net
Subject: Re: Status Locally Modified


Thu, May 09, 2002 at 09:19:45AM -0500, Elliott, Andrew:
> [rancid at athena Switches]$ cvs commit router.db
> 
> 
> -andrew

i guess i'm interested in how it got to this state.  only way
it should be possible is if the file were modified between runs.

that is, given folks' confusion with cvs, i'd prefer that rancid
take of it and it should have.  so, if i've buggered it, i would
like to know what happened so i can fix it.

> -----Original Message-----
> From: john heasley [mailto:heas at shrubbery.net]
> Sent: Wednesday, May 08, 2002 9:17 PM
> To: Poetzel, Christopher J.
> Cc: rancid-discuss at shrubbery.net
> Subject: Re: Status Locally Modified
> 
> 
> Wed, May 08, 2002 at 07:52:03PM -0500, Poetzel, Christopher J.:
> > I am having an issue where every time rancid runs(do-diffs) I get messages
> > saying that my router.db file
> > has changed, and it hasn't.  I ran the cvs status command on it and got
> the
> > following.
> >  
> >  
> > [rancid at athena Switches]$ cvs status router.db
> > ===================================================================
> > File: router.db         Status: Locally Modified
> >  
> >  
> > I recently changed the names of some of my routers when this happened.  If
> > anyone has any thoughts of how to get the status back
> > to UP-to-Date I would really appreciate it.
> >  
> >  
> > thanks,
> >  
> > chris poetzel
> 
> if this file gets modified (add/delete/rename a device), rancid should
> commit the file after it show you the diff of the file.  if it isnt
> committed when rancid runs, then its having some sort of problem with
> the commit which should appear in the log file.
> 
> if nothing appears there, please see the CVS section of the FAQ.



More information about the Rancid-discuss mailing list