NSSM – The Non-Sucking Service Manager

nssm.cc

13 pointsbdon6 comments

Any service-lizing wrapper should not be restarting underlying application on failure, because there's a standard built-in Windows mechanism for that, properly integrated with the rest of the system. The wrapper merely needs to log the incident.

See ChangeServiceConfig2, SERVICE_CONFIG_FAILURE_ACTIONS - https://msdn.microsoft.com/en-us/library/windows/desktop/ms6...

> Any service-lizing wrapper should not be restarting underlying application on failure...

From the frontpage:

"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."

I know very little about Windows Service management, but it sounds like there are certain poorly behaved services that do the wrong thing when they fail. It's always nice to give competent sysadmins the tools required to make poorly-designed software behave correctly.

If you find a service like that, you can probably just go into services.msc and change the Recovery settings for the service.

When it comes time to upgrade the service, do the changes you made override whatever the service's installer decides to do?

Very useful, isn't it R.Barbosa? ;)

Very useful indeed :)

Reply on news.ycombinator.com