mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #423] firejail shutdown does not pass SIGNAL to children #307
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#307
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pyther on GitHub (Apr 9, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/423
I'm testing against git.
When I run
firejail ./catchsignal.shand thenfirejail --shutdown ./catchsignal.shI would expect my shell script would receive a SIGTERM, but that does not appear to be the case.I have a simple shell script to demo straight this issue.
In this first example, I run the script with firejail, I kill the bash process and 'Caught Signal' is printed to the screen.
When I
firejail --shutdownthe script does not echo Caught Signal. Firejail shows it issues a SIGTERM and then 2 seconds later a SIGKILL. Also the output shows that I can not shutdown the jail as my user, even thought I created it as a user.@netblue30 commented on GitHub (Apr 10, 2016):
Definitely a bug, thanks!
@netblue30 commented on GitHub (Apr 12, 2016):
Fixed on the master branch.
@pyther commented on GitHub (Apr 13, 2016):
Thanks. When I built the latest git HEAD gcc had the following warning
Just wanted to give you a heads up as it seems directly related to this fix.
bb4830eb7e (diff-666cee54353ff0c7dfb4c7eb2933f273R37)@netblue30 commented on GitHub (Apr 14, 2016):
Fixed, thanks.