Kill -9 problem in bash file
Clash Royale CLAN TAG#URR8PPP
I wrote a 2 line bash script file in Centos 6.8
#! /bin/sh
pid= ps -ef | grep -i 'adminserver' | grep -v grep | awk 'print $2'
kill -9 $pid
when I run the script i get the following output:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
shell-script kill
edited Feb 6 at 10:31
ctrl-alt-delor
11.8k42159
asked Feb 6 at 8:05
Ali GolestanAli Golestan
91215
add a comment |
I wrote a 2 line bash script file in Centos 6.8
#! /bin/sh
pid= ps -ef | grep -i 'adminserver' | grep -v grep | awk 'print $2'
kill -9 $pid
when I run the script i get the following output:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
shell-script kill
edited Feb 6 at 10:31
ctrl-alt-delor
11.8k42159
asked Feb 6 at 8:05
Ali GolestanAli Golestan
91215
pid=$(ps -ef | grep -i 'adminserve[r]' | awk 'print $2')
– ctrl-alt-delor
Feb 6 at 10:32
add a comment |
I wrote a 2 line bash script file in Centos 6.8
#! /bin/sh
pid= ps -ef | grep -i 'adminserver' | grep -v grep | awk 'print $2'
kill -9 $pid
when I run the script i get the following output:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
shell-script kill
edited Feb 6 at 10:31
ctrl-alt-delor
11.8k42159
asked Feb 6 at 8:05
Ali GolestanAli Golestan
91215
I wrote a 2 line bash script file in Centos 6.8
#! /bin/sh
pid= ps -ef | grep -i 'adminserver' | grep -v grep | awk 'print $2'
kill -9 $pid
when I run the script i get the following output:
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
shell-script kill
shell-script kill
edited Feb 6 at 10:31
ctrl-alt-delor
11.8k42159
asked Feb 6 at 8:05
Ali GolestanAli Golestan
91215
edited Feb 6 at 10:31
ctrl-alt-delor
11.8k42159
asked Feb 6 at 8:05
Ali GolestanAli Golestan
91215
edited Feb 6 at 10:31
ctrl-alt-delor
11.8k42159
edited Feb 6 at 10:31
ctrl-alt-delor
11.8k42159
edited Feb 6 at 10:31
ctrl-alt-delor
11.8k42159
11.8k42159
asked Feb 6 at 8:05
Ali GolestanAli Golestan
91215
asked Feb 6 at 8:05
Ali GolestanAli Golestan
91215
asked Feb 6 at 8:05
Ali GolestanAli Golestan
91215
91215
pid=$(ps -ef | grep -i 'adminserve[r]' | awk 'print $2')
– ctrl-alt-delor
Feb 6 at 10:32
add a comment |
pid=$(ps -ef | grep -i 'adminserve[r]' | awk 'print $2')
– ctrl-alt-delor
Feb 6 at 10:32
pid=$(ps -ef | grep -i 'adminserve[r]' | awk 'print $2')
– ctrl-alt-delor
Feb 6 at 10:32
pid=$(ps -ef | grep -i 'adminserve[r]' | awk 'print $2')
– ctrl-alt-delor
Feb 6 at 10:32
add a comment |
1 Answer
1
active
oldest
votes
pid= with a space after it would set the pid variable to an empty string. The rest of that line would simply execute the pipeline and output the result (probably to the terminal unless it's being redirected). Since $pid is empty, kill later complains.
To capture the output of a command, use $(...), e.g.
pid=$( ps -ef | ... )
However, it's better to use pkill for what you're attempting to do:
pkill adminserver
See the pkill manual.
I would also avoid using the KILL signal if at all possible. See e.g. "When should I not kill -9 a process?".
answered Feb 6 at 8:11
KusalanandaKusalananda
133k17253416
thanks for your answer, it worked
– Ali Golestan
Feb 6 at 9:58
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f498989%2fkill-9-problem-in-bash-file%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
pid= with a space after it would set the pid variable to an empty string. The rest of that line would simply execute the pipeline and output the result (probably to the terminal unless it's being redirected). Since $pid is empty, kill later complains.
To capture the output of a command, use $(...), e.g.
pid=$( ps -ef | ... )
However, it's better to use pkill for what you're attempting to do:
pkill adminserver
See the pkill manual.
I would also avoid using the KILL signal if at all possible. See e.g. "When should I not kill -9 a process?".
answered Feb 6 at 8:11
KusalanandaKusalananda
133k17253416
thanks for your answer, it worked
– Ali Golestan
Feb 6 at 9:58
add a comment |
pid= with a space after it would set the pid variable to an empty string. The rest of that line would simply execute the pipeline and output the result (probably to the terminal unless it's being redirected). Since $pid is empty, kill later complains.
To capture the output of a command, use $(...), e.g.
pid=$( ps -ef | ... )
However, it's better to use pkill for what you're attempting to do:
pkill adminserver
See the pkill manual.
I would also avoid using the KILL signal if at all possible. See e.g. "When should I not kill -9 a process?".
answered Feb 6 at 8:11
KusalanandaKusalananda
133k17253416
thanks for your answer, it worked
– Ali Golestan
Feb 6 at 9:58
add a comment |
pid= with a space after it would set the pid variable to an empty string. The rest of that line would simply execute the pipeline and output the result (probably to the terminal unless it's being redirected). Since $pid is empty, kill later complains.
To capture the output of a command, use $(...), e.g.
pid=$( ps -ef | ... )
However, it's better to use pkill for what you're attempting to do:
pkill adminserver
See the pkill manual.
I would also avoid using the KILL signal if at all possible. See e.g. "When should I not kill -9 a process?".
answered Feb 6 at 8:11
KusalanandaKusalananda
133k17253416
pid= with a space after it would set the pid variable to an empty string. The rest of that line would simply execute the pipeline and output the result (probably to the terminal unless it's being redirected). Since $pid is empty, kill later complains.
To capture the output of a command, use $(...), e.g.
pid=$( ps -ef | ... )
However, it's better to use pkill for what you're attempting to do:
pkill adminserver
See the pkill manual.
I would also avoid using the KILL signal if at all possible. See e.g. "When should I not kill -9 a process?".
answered Feb 6 at 8:11
KusalanandaKusalananda
133k17253416
edited Feb 6 at 21:29
answered Feb 6 at 8:11
KusalanandaKusalananda
133k17253416
answered Feb 6 at 8:11
KusalanandaKusalananda
133k17253416
answered Feb 6 at 8:11
KusalanandaKusalananda
133k17253416
133k17253416
thanks for your answer, it worked
– Ali Golestan
Feb 6 at 9:58
add a comment |
thanks for your answer, it worked
– Ali Golestan
Feb 6 at 9:58
thanks for your answer, it worked
– Ali Golestan
Feb 6 at 9:58
thanks for your answer, it worked
– Ali Golestan
Feb 6 at 9:58
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f498989%2fkill-9-problem-in-bash-file%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
pid=$(ps -ef | grep -i 'adminserve[r]' | awk 'print $2')
– ctrl-alt-delor
Feb 6 at 10:32