-
Notifications
You must be signed in to change notification settings - Fork 510
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
SIGHUP seems to not be propagated to inner child processes #1781
Comments
I'm also experiencing this when using just to launch tasks inside of zellij. I would love to see a fix for this. For now I'm going to have to adjust my zellij layout to launch the commands directly instead of using just. Hopefully can migrate back soon. |
I've also ran into this and it's not ideal. I'd be great to have a fix/option for this. |
Closing in favor of #2473, where I tried to collect everything related to signal handling in one place. I'm not able to reproduce processes being left behind when Currently, |
Howdy! First of all, I am a recent
just
convert and I am loving it. Thanks for all the work into this amazing tool.I have been using a mix of
just
andzellij
to handle some of my workflows, and noticed that when I close azellij
pane running ajust
recipe it leaves the process alive.Summary: It seems that a SIGHUP signal is being sent to
just
, but that signal is not being propagated to the inner child process, which causes the whole process tree to be left alive.Here is a basic way to reproduce this issue using a simple bash script:
just --version
sighup.sh
justfile
Problematic behaviour:
Expected behaviour:
Happy to contribute a fix for this, but wanted to check in first if this is something worth fixing, or is it an expected behaviour? Also, any pointers on where to look for would be appreciated.
The text was updated successfully, but these errors were encountered: