You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes a running program fails because of the panic. Because CompileDaemon keeps running it is hard to notice that (except for the panic stack trace). I think it would be best if CompileDaemon would just restart the program, with some message (like, "program terminated, restarting"). Probably as opt-in CLI flag.
If you need more sophisticated job management I would recommend using a shell script that launches the executable and watches for the actual program. A very simple one would be something like
#!/bin/bashwhiletrue;do
./my_go_executable "$@"
sleep 5 # avoid flooding the system with crashing applicationsdone
Activity
[-]Restart the program if if fails[/-][+]Restart the program if it fails[/+]githubnemo commentedon Jun 6, 2022
If you need more sophisticated job management I would recommend using a shell script that launches the executable and watches for the actual program. A very simple one would be something like
I don't think this is a job for
CompileDaemon:)Set pgid and kill the process group on posix
asalkeld commentedon Aug 4, 2022
I have a commit on a fork that does this: asalkeld@238f1e6
If you are interested, I'll happily make a PR.