Peter Glanville wrote: >Stopping and restarting Routers2.cgi is pointless and impossible. Actually, this is not always the case...
If you are using speedycgi, or mod_perl, to speed up the running of routers2 under unix (and it makes a *big* difference on large installations), then it will cache the .cfg definitions in memory for the duration of the perl thread. This means that, every time you change the .cfg files, you need to either wait for the threads to expire (a few hours?) or touch the routers2.cgi file (to force a thread reload). If you don't use mod_perl or speedycgi, then you are quite correct -- there is nothing to stop and restart and it is indeed impossible and pointless. Steve --- Steve Shipway: ITSS, University of Auckland Email: [EMAIL PROTECTED] Web: http://www.steveshipway.org/ ** We can only discover new oceans when we have the ** ** courage to lose sight of the shore. ** -- Attached file removed by Ecartis and put at URL below -- -- Type: text/x-vcard -- Size: 155 bytes -- URL : http://www.ee.ethz.ch/~slist/p/50-Steve%20Shipway.vcf -- Unsubscribe mailto:[EMAIL PROTECTED] Archive http://www.ee.ethz.ch/~slist/mrtg FAQ http://faq.mrtg.org Homepage http://www.mrtg.org WebAdmin http://www.ee.ethz.ch/~slist/lsg2.cgi
