[GH-ISSUE #592] Kill the jailed process by a timer #417

New issue

Closed

opened 2026-05-05 05:49:15 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:49:15 -06:00

Owner

Originally created by @vporton on GitHub (Jun 24, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/592

I propose to kill the jailed process after the specified (by the command line) number of seconds (or better milliseconds) passes.

This is useful, as otherwise a hacked may make a command running forever.

Originally created by @vporton on GitHub (Jun 24, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/592 I propose to kill the jailed process after the specified (by the command line) number of seconds (or better milliseconds) passes. This is useful, as otherwise a hacked may make a command running forever.

gitea-mirror

2026-05-05 05:49:15 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 05:49:22 -06:00

Author

Owner

@reinerh commented on GitHub (Jun 24, 2016):

Is the timeout command on the command line not sufficient?

@reinerh commented on GitHub (Jun 24, 2016): Is the `timeout` command on the command line not sufficient?

gitea-mirror commented

2026-05-05 05:49:24 -06:00

Author

Owner

@netblue30 commented on GitHub (Jun 26, 2016):

Use timeout, it will work.

@netblue30 commented on GitHub (Jun 26, 2016): Use timeout, it will work.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#417

No description provided.

Rows
Columns