On 08/18, heasley wrote: > Fri, Aug 17, 2018 at 10:16:51PM +0300, Pavel Korovin: > > There are several issues with fluctuating data received from Cisco Nexus > > platform (55xx, 77xx): > > > > * if PAR_COUNT is > 1 (by default, it's 5) and rancid simultaneously runs > > "show version" in multiple VDCs on the same device, bootflash size > > slot0 too? or just bootflash? I don't have Nexus devices with slot0 size > 0, but I suppose it should be the same story.
> > values hop between 0 and actual size, with each invocation producing cvs > > commits and change notifications. To reproduce, run "show ver" > > simultaneously on multiple VDCs. It seems that NX-OS requires exclusive > > access to hardware to determine the size of bootflash and fails during > > concurrent access. I cannot offer any better solution than just > > providing a knob to filter out bootflash size fluctuations by setting > > FILTER_OSC = ALL. > > - # Drop accounting.log > > - /\s+accounting\.log$/ && next; > > + # Drop accounting logs > > + /\s+accounting.log.*/ && next; > > was removal of the escape of the . intentional? Yes. I don't remember if earlier versions of NX-OS use accounting_log or accounting.log naming, so it will filter both. -- With best regards, Pavel Korovin _______________________________________________ Rancid-discuss mailing list [email protected] http://www.shrubbery.net/mailman/listinfo/rancid-discuss
