Forum Discussion
Better solution for the OVRService to restart if failed:
Why not simply use NSSM (http://nssm.cc/) the the Non-Sucking Service Manager? I's open source, simple to use and it works way better than this LaunchAndRestart.vbs which is used as a fallback for now.
I can't describe it better than the website does itself:
nssm is a service helper which doesn't suck. srvany and other service helper programs suck because they don't handle failure of the application running as a service. If you use such a program you may see a service listed as started when in fact the application has died. nssm monitors the running service and will restart it if it dies. With nssm you know that if a service says it's running, it really is. Alternatively, if your application is well-behaved you can configure nssm to absolve all responsibility for restarting it and let Windows take care of recovery actions.
Most of the tracking problems now are simply because the service has died and the script failed to restart it. Please give it a try.
spyro
I can't describe it better than the website does itself:
nssm is a service helper which doesn't suck. srvany and other service helper programs suck because they don't handle failure of the application running as a service. If you use such a program you may see a service listed as started when in fact the application has died. nssm monitors the running service and will restart it if it dies. With nssm you know that if a service says it's running, it really is. Alternatively, if your application is well-behaved you can configure nssm to absolve all responsibility for restarting it and let Windows take care of recovery actions.
Most of the tracking problems now are simply because the service has died and the script failed to restart it. Please give it a try.
spyro
No RepliesBe the first to reply