In Linux I would like to run a program but only for a limited time, like 1 second. If the program exceeds this running time I would like to kill the process and show an error message.
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
StackOverflow won’t allow me to delete my answer since it’s the accepted one. It’s garnering down-votes since it’s at the top of the list with a better solution below it. If you’re on a GNU system, please use
timeoutinstead as suggested by @wRAR. So in the hopes that you’ll stop down-voting, here’s how it works:You can use
s,m,hordfor seconds (the default if omitted), minutes, hours or days. A nifty feature here is that you may specify another option-k 30s(before the1sabove) in order to kill it with a SIGKILL after another 30 seconds, should it not respond to the original SIGTERM.A very useful tool. Now scroll down and up-vote @wRAR’s answer.
For posterity, this was my original – inferior – suggestion, it might still be if some use for someone.
A simple bash-script should be able to do that for you
That ought to do it.
$!expands to the last backgrounded process (through the use of&), and kill returns false if it didn’t kill any process, so the echo is only executed if it actually killed something.2>/dev/nullredirects kill’s stderr, otherwise it would print something telling you it was unable to kill the process.You might want to add a
-KILLor whichever signal you want to use to get rid of your process too.EDIT
As ephemient pointed out, there’s a race here if your program finishes and the some other process snatches the pid, it’ll get killed instead. To reduce the probability of it happening, you could react to the SIGCHLD and not try to kill it if that happens. There’s still chance to kill the wrong process, but it’s very remote.