Does forever support binary executable monitoring?
See original GitHub issueDoes forever support binary executable monitoring? If yes, then how to monitor compiled c file executable. since it don’t need “COMMAND to execute” as suggested in options.
-c COMMAND COMMAND to execute (defaults to node)
Thanks. -Bhavesh
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Does forever support binary executable monitoring? #800
Does forever support binary executable monitoring? If yes, then how to monitor compiled c file executable. since it don't need "COMMAND to ...
Read more >Overwriting a running executable or .so - Unix Stack Exchange
No, current solaris does not implement any such "protection ". Both overwriting a running executable and executing a file already opened for ...
Read more >Run any Executable as Systemd Service in Linux | by Abhinand
There are multiple ways of doing this — keeping it running forever. But in this article, I'll cover a standard Linux way of...
Read more >How do I audit an executable to make sure it is not malicious?
A clever malicious binary may be able to detect that it is under observation and not perform malicious actions except when it is...
Read more >Is it possible to extend Icinga2 (Windows) with a custom check ...
Background: I have a Windows based application and want to Monitor this applications state. It would be easy to create a check_my_app_health.exe ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
One work-around is to wrap your binary in a simple shell script that just runs main.
forever start -o ./logs/out.log -e ./logs/err.log -c /bin/bash run-main.sh
Your shell script might look like
The
exec
causes the command being run to take over bash’s process rather than spawning a child. This is necessary so thatforever stop
kills your program rather than killing the parent bash script and leaving the orphaned child process running.When I run forever start iotgo,I got this error as following: (function (exports, require, module, __filename, __dirname) { # !/bin/bash
SyntaxError: Unexpected token ILLEGAL at exports.runInThisContext (vm.js:53:16) at Module._compile (module.js:373:25) at Object.Module._extensions…js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) at Function.Module.runMain (module.js:441:10) at startup (node.js:139:18) at node.js:968:3
npm: 2.15
node:4.4.2
forever:0.15.1