If planned to update the nslient++ on all of our servers. Should I activate the WMI option in the nsc.ini file (maybe of future usage) or can my system make trouble due to activating this?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Uhmm, well as with all free software I wont leave any guarantees.
But as the WMI module is "passive" it does nothing unless you ask it to do something so even if it was really horribly buggy and crashes it would only do so whenever you ask queries from it so unless you do that "it" should be perfectly stable.
As for the stability it is not 100% well written so it is likely "unstable" but I wouldn't expect it to crash that much, more along the lines of returning incorrect things when you ask strange queries from it, as I dont do error checks and such properly at the moment. But that will come when I have decided what to do with the module.
// MickeM
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've been reading your short tutorial on WMICheck - any Chance Mike you could share a nice-simple & clear example of a passive setup, including configs(scheduler, etc)?
I've failed to understand the inner-working, inasmuch I have successfully set up other passive checks you mentioned in your epubs I was unable to setup WMIcheck passively.
regards
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Is there a way with wmi to check that a installed service is both NOT running and set to manual startup?
currently I have a Business Objects cluster, and have a active/passive set of nodes, and won`t to monitor the passive side to make sure none of the services are running and are set to manual startup?
Thanks
John
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello..
I think the WMI module is a great idea, i have not personally tested it, but i cant wait..
thanks
g
If planned to update the nslient++ on all of our servers. Should I activate the WMI option in the nsc.ini file (maybe of future usage) or can my system make trouble due to activating this?
Uhmm, well as with all free software I wont leave any guarantees.
But as the WMI module is "passive" it does nothing unless you ask it to do something so even if it was really horribly buggy and crashes it would only do so whenever you ask queries from it so unless you do that "it" should be perfectly stable.
As for the stability it is not 100% well written so it is likely "unstable" but I wouldn't expect it to crash that much, more along the lines of returning incorrect things when you ask strange queries from it, as I dont do error checks and such properly at the moment. But that will come when I have decided what to do with the module.
// MickeM
I've been reading your short tutorial on WMICheck - any Chance Mike you could share a nice-simple & clear example of a passive setup, including configs(scheduler, etc)?
I've failed to understand the inner-working, inasmuch I have successfully set up other passive checks you mentioned in your epubs I was unable to setup WMIcheck passively.
regards
okay. thanks for the detailed info.
i've activated it, so i can easy use it in future.
Is there a way with wmi to check that a installed service is both NOT running and set to manual startup?
currently I have a Business Objects cluster, and have a active/passive set of nodes, and won`t to monitor the passive side to make sure none of the services are running and are set to manual startup?
Thanks
John