[rancid] Prevent commit when device cannot be reached

[Marki]

On 06/12/2025 18:54, heasley wrote:

> Fri, Dec 05, 2025 at 11:19:22AM +0100, Marki:
> 
>> For example, this happens:
>> 
>> executing clogin -t 90 -c"terminal more disable;show running-config"
>> 192.168.80.112
>> 192.168.80.112: clogin error: Error: Couldn't login: 192.168.80.112
>> 192.168.80.112: missed cmd(s): all commands
>> 192.168.80.112: End of run not found
>> 192.168.80.112: clean_run is false
>> 192.168.80.112: found_end is false
>> Sending        configs/192.168.80.112   <--- This is what I'd like to
>> prevent.
>> 
>> What setting should I use in order to prevent commit in such a case?
> 
> The only reason that I can imagine you would care about this is if
> you have some other process that consumes the files.  Assuming that
> is the case, simply ignore files that have fewer than 10 lines or
> less than 100 bytes or something like similar.

I care about it bc I like my repos clean i.e. without useless commits.

I'm not sure we are talking about the same thing here.

I'm used to not getting any empty/irrelevant config committed but 
instead get email notification about "missed" routers after 24 hours.

I'll dig a little bit further why this isn't the case with this module 
which I copy/pasted together from other modules.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.shrubbery.net/pipermail/rancid-discuss/attachments/20251207/7eafd51f/attachment.htm>