[rancid] coredump.cfg on our Cisco ASA's..

[Howard Leadmon]

In an older version of rancid, we used to edit the rancid file to add a
"next if" line to tell it to skip coredump.cfg if it encountered any change.
This stopped it sending out a diff for every ASA we have on every run, which
is to say the least annoying.

 

Here is an example of what we are seeing:

 

Index: configs/firewall

===================================================================

retrieving revision 1.9

diff -u -4 -r1.9 firewall

@@ -67,9 +67,9 @@

  ! The flash activation key is the SAME as the running key.

  !

  !Flash: --#--  --length--  -----date/time------  path

  !Flash:    13  4096        Jul 14 2009 04:32:24  coredumpinfo

- !Flash:    14  43          Jun 16 2016 21:03:07  coredumpinfo/coredump.cfg

+ !Flash:    14  43          Jun 16 2016 22:03:07  coredumpinfo/coredump.cfg

  !Flash:    84  4181246     May 21 2009 04:16:00
securedesktop-asa-3.2.1.103-k9.pkg

  !Flash:    85  398305      May 21 2009 04:16:22
sslclient-win-1.1.0.154.pkg

  !Flash:    12  4096        Nov 09 2009 19:24:16  crypto_archive

  !Flash:    92  393828      Sep 01 2009 13:25:16
crypto_archive/crypto_arch_1.bin

 

 

 

I am now running version 3.3.0 according the start script, and the rancid
script is very small now, guessing a lot got put elsewhere.   

 

Can anyone point me to a way to make rancid stop sending me an update about
the coredump.cfg file on every run, it would sure be appreciated..

 

 

 

---

Howard Leadmon 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20160616/4884fbec/attachment.html>