We really can't do that approach here. The issue is that one a host is using the offline alias, it runs other processes and we want to keep track of the stats of a machine going back to the day it was added. Having good tracking and knowing that a host is healthy saves a bunch of time in the event of an outage and we can restore service confidently that the offline host is not in a bad state. I have seen offline hosts at another job that when switched to the online host cause more of a problem then the origional issue because a script had a memory leak and activating the rest of the processes killed the server. It was almost the same bad mojo as releasing a fork() bomb on the server. We want to be aware of the state of all our hosts at any given moment.
-------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=27050#27050 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
