5 ms·
NSSM – The Non-Sucking Service Manager
- eps 11y agoAny 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/ms685939(v=vs.85).aspx https://msdn.microsoft.com/en-us/library/windows/desktop/ms6...
- simoncion 11y ago> 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.
- vmateixeira 11y agoVery useful, isn't it R.Barbosa? ;)
- rafaelbarbosa 11y agoVery useful indeed :)