mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #431] Increase delay before issuing SIGKILL on shutdown? #313
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#313
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 13, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/431
Would it be possible to increase the time that is waited before sending a SIGTERM on shutdown?
I have an application that may need to write data to disk when it receives a SIGTERM. The current value of 2 seconds seems low and may not give an application enough to gracefully shutdown. There does not appear to be a standard on how long to wait after sending a SIGTERM, but systemd waits 10 seconds after SIGTERM before issuing additional signals.
#define TIMEOUT_USEC (10 * USEC_PER_SEC)until = now(CLOCK_MONOTONIC) + TIMEOUT_USEC;https://github.com/systemd/systemd/blob/master/src/core/killall.c#L36
Would it be possible to send a SIGTERM and then loop every 0.5 second or so checking to see if the children have died, sending a SIGTERM after 10 seconds?
https://stackoverflow.com/questions/27570302/how-much-time-before-sigkill
@netblue30 commented on GitHub (Apr 13, 2016):
I'll bring something in soon, thanks!
@netblue30 commented on GitHub (Apr 14, 2016):
Fixed in main branch.