Cheshire Cat Computing

I have 2 questions and hopefully they havent already been asked and answered (or else I havent read the docs very well )

1. When routers2.cgi is told to rgaph a target from a non-existing cfg file,
it picks up a random (?) cfg/target and displays it. How can I disable that feature? There ae cases where I'drather see an error message.

2. I'm using the "cache = yes" option. My question is: how often does this cache expire? Is there any way to override that? (apart from manually removing things from the cache)

1) If routers2 gets invalid parameters (eg, a non-existing cfg file) then it will act as if no parameter at all was given -- and pick the first available. This currently cannot be disabled.

2) The cache never expires (I assume you mean the cfg file caching used when you have mod_perl or speedycgi). However, with speedycgi, you should set the threads to restart every few hours or every few hundred invocations, which will cause the cache to reload (on that thread). I think mod_perl will do something similar. The suggested speedycgi parameters in the routers2.cgi file are set for this.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

thanks for the info Steve!

any plans on changing the "invalid target/cfg file" behavior?

I wasn'r planning on changing the default behaviour, since the code makes a lot of assumptions that it has valid parameters once it passes the initial sanity check. I might be able to make an option on choosing the default, though, to have 'none' as an option (currently, you can set defaultinterface in the routers2.conf but not to 'none'). Maybe I can add a 'none' default option, and also add a defaultrouter option to specify a default .cfg file (which could also be 'none')?

Steve

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11