Open brianehlert opened 9 years ago
On Raspberry pie starting the gateblu-service using "sudo service gateblu-service start" works just fine. The stop silently fails.
Recently working through a different node.js app my solution was to change the way the app launched so that the kill could properly find it. This: http://stackoverflow.com/questions/22108317/stopping-nodejs-service-does-not-kill-node-process-when-wrapped-in-script-comm article tipped me off to the child process spawning that I was dealing with.
I don't know if the issue here is the same.
My init script is: https://gist.github.com/brianehlert/4cbf43edb5410f82a320
On Raspberry pie starting the gateblu-service using "sudo service gateblu-service start" works just fine. The stop silently fails.
Recently working through a different node.js app my solution was to change the way the app launched so that the kill could properly find it. This: http://stackoverflow.com/questions/22108317/stopping-nodejs-service-does-not-kill-node-process-when-wrapped-in-script-comm article tipped me off to the child process spawning that I was dealing with.
I don't know if the issue here is the same.
My init script is: https://gist.github.com/brianehlert/4cbf43edb5410f82a320