Re: mktop not giving node records

actually the reason I use the *.in (.in being the TLD for the=20
hostnames...calccrc1.rdn.ric.net.in) is that mktop stops when it hits the=
 CVS=20
directory in the configs directory and then creates and empty .top file.

tried the command and it just hung...I think it's also getting stopped by=
 the=20
CVS directory but there error is not coming to the terminal.

Has the CVS directory always been in the rancid/group/ directory?=20

thanks,
Steve

---------- Original Message -----------
From: Joe Abley <[email protected]>
To: "Stephen Miller" <[email protected]>
Cc: [email protected]
Sent: Wed, 23 Apr 2003 01:59:54 -0400
Subject: Re: mktop not giving node records

> On Tuesday, Apr 22, 2003, at 23:41 Canada/Eastern, Stephen Miller wrote=
:
>=20
> > like this:
> >
> > cat /usr/local/rancid/core/configs/*.in | ./mktop > net.top
> >
> > and like this:
> >
> > ./mktop /usr/local/rancid/core/configs/*.in > net1.top
> >
> >
> > same out output for both....
> >
> > node::::::
>=20
> Mmmm. I think that files named "*.in" in the configs directory are=20
> transient files that rancid uses while it grabs new state from the=20
> network, and subsequently renames to their non-.in counterparts. You=20
> may find that those files are either not always there, or you have=20
> some stale, maybe truncated "*.in" files lying about.
>=20
> Try running mktop like this and see what you get:
>=20
> ./mktop $(awk -F: '/:up:/ { printf=20
> "/usr/local/rancid/core/configs/%s\n", $1; }' \
>    /usr/local/rancid/core/router.db) >net2.top
>=20
> (if you're a csh person you'll need to use back-ticks instead of the=20
> $() notation). That expression should spit out a list of config files=20
> corresponding to devices in the "core" group which are up, which=20
> should contain reasonable food for mktop.
>=20
> Joe
------- End of Original Message -------