From heas at shrubbery.net Fri Aug 9 18:40:14 2002 From: heas at shrubbery.net (john heasley) Date: Fri, 9 Aug 2002 11:40:14 -0700 Subject: rancid 2.2.2 Message-ID: <20020809114014.H20921@shrubbery.net> i've made rancid-2.2.2 available for ftp from ftp.shrubbery.net:/pub/rancid *** if you make use of the looking glass (lg) scripts that come with rancid, PLEASE upgrade. previous versions did not check the query target properly, allowing someone with access to the looking glass to query any device which can be logged into. possible bug: a user to whom we supplied an EFT copy of flogin told us that it did not work with certain devices, but became silent when we asked for more information. 2.2.2 *login: fix handling of userprompt et al so that {}'s are used in .cloginrc as they are with every other .cloginrc directive. f10rancid: Fix to pick up new info in show version output. jrancid: Ignore Timecounter "TSC" in show system boot-messages output. rancid: filter tty line speed when configured for auto-configure flogin: bring login() and do_enable() in-line with [cj]login. also match "telnet server disabled" - from brad volz. control_rancid: report devices added to router.db - from Fredrik Thulin also eliminate empty up/down lists. rancid/jrancid: filter isis passwords - partial from Janos Mohacsi lg: make o/p from the lg stream (unbuffered), so one doesnt have to wait for entire o/p from the router in a failing traceroute, for example. suggestion and clues from alexander koch. while here, fix cache handling so 1) it doesnt cache cmds that resulted in an error or otherwise failed and 2) log and run the cmd as normal if there are problems opening a cache file. lg: make logging more consistent. log as defined by LG_LOG if possible and stderr as last resort. it was logging largely to stderr. and make exit-code small (instead of 255); some wait()s only look at the first 3 bits lg: add check in lg.cgi that router name appears in the router.db and is thus accessible. from richard doty. also fix-up a few comments and such. rancid: GSR LC PCA h/w revision now called "design release" on some platforms. CSCdw13295 add util/getipacctg example script - contrib from steve neighorn From rancid at jnull.rackspace.com Sat Aug 24 22:53:49 2002 From: rancid at jnull.rackspace.com (rancid) Date: Sat, 24 Aug 2002 17:53:49 -0500 Subject: customize commands Message-ID: <20020824225349.GA32066@jnull.rackspace.com> Forgive the newbie. Implementation and general satisfaction meets expectations.... However, I would like to know how to customize the commmands set used by do-diffs. (I attempted to sort through archives, but ugh.) -- sig=$header From heas at shrubbery.net Sun Aug 25 19:26:17 2002 From: heas at shrubbery.net (john heasley) Date: Sun, 25 Aug 2002 19:26:17 +0000 Subject: customize commands In-Reply-To: <20020824225349.GA32066@jnull.rackspace.com>; from rancid@jnull.rackspace.com on Sat, Aug 24, 2002 at 05:53:49PM -0500 References: <20020824225349.GA32066@jnull.rackspace.com> Message-ID: <20020825192617.A26685@shrubbery.net> Sat, Aug 24, 2002 at 05:53:49PM -0500, rancid: > Forgive the newbie. Implementation and general satisfaction meets > expectations.... However, I would like to know how to customize the commmands > set used by do-diffs. (I attempted to sort through archives, but ugh.) > -- > sig=$header there isnt such a facility built-in at the moment. we have been discussing how to add this though. so, its coming at some point. From jayb at braeburn.org Thu Aug 29 15:42:08 2002 From: jayb at braeburn.org (Jay Borkenhagen) Date: Thu, 29 Aug 2002 11:42:08 -0400 Subject: customize commands In-Reply-To: <20020825192617.A26685@shrubbery.net> References: <20020824225349.GA32066@jnull.rackspace.com> <20020825192617.A26685@shrubbery.net> Message-ID: <15726.16592.262209.672693@oz.mt.att.com> >> Forgive the newbie. Implementation and general satisfaction meets >> expectations.... However, I would like to know how to customize the >> commmands set used by do-diffs. (I attempted to sort through >> archives, but ugh.) heas> there isnt such a facility built-in at the moment. we have been heas> discussing how to add this though. so, its coming at some heas> point. As someone who just upgraded to rancid-2.2.2 thereby unintentionally clobbering my modifications to bin/rancid's list of router commands of interest, let me voice my support for such a facility. I see that "make install" preserved my modified bin/env file with the new one ending up in bin/env.new -- it would be terrific if the command set was in a file which would be similarly preserved across an upgrade. Thanks. Jay B. -- Jay Borkenhagen jayb at braeburn.org From heas at shrubbery.net Thu Aug 29 16:07:07 2002 From: heas at shrubbery.net (john heasley) Date: Thu, 29 Aug 2002 09:07:07 -0700 Subject: customize commands In-Reply-To: <15726.16592.262209.672693@oz.mt.att.com>; from jayb@braeburn.org on Thu, Aug 29, 2002 at 11:42:08AM -0400 References: <20020824225349.GA32066@jnull.rackspace.com> <20020825192617.A26685@shrubbery.net> <15726.16592.262209.672693@oz.mt.att.com> Message-ID: <20020829090707.D4320@shrubbery.net> Thu, Aug 29, 2002 at 11:42:08AM -0400, Jay Borkenhagen: > >> Forgive the newbie. Implementation and general satisfaction meets > >> expectations.... However, I would like to know how to customize the > >> commmands set used by do-diffs. (I attempted to sort through > >> archives, but ugh.) > > heas> there isnt such a facility built-in at the moment. we have been > heas> discussing how to add this though. so, its coming at some > heas> point. > > As someone who just upgraded to rancid-2.2.2 thereby unintentionally > clobbering my modifications to bin/rancid's list of router commands of > interest, let me voice my support for such a facility. I see that > "make install" preserved my modified bin/env file with the new one > ending up in bin/env.new -- it would be terrific if the command set > was in a file which would be similarly preserved across an upgrade. > the idea we've been kicking around is to have a file (a default file included with the dist and perhaps a "file.local") which defines a device "type". for a given type, you could set which commands you wanted collected and what function (including home-grown external scripts) to use to filter the output. this "type" is then used as the type in the router.db file, eg: cisco or cisco_osr, where cisco_sla might have additional (or fewer) commands for your OSRs.