Yes there is.  I don't have the info handy, but it is in the MRTG docs.  I use 
it to do exactly what you are trying. 
1. Create new config file.
2. Use MRTG to test the file.
3. If bad, send me an alert and run the existing config.
4. If good, copy config over old one and run it.

This happens every 5 min.  I always have an up to date config file.


HTH

-----Original Message-----
   >From: "Pete Templin" <[EMAIL PROTECTED]>
   >Sent: 5/13/04 1:50:59 PM
   >To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
   >Subject: [mrtg] command line switch to just verify config syntax?
   >
   >List,
   >
   >Is there any easy way to run MRTG but only verify if the syntax of the 
   >config file is clean?  In conjunction with automating the generation of 
   >my config files, I'd like to add a verification step so I don't 
   >accidentally overwrite a good config file with a buggy config file.
   >
   >TIA,
   >
   >pt
   >
   >--
   >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
   >
   >


-- Attached file removed by Ecartis and put at URL below --
-- Type: application/ms-tnef
-- Size: 2k (2389 bytes)
-- URL : http://www.ee.ethz.ch/~slist/p/40A5782210077-winmail.dat


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

Reply via email to