your output is expected behavior. jlogin is just an expect script that logs into the devices.
if you're configuration is complete (with cron job/etc and you just want to test you can run the following /blah/blah/rancid/bin/rancid-run to run rancid -ck On Thu, Jul 15, 2010 at 4:53 PM, Stefan Schlesinger <s...@ono.at> wrote: > Hello Folks, > > I'm trying to get RANCID to work with jlogin on my SRX100. I > configured my router.db and .cloginrc. The following command > can login to the router, but it doesn't backup anything. > > $ bin/jlogin -f .cloginrc 192.168.0.13 > > > I'm running rancid 2.3.3, and here are my configuration files: > > .cloginrc > add password 192.168.0.* pwdstring > add user 192.168.0.* rancid > add method 192.168.0.* {ssh} > -- > > var/noc/router.db: > 192.168.0.13:juniper:up > -- > > The following happens when i run the command line from above: > > > $ bin/jlogin -f .cloginrc 192.168.0.13 > spawn ssh -c 3des -x -l rancid 192.168.0.13 > ran...@192.168.0.13's password: > --- JUNOS 10.1R3.7 built 2010-07-10 08:32:02 UTC > ran...@juniper-01> > > ran...@juniper-01> > > > > Maybe someone on the list could provide me with some advice on how > to get that working. > > Regards, Stefan. > > -- > Stefan Schlesinger ////////////////////////////////////////// /////// > s...@ono.at > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp