<div dir="ltr"><div class="gmail_default" style="font-family:courier new,monospace"><span style="font-family:arial">On 7 June 2013 16:22, heasley </span><span dir="ltr" style="font-family:arial"><<a href="mailto:heas@shrubbery.net" target="_blank">heas@shrubbery.net</a>></span><span style="font-family:arial"> wrote:</span><br>
</div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thu, Jun 06, 2013 at 09:52:50PM +0100, Alex DEKKER:<div class="im">
> If it's not the default, then it will catch instances where a<br>
> forward-thinking admin [or package maintainer] thinks to enable it; it<br>
> won't help noobs setting RANCID working on their own.<br>
<br>
</div>so, ./configure --noobpid ?<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:'courier new',monospace">As hilarious as that would be... ;)</div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
how about just adding the check to rancid.conf? that affects everything that<br>
reads it, the check can be customized (like adding a timer), or completely<br>
disabled w/o an arg/etc.</blockquote><div><br></div><div class="gmail_default" style="font-family:'courier new',monospace">It'd be great if it was default-on though. Just my opinion though, like you say, it's only people unfamiliar with how RANCID works and think they're being helpful by running rancid-run immediately after altering a router.db</div>
<div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">M</div></div></div></div>