Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npx exec processes are left running after foreman exits #810

Open
davetron5000 opened this issue Nov 12, 2024 · 0 comments
Open

npx exec processes are left running after foreman exits #810

davetron5000 opened this issue Nov 12, 2024 · 0 comments

Comments

@davetron5000
Copy link

web: PORT=6502 bin/run
sidekiq: bin/run-sidekiq
css: SHELL=/bin/bash npx chokidar --initial -p "app/src/front_end/css/**/*"    -c "bin/build-assets css"
js: SHELL=/bin/bash npx chokidar --initial -p "app/src/front_end/js/**/*"     -c "bin/build-assets js"
images: SHELL=/bin/bash npx chokidar --initial -p "app/src/front_end/images/**/*" -c "bin/build-assets images"

When I Ctrl-C foreman, bin/dev (and whatever it starts) and bin/run-sidekiq (and whatever it starts) terminate normally. The other commands do not and remain running.

When trying those on the command line, they do terminate when given SIGTERM. What's interesting is that Ctrl-C does exit those, but using KILL -INT does not.

Any ideas how to debug what is going on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant