Bash, how to check if a C program times out
I want to run a C program foo.c thats compiled to foo within a bash script and see check if it times out.
There is one parameter to foo and the 10 second timeout.
I want to check if the program foo times out or executes. If it times out I want to exit 0.
#!/bin/sh
# -*-sh-*-
/foo $1 10
if [$? -eq 0]
then
exit 0;
fi
exit 1;
c bash
asked Nov 13 '18 at 18:57
ab3rcab3rc
114
add a comment |
I want to run a C program foo.c thats compiled to foo within a bash script and see check if it times out.
There is one parameter to foo and the 10 second timeout.
I want to check if the program foo times out or executes. If it times out I want to exit 0.
#!/bin/sh
# -*-sh-*-
/foo $1 10
if [$? -eq 0]
then
exit 0;
fi
exit 1;
c bash
asked Nov 13 '18 at 18:57
ab3rcab3rc
114
Either one should suffice, the issue is that the syntax is breaking things. Line 5 is command not found.
– ab3rc
Nov 13 '18 at 19:20
add a comment |
I want to run a C program foo.c thats compiled to foo within a bash script and see check if it times out.
There is one parameter to foo and the 10 second timeout.
I want to check if the program foo times out or executes. If it times out I want to exit 0.
#!/bin/sh
# -*-sh-*-
/foo $1 10
if [$? -eq 0]
then
exit 0;
fi
exit 1;
c bash
asked Nov 13 '18 at 18:57
ab3rcab3rc
114
I want to run a C program foo.c thats compiled to foo within a bash script and see check if it times out.
There is one parameter to foo and the 10 second timeout.
I want to check if the program foo times out or executes. If it times out I want to exit 0.
#!/bin/sh
# -*-sh-*-
/foo $1 10
if [$? -eq 0]
then
exit 0;
fi
exit 1;
c bash
c bash
asked Nov 13 '18 at 18:57
ab3rcab3rc
114
asked Nov 13 '18 at 18:57
ab3rcab3rc
114
asked Nov 13 '18 at 18:57
ab3rcab3rc
114
asked Nov 13 '18 at 18:57
ab3rcab3rc
114
asked Nov 13 '18 at 18:57
ab3rcab3rc
114
114
Either one should suffice, the issue is that the syntax is breaking things. Line 5 is command not found.
– ab3rc
Nov 13 '18 at 19:20
add a comment |
Either one should suffice, the issue is that the syntax is breaking things. Line 5 is command not found.
– ab3rc
Nov 13 '18 at 19:20
Either one should suffice, the issue is that the syntax is breaking things. Line 5 is command not found.
– ab3rc
Nov 13 '18 at 19:20
Either one should suffice, the issue is that the syntax is breaking things. Line 5 is command not found.
– ab3rc
Nov 13 '18 at 19:20
add a comment |
1 Answer
1
active
oldest
votes
Use the timeout command:
timeout 10s ./foo
if [ $? -eq 124 ] ; then
exit 0
else
exit 1
fi
From man timeout:
If the command times out, and --preserve-status is not set, then exit with status 124. Otherwise, exit with the status of COMMAND. If
no signal is specified, send the TERM signal upon timeout. The TERM signal kills any process that does not block or catch that signal.
It may be necessary to use the KILL (9) signal, since this signal cannot be caught, in which case the exit status is 128+9 rather than
124.
answered Nov 13 '18 at 19:00
hek2mglhek2mgl
107k13144167
If I try that as a bash script I get command not found for timeout for timeout 10s /foo $1
– ab3rc
Nov 13 '18 at 19:06
isn't it better to use-eqinifstatement?
– Afshin
Nov 13 '18 at 19:06
@Afshin Yeah, thanks!
– hek2mgl
Nov 13 '18 at 19:53
@ab3rc If you are not working on GNU/Linux, you'll have to install the timeout command. Installing GNU coreutils will do it.
– hek2mgl
Nov 13 '18 at 19:54
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287796%2fbash-how-to-check-if-a-c-program-times-out%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Use the timeout command:
timeout 10s ./foo
if [ $? -eq 124 ] ; then
exit 0
else
exit 1
fi
From man timeout:
If the command times out, and --preserve-status is not set, then exit with status 124. Otherwise, exit with the status of COMMAND. If
no signal is specified, send the TERM signal upon timeout. The TERM signal kills any process that does not block or catch that signal.
It may be necessary to use the KILL (9) signal, since this signal cannot be caught, in which case the exit status is 128+9 rather than
124.
answered Nov 13 '18 at 19:00
hek2mglhek2mgl
107k13144167
If I try that as a bash script I get command not found for timeout for timeout 10s /foo $1
– ab3rc
Nov 13 '18 at 19:06
isn't it better to use-eqinifstatement?
– Afshin
Nov 13 '18 at 19:06
@Afshin Yeah, thanks!
– hek2mgl
Nov 13 '18 at 19:53
@ab3rc If you are not working on GNU/Linux, you'll have to install the timeout command. Installing GNU coreutils will do it.
– hek2mgl
Nov 13 '18 at 19:54
add a comment |
Use the timeout command:
timeout 10s ./foo
if [ $? -eq 124 ] ; then
exit 0
else
exit 1
fi
From man timeout:
If the command times out, and --preserve-status is not set, then exit with status 124. Otherwise, exit with the status of COMMAND. If
no signal is specified, send the TERM signal upon timeout. The TERM signal kills any process that does not block or catch that signal.
It may be necessary to use the KILL (9) signal, since this signal cannot be caught, in which case the exit status is 128+9 rather than
124.
answered Nov 13 '18 at 19:00
hek2mglhek2mgl
107k13144167
If I try that as a bash script I get command not found for timeout for timeout 10s /foo $1
– ab3rc
Nov 13 '18 at 19:06
isn't it better to use-eqinifstatement?
– Afshin
Nov 13 '18 at 19:06
@Afshin Yeah, thanks!
– hek2mgl
Nov 13 '18 at 19:53
@ab3rc If you are not working on GNU/Linux, you'll have to install the timeout command. Installing GNU coreutils will do it.
– hek2mgl
Nov 13 '18 at 19:54
add a comment |
Use the timeout command:
timeout 10s ./foo
if [ $? -eq 124 ] ; then
exit 0
else
exit 1
fi
From man timeout:
If the command times out, and --preserve-status is not set, then exit with status 124. Otherwise, exit with the status of COMMAND. If
no signal is specified, send the TERM signal upon timeout. The TERM signal kills any process that does not block or catch that signal.
It may be necessary to use the KILL (9) signal, since this signal cannot be caught, in which case the exit status is 128+9 rather than
124.
answered Nov 13 '18 at 19:00
hek2mglhek2mgl
107k13144167
Use the timeout command:
timeout 10s ./foo
if [ $? -eq 124 ] ; then
exit 0
else
exit 1
fi
From man timeout:
If the command times out, and --preserve-status is not set, then exit with status 124. Otherwise, exit with the status of COMMAND. If
no signal is specified, send the TERM signal upon timeout. The TERM signal kills any process that does not block or catch that signal.
It may be necessary to use the KILL (9) signal, since this signal cannot be caught, in which case the exit status is 128+9 rather than
124.
answered Nov 13 '18 at 19:00
hek2mglhek2mgl
107k13144167
edited Nov 13 '18 at 19:53
answered Nov 13 '18 at 19:00
hek2mglhek2mgl
107k13144167
answered Nov 13 '18 at 19:00
hek2mglhek2mgl
107k13144167
answered Nov 13 '18 at 19:00
hek2mglhek2mgl
107k13144167
107k13144167
If I try that as a bash script I get command not found for timeout for timeout 10s /foo $1
– ab3rc
Nov 13 '18 at 19:06
isn't it better to use-eqinifstatement?
– Afshin
Nov 13 '18 at 19:06
@Afshin Yeah, thanks!
– hek2mgl
Nov 13 '18 at 19:53
@ab3rc If you are not working on GNU/Linux, you'll have to install the timeout command. Installing GNU coreutils will do it.
– hek2mgl
Nov 13 '18 at 19:54
add a comment |
If I try that as a bash script I get command not found for timeout for timeout 10s /foo $1
– ab3rc
Nov 13 '18 at 19:06
isn't it better to use-eqinifstatement?
– Afshin
Nov 13 '18 at 19:06
@Afshin Yeah, thanks!
– hek2mgl
Nov 13 '18 at 19:53
@ab3rc If you are not working on GNU/Linux, you'll have to install the timeout command. Installing GNU coreutils will do it.
– hek2mgl
Nov 13 '18 at 19:54
If I try that as a bash script I get command not found for timeout for timeout 10s /foo $1
– ab3rc
Nov 13 '18 at 19:06
If I try that as a bash script I get command not found for timeout for timeout 10s /foo $1
– ab3rc
Nov 13 '18 at 19:06
isn't it better to use
-eq in if statement?– Afshin
Nov 13 '18 at 19:06
isn't it better to use
-eq in if statement?– Afshin
Nov 13 '18 at 19:06
@Afshin Yeah, thanks!
– hek2mgl
Nov 13 '18 at 19:53
@Afshin Yeah, thanks!
– hek2mgl
Nov 13 '18 at 19:53
@ab3rc If you are not working on GNU/Linux, you'll have to install the timeout command. Installing GNU coreutils will do it.
– hek2mgl
Nov 13 '18 at 19:54
@ab3rc If you are not working on GNU/Linux, you'll have to install the timeout command. Installing GNU coreutils will do it.
– hek2mgl
Nov 13 '18 at 19:54
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53287796%2fbash-how-to-check-if-a-c-program-times-out%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Either one should suffice, the issue is that the syntax is breaking things. Line 5 is command not found.
– ab3rc
Nov 13 '18 at 19:20