A user asked how to monitor a service and stop it if it is detected as "Running". Another user suggested using the process name and creating a trigger with a script action to kill the process and stop the service. They also mentioned a cu script that can look into svchost, but it may not be able to be modified for this purpose. It was also mentioned that the system will not allow direct killing of svchost. The user will check if the service creates an event log and if it does, they can create a trigger and run a script action. The thread includes a few humorous responses as well.
Read the entire ‘How to Monitor and Stop Running Services in ControlUp’ thread below:
Hello Folks!
Quick question… I’m sure its been asked before but I couldn’t find the answer. Looking to monitor a service or two and then if they are detected as "Running" then stop them. Currently I only see the option to trigger based off of stopped or not configured. Would I just need to use the process name instead?
Of the service starts dose it start and process that u can see within controlup. If yes than create a trigger with a script action to kill the process and stop the service.
unfortunately, looks like they run under the svchost.exe. I could kill that… what could go wrong? 😉
I know there is a cu script that let’s u look in to svchost but not sure it can be modified to kill a process
System will not let u kill svchost direct as it is a protect system process
yeah, was kidding anyway re svchost
Hehe
if the service starts dose it create an event log?
I’ll have to check. I know that it creates an event when it changes from disabled to manual start. I’ll have to look for other events.
If it is application or system event u can also create a trigger and run a script action
If information u out of luck
trigger on if not stopped?
:mindblown:
Continue reading and comment on the thread ‘How to Monitor and Stop Running Services in ControlUp’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers