automating non-config actions?
avram at juniper.net
Sat Jan 12 22:39:28 UTC 2002
I did see that. -s will cover the arbitrary script task I've suggested.
The grouping and parallel processing done by do-diffs, control_rancid,
and par, look like they would need to be hacked to support the -s option
of the *login scripts, with the more flexible batch functionality that
they provide, rather than manually listing every router using *login -r.
But a lot of the checking & emailing control_rancid does sort of doesn't
make sense to do for non-config collecting, or in an interactive
My apologies for not really specifying my intent clearly.
> -----Original Message-----
> From: Andrew Partan [mailto:asp at partan.com]
> Sent: Saturday, January 12, 2002 5:07 PM
> To: Avram Dorfman
> Cc: rancid-discuss at shrubbery.net
> Subject: Re: automating non-config actions?
> On Sat, Jan 12, 2002 at 01:05:50PM -0800, Avram Dorfman wrote:
> > Has anyone thought about modifying rancid to make it a batch
> > utility for executing arbitrary actions on lots of routers?
> Look at clogin - its already does a lot of what you want.
More information about the Rancid-discuss