From brett at fj.com.au Wed Sep 5 05:04:24 2001 From: brett at fj.com.au (Brett O'Hara) Date: Wed, 5 Sep 2001 15:04:24 +1000 Subject: Newbie install question Message-ID: <017601c135c8$3ba7d270$01000001@U013423> Warning: newbie question. I've just intalled rancid-2.1.0 on our Solaris 8, with tcl-8.3.1, tk-8.3.1, expect-5.32, and cvs 1.11 After following the instructions, I'm now receiving; [root at mel1:/usr/local/rancid/logs]$ cat core.20010905.150101 starting: Wed Sep 5 15:01:01 EST 2001 Trying to get all of the configs. All routers sucessfully completed. cvs diff: in directory .: cvs [diff aborted]: there is no version here; run 'cvs checkout' first cvs [commit aborted]: cannot commit files as 'root' ending: Wed Sep 5 15:01:12 EST 2001 Obviously I need to run the scripts as other than root, but knowing nothing about cvd, I'm wondering what the cvs checkout stuff is? Regards, Brett From afort at staff.webcentral.com.au Wed Sep 5 05:33:47 2001 From: afort at staff.webcentral.com.au (Andrew Fort) Date: Wed, 5 Sep 2001 15:33:47 +1000 Subject: Newbie install question Message-ID: <415DD4BF903BD311A3D900A0C99F90220960723C@bnc.webcentral.com.au> >[root at mel1:/usr/local/rancid/logs]$ cat core.20010905.150101 >starting: Wed Sep 5 15:01:01 EST 2001 > >Trying to get all of the configs. >All routers sucessfully completed. > >cvs diff: in directory .: >cvs [diff aborted]: there is no version here; run 'cvs checkout' first >cvs [commit aborted]: cannot commit files as 'root' > >ending: Wed Sep 5 15:01:12 EST 2001 > >Obviously I need to run the scripts as other than root, but >knowing nothing >about cvd, I'm wondering what the cvs checkout stuff is? Brett, it looks like you possibly didn't run /usr/local/rancid/bin/create_cvs once you'd set up the groups you want (such as 'core') in the /usr/local/rancid/bin/env file (LIST_OF_GROUPS variable). create_cvs can handle if your directories have already been manually created (e.g., you manually created /usr/local/rancid/core/), but the recommended method is to just add to the LIST_OF_GROUPS, then run create_cvs. The way I setup permissions was to create a rancid user (and group), then set the permissions as (from memory): chgrp -r rancid /usr/local/rancid/ chmod g+ws /usr/local/rancid/ Then put your admins in the rancid group. The rancid user has its own ~/.cloginrc naturally, and this user is the one which 'cleans up' after the admins who forget to 'do-diffs' after they make changes, i.e., from cron (we do it once an hour, if you run less regularly than that, be aware of the value of OLDTIME in the /usr/local/rancid/bin/env should be greater than the number of hours between your 'rancid' cronjobs. If you're still stuck, try going through the quickstart guide again, I found it made much more sense the second time... -afort From heas at shrubbery.net Wed Sep 5 08:44:37 2001 From: heas at shrubbery.net (john heasley) Date: Wed, 5 Sep 2001 01:44:37 -0700 Subject: Newbie install question In-Reply-To: <415DD4BF903BD311A3D900A0C99F90220960723C@bnc.webcentral.com.au>; from afort@staff.webcentral.com.au on Wed, Sep 05, 2001 at 03:33:47PM +1000 References: <415DD4BF903BD311A3D900A0C99F90220960723C@bnc.webcentral.com.au> Message-ID: <20010905014437.B13388@shrubbery.net> Wed, Sep 05, 2001 at 03:33:47PM +1000, Andrew Fort: > >[root at mel1:/usr/local/rancid/logs]$ cat core.20010905.150101 > >starting: Wed Sep 5 15:01:01 EST 2001 > > > >Trying to get all of the configs. > >All routers sucessfully completed. > > > >cvs diff: in directory .: > >cvs [diff aborted]: there is no version here; run 'cvs checkout' first > >cvs [commit aborted]: cannot commit files as 'root' > > > >ending: Wed Sep 5 15:01:12 EST 2001 > > > >Obviously I need to run the scripts as other than root, but > >knowing nothing > >about cvd, I'm wondering what the cvs checkout stuff is? > > Brett, it looks like you possibly didn't run > /usr/local/rancid/bin/create_cvs once you'd set up the groups you want (such > as 'core') in the /usr/local/rancid/bin/env file (LIST_OF_GROUPS variable). > create_cvs can handle if your directories have already been manually created > (e.g., you manually created /usr/local/rancid/core/), but the recommended > method is to just add to the LIST_OF_GROUPS, then run create_cvs. > > The way I setup permissions was to create a rancid user (and group), then > set the permissions as (from memory): > > chgrp -r rancid /usr/local/rancid/ > chmod g+ws /usr/local/rancid/ > > Then put your admins in the rancid group. > > The rancid user has its own ~/.cloginrc naturally, and this user is the one > which 'cleans up' after the admins who forget to 'do-diffs' after they make > changes, i.e., from cron (we do it once an hour, if you run less regularly > than that, be aware of the value of OLDTIME in the /usr/local/rancid/bin/env > should be greater than the number of hours between your 'rancid' cronjobs. thats a good point! thanks, i'll be sure to add a note. > If you're still stuck, try going through the quickstart guide again, I found > it made much more sense the second time... hmm, if thats the case (as it seems so), please tell us how we might improve the install instructions. thanks. also, see the rancid_intro man page. > -afort From brett at fj.com.au Wed Sep 5 08:55:00 2001 From: brett at fj.com.au (Brett O'Hara) Date: Wed, 5 Sep 2001 18:55:00 +1000 Subject: Newbie install question References: <415DD4BF903BD311A3D900A0C99F90220960723C@bnc.webcentral.com.au> <20010905014437.B13388@shrubbery.net> Message-ID: <024401c135e8$71e6a3f0$01000001@U013423> I worked it out. create_cvs does NOT cope with manually creating the directory. I've adopted Andrew's user stuff which works like a dream, and now I finally have notification when somone makes changes to our Cisco's (no more finding out 2 weeks later that something's been messed with and broken). Regards, Brett ----- Original Message ----- From: "john heasley" To: "Andrew Fort" Cc: "'Brett O'Hara'" ; Sent: Wednesday, September 05, 2001 6:44 PM Subject: Re: Newbie install question > Wed, Sep 05, 2001 at 03:33:47PM +1000, Andrew Fort: > > >[root at mel1:/usr/local/rancid/logs]$ cat core.20010905.150101 > > >starting: Wed Sep 5 15:01:01 EST 2001 > > > > > >Trying to get all of the configs. > > >All routers sucessfully completed. > > > > > >cvs diff: in directory .: > > >cvs [diff aborted]: there is no version here; run 'cvs checkout' first > > >cvs [commit aborted]: cannot commit files as 'root' > > > > > >ending: Wed Sep 5 15:01:12 EST 2001 > > > > > >Obviously I need to run the scripts as other than root, but > > >knowing nothing > > >about cvd, I'm wondering what the cvs checkout stuff is? > > > > Brett, it looks like you possibly didn't run > > /usr/local/rancid/bin/create_cvs once you'd set up the groups you want (such > > as 'core') in the /usr/local/rancid/bin/env file (LIST_OF_GROUPS variable). > > create_cvs can handle if your directories have already been manually created > > (e.g., you manually created /usr/local/rancid/core/), but the recommended > > method is to just add to the LIST_OF_GROUPS, then run create_cvs. > > > > The way I setup permissions was to create a rancid user (and group), then > > set the permissions as (from memory): > > > > chgrp -r rancid /usr/local/rancid/ > > chmod g+ws /usr/local/rancid/ > > > > Then put your admins in the rancid group. > > > > The rancid user has its own ~/.cloginrc naturally, and this user is the one > > which 'cleans up' after the admins who forget to 'do-diffs' after they make > > changes, i.e., from cron (we do it once an hour, if you run less regularly > > than that, be aware of the value of OLDTIME in the /usr/local/rancid/bin/env > > should be greater than the number of hours between your 'rancid' cronjobs. > > thats a good point! thanks, i'll be sure to add a note. > > > If you're still stuck, try going through the quickstart guide again, I found > > it made much more sense the second time... > > hmm, if thats the case (as it seems so), please tell us how we might improve > the install instructions. thanks. also, see the rancid_intro man page. > > > -afort > From afort at staff.webcentral.com.au Wed Sep 5 12:00:52 2001 From: afort at staff.webcentral.com.au (Andrew Fort) Date: Wed, 5 Sep 2001 22:00:52 +1000 Subject: Newbie install question Message-ID: <415DD4BF903BD311A3D900A0C99F90220960723E@bnc.webcentral.com.au> Brett o'hara wrote; >I worked it out. create_cvs does NOT cope with manually creating the >directory. I've adopted Andrew's user stuff which works like >a dream, and >now I finally have notification when somone makes changes to >our Cisco's (no >more finding out 2 weeks later that something's been messed with and >broken). The limitation here is that 'rancid' made the changes (or whichever user is doing the cronjob). tracking down whom to execute the lart(8) on requires other logs, so be sure to keep TACACS+/RADIUS accounting logs so you can track down those 'cleaner' admins who have that awful habit of 'cleaning up' router configs :) On this point, I've been considering hacking in a 'RANCID-APPARENTLY-BY:' tag (at the top of the diff) which would grab the username from the 'Last modified by' stuff (at the top of the output of 'wr term'/'sh run' on IOS), where it's valid, so the stored config actually tells you who last updated it (well, apparently :). Upon examining the code, it looks like someone tried to do this, but commented the code out; perahps due to inconsistencies in the formatting of these two lines between different IOS versions (or the lack of this data on other platforms).. can anyone shed some light on this? anyone else reckon this feature wouldn't suck? after all, there's no use cluttering up the config files with yet more cruft if it's only me who wants it :) -afort From afort at staff.webcentral.com.au Wed Sep 5 12:03:47 2001 From: afort at staff.webcentral.com.au (Andrew Fort) Date: Wed, 5 Sep 2001 22:03:47 +1000 Subject: Newbie install question Message-ID: <415DD4BF903BD311A3D900A0C99F90220960723F@bnc.webcentral.com.au> >> The rancid user has its own ~/.cloginrc naturally, and this >user is the one >> which 'cleans up' after the admins who forget to 'do-diffs' >after they make >> changes, i.e., from cron (we do it once an hour, if you run >less regularly >> than that, be aware of the value of OLDTIME in the >/usr/local/rancid/bin/env >> should be greater than the number of hours between your >'rancid' cronjobs. > >thats a good point! thanks, i'll be sure to add a note. > John, if you're referring to 'check OLDTIME if you're running less-than-regular cronjobs', there's already a note in the README for that (under section 9). From david_laporte at harvard.edu Fri Sep 21 21:16:20 2001 From: david_laporte at harvard.edu (David LaPorte) Date: Fri, 21 Sep 2001 17:16:20 -0400 Subject: Rancid hangs Message-ID: <014d01c142e2$a9defd50$c9d16780@navajo> Hi all, Has anyone seen behavior similar to the following? Recently, when querying our routers for configurations, clogin seems to = hang while downloading the configuration. For instance, running clogin = manually with the command-line: ./clogin -t 90 -c show version;show install active;show env all;show gsr = chassis;show boot;show bootvar;show variables boot;show flash;dir /all = nvram:;dir /all bootflash:;dir /all slot0:;dir /all disk0:;dir /all = slot1:;dir /all disk1:;show controllers;show controllers cbus;show = diagbus;show diag;show module;show c7200;show vtp status;show vlan;write = term it logs in properly and begins running commands. When it gets to "write = term" it begins printing it out but then hangs (the exact point at which = it hangs varies with each run). The do-diffs script (which also runs = the above) hangs on several routers. I am running Rancid 2.1 and have had no issues until the past week or = so. I am using both SSH and telnet as my connection methods... Thanks! David LaPorte From mhyde at escape.ca Mon Sep 24 14:57:03 2001 From: mhyde at escape.ca (Mike Hyde) Date: Mon, 24 Sep 2001 09:57:03 -0500 Subject: Rancid hangs In-Reply-To: <014d01c142e2$a9defd50$c9d16780@navajo> Message-ID: Have you upgraded expect latley? I had the same problem, and it turned out that the version of expect caused it to hang. There was a patch posted on this list, I have attacked it below: disclaimer: i am not at all sure that this is the proper way to fix this problem (where rancid's *logins hang while collecting info from devices on linux platforms with tcl8.3* and expect 5.32*) or if it will have adverse affects on other expect scripts. what is happening (usually amid write term or show config, cisco-ism or juniper-ism) is the last chunk of data before the prompt has been read into the internal ("channel") buffer, expect asks for more data, but instead of tcl reading from the buffer or checking if the file descriptor is actually ready for reading, it just calls read() via expect's ExpInputProc() where it hangs with the router waiting for input (until the router's session-timeout expires). i believe this is due to Tcl_WaitForEvent() not differentiating properly between timeout and "ready_for_read", but i did not unwrap the maze of callbacks within tcl and don't have time to right now. the (inefficient) patch below makes sure the filedescriptor is set non-blocking, so the read will return immediately if the FD is not ready for reading and thus give the tcl timer functions the opportunity to timeout an operation (and apparently look at the internal buffer for more data). i have no idea why this doesnt happen/affect netbsd. it works for me with tcl8.3.b2 and expect 5.32.1 on the linux box i have freewill-access to, or at least do-diffs completed flawlessly 4 times, whereas before it barely even got out of the gate. i think this is RedCrap 6.1 or so...uname says Linux 2.2.16-22, but i'm guessing that's just the kernel and i'm blissfully unaware of where all the other version info is hidden. you'll have to apply this to your expect 5.32.1 source; cd expect-5.32; patch < patchfile; make install - - - - - - - - - - - - - c u t h e r e - - - - - - - - - - - - - - *** exp_chan.c.FCS Tue Aug 14 16:55:54 2001 --- exp_chan.c Tue Aug 14 16:59:25 2001 *************** *** 119,124 **** --- 119,125 ---- * nonblocking, the read will never block. */ + fcntl(esPtr->fdin, F_SETFL, O_NONBLOCK); bytesRead = read(esPtr->fdin, buf, (size_t) toRead); /*printf("ExpInputProc: read(%d,,) = %d\r\n",esPtr->fdin,bytesRead);*/ if (bytesRead > -1) { From heas at shrubbery.net Tue Sep 25 15:18:42 2001 From: heas at shrubbery.net (john heasley) Date: Tue, 25 Sep 2001 08:18:42 -0700 Subject: Rancid hangs In-Reply-To: ; from mhyde@escape.ca on Mon, Sep 24, 2001 at 09:57:03AM -0500 References: <014d01c142e2$a9defd50$c9d16780@navajo> Message-ID: <20010925081842.A18462@shrubbery.net> note that patch(1) might get confused with the spacing below. you can see the correct spacing on www.shrubbery.net/rancid. Mon, Sep 24, 2001 at 09:57:03AM -0500, Mike Hyde: > Have you upgraded expect latley? I had the same problem, and it turned out > that the version of expect caused it to hang. There was a patch posted on > this list, I have attacked it below: > > disclaimer: i am not at all sure that this is the proper way to fix > > this problem (where rancid's *logins hang while collecting info from > > devices on linux platforms with tcl8.3* and expect 5.32*) or if it > > will have adverse affects on other expect scripts. > > what is happening (usually amid write term or show config, cisco-ism > > or juniper-ism) is the last chunk of data before the prompt has been > > read into the internal ("channel") buffer, expect asks for more data, > > but instead of tcl reading from the buffer or checking if the file > > descriptor is actually ready for reading, it just calls read() via > > expect's ExpInputProc() where it hangs with the router waiting for > > input (until the router's session-timeout expires). > > i believe this is due to Tcl_WaitForEvent() not differentiating properly > > between timeout and "ready_for_read", but i did not unwrap the maze of > > callbacks within tcl and don't have time to right now. > > the (inefficient) patch below makes sure the filedescriptor is > > set non-blocking, so the read will return immediately if the FD > > is not ready for reading and thus give the tcl timer functions the > > opportunity to timeout an operation (and apparently look at the internal > > buffer for more data). i have no idea why this doesnt happen/affect netbsd. > > it works for me with tcl8.3.b2 and expect 5.32.1 on the linux box i have > > freewill-access to, or at least do-diffs completed flawlessly 4 times, > > whereas before it barely even got out of the gate. i think this is > > RedCrap 6.1 or so...uname says Linux 2.2.16-22, but i'm guessing that's > > just the kernel and i'm blissfully unaware of where all the other version > > info is hidden. > > you'll have to apply this to your expect 5.32.1 source; cd expect-5.32; > > patch < patchfile; make install > > - - - - - - - - - - - - - c u t h e r e - - - - - - - - - - - - - - > > *** exp_chan.c.FCS Tue Aug 14 16:55:54 2001 > > --- exp_chan.c Tue Aug 14 16:59:25 2001 > > *************** > > *** 119,124 **** > > --- 119,125 ---- > > * nonblocking, the read will never block. > > */ > > > + fcntl(esPtr->fdin, F_SETFL, O_NONBLOCK); > > bytesRead = read(esPtr->fdin, buf, (size_t) toRead); > > /*printf("ExpInputProc: read(%d,,) = %d\r\n",esPtr->fdin,bytesRead);*/ > > if (bytesRead > -1) { > > > > -----Original Message----- > From: owner-rancid-discuss at shrubbery.net > [mailto:owner-rancid-discuss at shrubbery.net]On Behalf Of David LaPorte > Sent: Friday, September 21, 2001 4:16 PM > To: rancid-discuss at shrubbery.net > Subject: Rancid hangs > > > Hi all, > > Has anyone seen behavior similar to the following? > > Recently, when querying our routers for configurations, clogin seems to > hang while downloading the configuration. For instance, running clogin > manually with the command-line: > > ./clogin -t 90 -c show version;show install active;show env all;show gsr > chassis;show boot;show bootvar;show variables boot;show flash;dir /all > nvram:;dir /all bootflash:;dir /all slot0:;dir /all disk0:;dir /all > slot1:;dir /all disk1:;show controllers;show controllers cbus;show > diagbus;show diag;show module;show c7200;show vtp status;show vlan;write > term > > it logs in properly and begins running commands. When it gets to "write > term" it begins printing it out but then hangs (the exact point at which it > hangs varies with each run). The do-diffs script (which also runs the > above) hangs on several routers. > > I am running Rancid 2.1 and have had no issues until the past week or so. > I am using both SSH and telnet as my connection methods... > > Thanks! > David LaPorte > > From ABochannek at yipes.com Tue Sep 25 22:47:13 2001 From: ABochannek at yipes.com (Alex Bochannek) Date: Tue, 25 Sep 2001 15:47:13 -0700 Subject: Proposed Extreme changes. Message-ID: <65988049D870C042BD59CF516556134A14D1E5@sfoexh01.yipes.com> I am finally getting around working on Rancid for Extreme and had some problems getting it to work. Here are my proposed changes: bash-2.03$ diff -c /opt/rancid-2.2b7/bin/clogin bin/clogin *** /opt/rancid-2.2b7/bin/clogin Thu Sep 13 17:37:40 2001 --- bin/clogin Tue Sep 25 15:40:22 2001 *************** *** 432,438 **** # If the prompt is (enable), then we are on a switch and the # command is "set length 0"; otherwise its "term length 0". # skip if its and extreme. ! if { [ string compare "extreme" "$prompt" ] } { if [ regexp -- ".*> .*enable" "$prompt" ] { send "set length 0\r" } else { --- 432,438 ---- # If the prompt is (enable), then we are on a switch and the # command is "set length 0"; otherwise its "term length 0". # skip if its and extreme. ! if { [ string compare "extreme" "$platform" ] } { if [ regexp -- ".*> .*enable" "$prompt" ] { send "set length 0\r" } else { *************** *** 501,507 **** } } log_user 1 ! send "exit\r" expect { "Do you wish to save your configuration changes" { send "n\r" --- 501,507 ---- } } log_user 1 ! send "quit\r" expect { "Do you wish to save your configuration changes" { send "n\r" bash-2.03$ diff -c /opt/rancid-2.2b7/bin/xrancid bin/xrancid *** /opt/rancid-2.2b7/bin/xrancid Thu Sep 13 17:38:01 2001 --- bin/xrancid Tue Sep 25 15:42:19 2001 *************** *** 330,342 **** print STDOUT "opening file $host\n" if ($log); open(INPUT,"<$host") || die "open failed for $host: $!\n"; } else { ! print STDERR "executing clogin -t $timeo -c\"$cisco_cmds\" $host\n" if ($debug); ! print STDOUT "executing clogin -t $timeo -c\"$cisco_cmds\" $host\n" if ($log); if (defined($ENV{NOPIPE})) { ! system "clogin -t $timeo -c \"$cisco_cmds\" $host $host.raw 2>&1" || die "clogin failed for $host: $!\n"; open(INPUT, "< $host.raw") || die "clogin failed for $host: $!\n"; } else { ! open(INPUT,"clogin -t $timeo -c \"$cisco_cmds\" $host $host.raw 2>&1" || die "clogin failed for $host: $!\n"; open(INPUT, "< $host.raw") || die "clogin failed for $host: $!\n"; } else { ! open(INPUT,"clogin -t $timeo -autoenable -c \"$cisco_cmds\" $host From morty at sanctuary.arbutus.md.us Wed Sep 26 01:52:27 2001 From: morty at sanctuary.arbutus.md.us (Mordechai T. Abzug) Date: Tue, 25 Sep 2001 21:52:27 -0400 Subject: brancid patch for uptime Message-ID: <20010925215227.A14536@red-sonja.sanctuary.arbutus.md.us> I'm running rancid 2.2b7 to get config info from Bay routers running assorted versions of BayRS. It works fine for the version 12 boxen, but the version 14 boxen include uptime info in the config. Here's a patch: *** brancid.dist Tue Sep 25 16:54:22 2001 --- brancid Tue Sep 25 21:14:40 2001 *************** *** 140,145 **** --- 140,146 ---- last if (/^$prompt/); next if (/^(\s*|\s*$cmd\s*)$/); next if (/^Reading configuration information/); + next if (/^\# *uptime +\d+\s*$/); if (/community label /) { if (defined($ENV{'NOCOMMSTR'})) { $_ =~ s/community label .*$/community label /; While poking in brancid, I noticed a comment that says there is no equivalent to enable for Bay routers. AFAIK, BayRS has a "system" command that lets you go from User to Manager. This doesn't seem to affect anything, though. - Morty From heas at shrubbery.net Thu Sep 27 18:58:47 2001 From: heas at shrubbery.net (john heasley) Date: Thu, 27 Sep 2001 11:58:47 -0700 Subject: Proposed Extreme changes. In-Reply-To: <65988049D870C042BD59CF516556134A14D1E5@sfoexh01.yipes.com>; from ABochannek@yipes.com on Tue, Sep 25, 2001 at 03:47:13PM -0700 References: <65988049D870C042BD59CF516556134A14D1E5@sfoexh01.yipes.com> Message-ID: <20010927115847.I18070@shrubbery.net> i havent had a chance to look at these. didnt want you to think we were ignoring you. Tue, Sep 25, 2001 at 03:47:13PM -0700, Alex Bochannek: > I am finally getting around working on Rancid for Extreme and had some > problems getting it to work. Here are my proposed changes: From ABochannek at yipes.com Thu Sep 27 20:00:50 2001 From: ABochannek at yipes.com (Alex Bochannek) Date: Thu, 27 Sep 2001 13:00:50 -0700 Subject: Proposed Extreme changes. Message-ID: <65988049D870C042BD59CF516556134A14D202@sfoexh01.yipes.com> OK, thanks ;-) Alex Bochannek Senior Unix/Network Engineer Yipes ... that's fast! (415) 901-2000 (415) 901-2090 (direct) www.yipes.com -----Original Message----- From: john heasley [mailto:heas at shrubbery.net] Sent: Thursday, September 27, 2001 11:59 AM To: Alex Bochannek Cc: 'rancid-discuss at shrubbery.net' Subject: Re: Proposed Extreme changes. i havent had a chance to look at these. didnt want you to think we were ignoring you. Tue, Sep 25, 2001 at 03:47:13PM -0700, Alex Bochannek: > I am finally getting around working on Rancid for Extreme and had some > problems getting it to work. Here are my proposed changes: From ABochannek at yipes.com Sat Sep 29 00:34:11 2001 From: ABochannek at yipes.com (Alex Bochannek) Date: Fri, 28 Sep 2001 17:34:11 -0700 Subject: Proposed Extreme changes. Message-ID: <65988049D870C042BD59CF516556134A14D20F@sfoexh01.yipes.com> One thing I need to know is what the largest number of devices is anybody uses Rancid for. Tens? Hundreds? Considering how long it can take for telnet to terminate an unsuccessful connection (on Solaris), I am bit worried about scalability. Thanks. Alex Bochannek Senior Unix/Network Engineer Yipes ... that's fast! (415) 901-2000 (415) 901-2090 (direct) www.yipes.com -----Original Message----- From: john heasley [mailto:heas at shrubbery.net] Sent: Thursday, September 27, 2001 11:59 AM To: Alex Bochannek Cc: 'rancid-discuss at shrubbery.net' Subject: Re: Proposed Extreme changes. i havent had a chance to look at these. didnt want you to think we were ignoring you. Tue, Sep 25, 2001 at 03:47:13PM -0700, Alex Bochannek: > I am finally getting around working on Rancid for Extreme and had some > problems getting it to work. Here are my proposed changes: From heas at shrubbery.net Sat Sep 29 00:38:58 2001 From: heas at shrubbery.net ('john heasley') Date: Sat, 29 Sep 2001 00:38:58 +0000 Subject: Proposed Extreme changes. In-Reply-To: <65988049D870C042BD59CF516556134A14D20F@sfoexh01.yipes.com>; from ABochannek@yipes.com on Fri, Sep 28, 2001 at 05:34:11PM -0700 References: <65988049D870C042BD59CF516556134A14D20F@sfoexh01.yipes.com> Message-ID: <20010929003857.G7146@shrubbery.net> Fri, Sep 28, 2001 at 05:34:11PM -0700, Alex Bochannek: > One thing I need to know is what the largest number of devices is anybody > uses Rancid for. Tens? Hundreds? Considering how long it can take for telnet > to terminate an unsuccessful connection (on Solaris), I am bit worried about > scalability. have seen as many as 700. bin/control_rancid:PAR_COUNT=5 could be raised to process more devices concurrently. that should really be a bin/env knob; which i'll add to the todo list. > Thanks. > > Alex Bochannek > Senior Unix/Network Engineer > Yipes ... that's fast! > (415) 901-2000 > (415) 901-2090 (direct) > www.yipes.com > > > -----Original Message----- > From: john heasley [mailto:heas at shrubbery.net] > Sent: Thursday, September 27, 2001 11:59 AM > To: Alex Bochannek > Cc: 'rancid-discuss at shrubbery.net' > Subject: Re: Proposed Extreme changes. > > i havent had a chance to look at these. didnt want you to think we > were ignoring you. > > Tue, Sep 25, 2001 at 03:47:13PM -0700, Alex Bochannek: > > I am finally getting around working on Rancid for Extreme and had some > > problems getting it to work. Here are my proposed changes: From ABochannek at yipes.com Sat Sep 29 00:39:55 2001 From: ABochannek at yipes.com (Alex Bochannek) Date: Fri, 28 Sep 2001 17:39:55 -0700 Subject: Proposed Extreme changes. Message-ID: <65988049D870C042BD59CF516556134A14D210@sfoexh01.yipes.com> Good data point. Thanks! Alex Bochannek Senior Unix/Network Engineer Yipes ... that's fast! (415) 901-2000 (415) 901-2090 (direct) www.yipes.com -----Original Message----- From: 'john heasley' [mailto:heas at shrubbery.net] Sent: Friday, September 28, 2001 5:39 PM To: Alex Bochannek Cc: 'john heasley'; 'rancid-discuss at shrubbery.net' Subject: Re: Proposed Extreme changes. Fri, Sep 28, 2001 at 05:34:11PM -0700, Alex Bochannek: > One thing I need to know is what the largest number of devices is anybody > uses Rancid for. Tens? Hundreds? Considering how long it can take for telnet > to terminate an unsuccessful connection (on Solaris), I am bit worried about > scalability. have seen as many as 700. bin/control_rancid:PAR_COUNT=5 could be raised to process more devices concurrently. that should really be a bin/env knob; which i'll add to the todo list. > Thanks. > > Alex Bochannek > Senior Unix/Network Engineer > Yipes ... that's fast! > (415) 901-2000 > (415) 901-2090 (direct) > www.yipes.com > > > -----Original Message----- > From: john heasley [mailto:heas at shrubbery.net] > Sent: Thursday, September 27, 2001 11:59 AM > To: Alex Bochannek > Cc: 'rancid-discuss at shrubbery.net' > Subject: Re: Proposed Extreme changes. > > i havent had a chance to look at these. didnt want you to think we > were ignoring you. > > Tue, Sep 25, 2001 at 03:47:13PM -0700, Alex Bochannek: > > I am finally getting around working on Rancid for Extreme and had some > > problems getting it to work. Here are my proposed changes: