PK
7C̶{T _rels/.rels ( PK 7C$ $ NSSM.nuspec ( uTMo6KLshB (v(=Ę*ڍ}n09|ޛGv>{gJlcx{{?t3 d7)gL䑕&ECV&z07>3[tZ~FvQ=w'"}tVݎ⒧xBYc%1Ew-9Od͍1W{@7J~]4յc^lCs`8cw$;b\ =\&kqxCVCwgDs-g209T`&9nIqCyv`i ()8
@OZeҕg9S_@8c*?/hNR[T;|6kNh./9HTP+i)^B֚1,G^ $BVNݙ29wLEaig0dec;gl^aiRD
Q _Hpi%2QDnnjjX-*B(6/DG؞_DT-B~-0f\B#%辸mtnC,x CA+ߋygK[O,)Nka |q䷏'VJu2ŋ[^]-
YP \ڒV)w$fB
iz\^$qȉNcY3鮽tPK 7CR Tools/ChocolateyInstall.ps1 ( ]
0@wPTۑF{4PK
IN$KGOv dr@9.r^uBĎ/WL^5s{;7F5H:ZhEa]UުPK
7C
Q package/services/metadata/core-properties/5fd37e4c674044d69ac12957b8ee3385.psmdcp ( Iain Pattersonnssm 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.
nssm logs its progress to the system Event Log so you can get some idea of why an application isn't behaving as it should.
nssm also features a graphical service installation and removal facility. Admittedly this does suck. I hate trying to make GUIs...NSSM2.16.0nssm servicePK
7CUd, [Content_Types].xml ( PK-
7C̶{T _rels/.relsPK- 7C$ $ . NSSM.nuspecPK- 7CR Tools/ChocolateyInstall.ps1PK-
7C
Q l package/services/metadata/core-properties/5fd37e4c674044d69ac12957b8ee3385.psmdcpPK-
7CUd, [Content_Types].xmlPK {