All,

        We are preparing to roll mon into our production environment. There is 
still a few things 
that I need to prove to get the higher-ups approval. How are most of you 
managing planned system 
downtime? Looking into the scripts it appears that mon has been designed more 
to load the mon.cf
file at startup and stays with it. Is the preferred way to remove and/or add a 
host to add it to
the config file and restart mon? Or am I missing a feature to have mon check 
it's configuration 
file and reload if it changes?


Thanks all,

-- 
Michael Osburn
[EMAIL PROTECTED]
Engineer I
Conditional Access Systems
EchoStar Operating Corp.

------------

This e-mail and its attachments is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. Any review, retransmission, 
dissemination or other use of, or taking of any action in 
reliance upon, this information by persons or entities other than 
the intended recipient is prohibited. 
If you received this in error, please contact the sender and 
delete the material from any computer.

_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon

Reply via email to