Re: mktop not giving node records

On Tuesday, Apr 22, 2003, at 23:41 Canada/Eastern, Stephen Miller wrote:

> 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::::::

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 some=20
stale, maybe truncated "*.in" files lying about.

Try running mktop like this and see what you get:

./mktop $(awk -F: '/:up:/ { printf=20
"/usr/local/rancid/core/configs/%s\n", $1; }' \
   /usr/local/rancid/core/router.db) >net2.top

(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 should=20
contain reasonable food for mktop.


Joe