Why can't I get pgrep output right to variable on bash script?2019 Community Moderator ElectionBash script...
Travelling in US for more than 90 days
How can I, as DM, avoid the Conga Line of Death occurring when implementing some form of flanking rule?
In the event of Brexit being postponed beyond the EU elections, will UK voters in EU countries be eligible to participate?
Recursively move files within sub directories
Why didn't Voldemort know what Grindelwald looked like?
Would this string work as string?
Why would five hundred and five same as one?
A seasonal riddle
Connection Between Knot Theory and Number Theory
Trouble reading roman numeral notation with flats
Relations between homogeneous polynomials
Can creatures abilities target that creature itself?
What should be the ideal length of sentences in a blog post for ease of reading?
is this saw blade faulty?
What is the period/term used describe Giuseppe Arcimboldo's style of painting?
Why can't I get pgrep output right to variable on bash script?
Showing mass murder in a kid's book
What is the tangent at a sharp point on a curve?
Mortal danger in mid-grade literature
Should a narrator ever describe things based on a character's view instead of facts?
"Marked down as someone wanting to sell shares." What does that mean?
What is the purpose of using a decision tree?
Are hand made posters acceptable in Academia?
Weird lines in Microsoft Word
Why can't I get pgrep output right to variable on bash script?
2019 Community Moderator ElectionBash script doesn't TEE output to subdirectoryExiting a Bash script when a sudo child quitsConditional execution block with || and parentheses problemProcess being stopped randomlyHow to write bash script while using command as condition in if statement?Using spd-say in a bash script functionGet PID and return code from 1 line bash callbash script: capturing tcp traffic on a remote server sometimes works, sometimes fails. No errorsWhy does bash 'read' exit with status 1?Passing variable to “authorization: bearer” header with Curl and Bash
I'm trying to make a script to either quit compton if it's running or start it if it's not running. I've read from man that it should exit 1 if process is found, so I've tried to make a script that uses that... However this just doesn't work, It starts if it's closed but doesn't close it. what am I doing wrong ??
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ $status == 1 ]];
then
killall compton
else
exec compton -b
fi
echo $status
bash stdout stderr exit-status pgrep
New contributor
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I'm trying to make a script to either quit compton if it's running or start it if it's not running. I've read from man that it should exit 1 if process is found, so I've tried to make a script that uses that... However this just doesn't work, It starts if it's closed but doesn't close it. what am I doing wrong ??
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ $status == 1 ]];
then
killall compton
else
exec compton -b
fi
echo $status
bash stdout stderr exit-status pgrep
New contributor
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I'm trying to make a script to either quit compton if it's running or start it if it's not running. I've read from man that it should exit 1 if process is found, so I've tried to make a script that uses that... However this just doesn't work, It starts if it's closed but doesn't close it. what am I doing wrong ??
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ $status == 1 ]];
then
killall compton
else
exec compton -b
fi
echo $status
bash stdout stderr exit-status pgrep
New contributor
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I'm trying to make a script to either quit compton if it's running or start it if it's not running. I've read from man that it should exit 1 if process is found, so I've tried to make a script that uses that... However this just doesn't work, It starts if it's closed but doesn't close it. what am I doing wrong ??
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ $status == 1 ]];
then
killall compton
else
exec compton -b
fi
echo $status
bash stdout stderr exit-status pgrep
bash stdout stderr exit-status pgrep
New contributor
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 10 mins ago
Kusalananda
136k17257426
136k17257426
New contributor
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 2 hours ago
TubeTube
61
61
New contributor
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Tube is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
You should control exit status of pgrep process which will be in $? variable. Or check if $status variable where you're storing the output of pgrep is f.e. non zero-length string. The script in the question checks whether string in variable status is "1"
so
#!/bin/bash
pgrep compton >/dev/null
if [[ $? -eq 0 ]]
then
killall compton
else
exec compton -b
fi
or
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ -n "$status" ]]
then
killall compton
else
exec compton -b
fi
add a comment |
You are getting the pgrep output in your status variable. It's just not the output that you expect it to be.
pgrep outputs the process IDs (PIDs) of the processes matching the pattern that you give it. If there is a process whose name matches compton, then $status would be the PID of that process, or of those processes. pgrep also returns an exit status, but an exit status is not captured by a command substitution as a string.
In your test, you compare $status against 1. It is unlikely that compton has PID 1.
If you want to kill any compton process if they exist, and start compton -b if no compton process exists, you may do that with
#!/bin/sh
if ! pkill compton; then
exec compton -b
fi
This uses the exit status of pkill. The pkill tool works in an equivalent way to pgrep (they are usually distributed and installed as a pair) but instead of outputting PIDs of matching processes like pgrep would do, pkill sends the TERM signal (by default) to the matching processes.
The if keyword uses the exit status of the command that you use with it.
The ! inverts the sense of the test so that
If
pkill comptonsucceeds, it means that there was one or severalcomptonprocesses that have now been killed, or at least signalled, andexec compton -bwill not be executed.If
pkill comptonfails (no process matched the name, or there was some internal error inpkill), the body of theifstatement would call yourexec compton -b, which would replace the shell process with that ofcompton -b.
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
});
}
});
Tube is a new contributor. Be nice, and check out our Code of Conduct.
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%2f507290%2fwhy-cant-i-get-pgrep-output-right-to-variable-on-bash-script%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
You should control exit status of pgrep process which will be in $? variable. Or check if $status variable where you're storing the output of pgrep is f.e. non zero-length string. The script in the question checks whether string in variable status is "1"
so
#!/bin/bash
pgrep compton >/dev/null
if [[ $? -eq 0 ]]
then
killall compton
else
exec compton -b
fi
or
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ -n "$status" ]]
then
killall compton
else
exec compton -b
fi
add a comment |
You should control exit status of pgrep process which will be in $? variable. Or check if $status variable where you're storing the output of pgrep is f.e. non zero-length string. The script in the question checks whether string in variable status is "1"
so
#!/bin/bash
pgrep compton >/dev/null
if [[ $? -eq 0 ]]
then
killall compton
else
exec compton -b
fi
or
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ -n "$status" ]]
then
killall compton
else
exec compton -b
fi
add a comment |
You should control exit status of pgrep process which will be in $? variable. Or check if $status variable where you're storing the output of pgrep is f.e. non zero-length string. The script in the question checks whether string in variable status is "1"
so
#!/bin/bash
pgrep compton >/dev/null
if [[ $? -eq 0 ]]
then
killall compton
else
exec compton -b
fi
or
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ -n "$status" ]]
then
killall compton
else
exec compton -b
fi
You should control exit status of pgrep process which will be in $? variable. Or check if $status variable where you're storing the output of pgrep is f.e. non zero-length string. The script in the question checks whether string in variable status is "1"
so
#!/bin/bash
pgrep compton >/dev/null
if [[ $? -eq 0 ]]
then
killall compton
else
exec compton -b
fi
or
#!/bin/bash
status=$(pgrep compton 2>&1)
if [[ -n "$status" ]]
then
killall compton
else
exec compton -b
fi
answered 2 hours ago
Jakub JindraJakub Jindra
307310
307310
add a comment |
add a comment |
You are getting the pgrep output in your status variable. It's just not the output that you expect it to be.
pgrep outputs the process IDs (PIDs) of the processes matching the pattern that you give it. If there is a process whose name matches compton, then $status would be the PID of that process, or of those processes. pgrep also returns an exit status, but an exit status is not captured by a command substitution as a string.
In your test, you compare $status against 1. It is unlikely that compton has PID 1.
If you want to kill any compton process if they exist, and start compton -b if no compton process exists, you may do that with
#!/bin/sh
if ! pkill compton; then
exec compton -b
fi
This uses the exit status of pkill. The pkill tool works in an equivalent way to pgrep (they are usually distributed and installed as a pair) but instead of outputting PIDs of matching processes like pgrep would do, pkill sends the TERM signal (by default) to the matching processes.
The if keyword uses the exit status of the command that you use with it.
The ! inverts the sense of the test so that
If
pkill comptonsucceeds, it means that there was one or severalcomptonprocesses that have now been killed, or at least signalled, andexec compton -bwill not be executed.If
pkill comptonfails (no process matched the name, or there was some internal error inpkill), the body of theifstatement would call yourexec compton -b, which would replace the shell process with that ofcompton -b.
add a comment |
You are getting the pgrep output in your status variable. It's just not the output that you expect it to be.
pgrep outputs the process IDs (PIDs) of the processes matching the pattern that you give it. If there is a process whose name matches compton, then $status would be the PID of that process, or of those processes. pgrep also returns an exit status, but an exit status is not captured by a command substitution as a string.
In your test, you compare $status against 1. It is unlikely that compton has PID 1.
If you want to kill any compton process if they exist, and start compton -b if no compton process exists, you may do that with
#!/bin/sh
if ! pkill compton; then
exec compton -b
fi
This uses the exit status of pkill. The pkill tool works in an equivalent way to pgrep (they are usually distributed and installed as a pair) but instead of outputting PIDs of matching processes like pgrep would do, pkill sends the TERM signal (by default) to the matching processes.
The if keyword uses the exit status of the command that you use with it.
The ! inverts the sense of the test so that
If
pkill comptonsucceeds, it means that there was one or severalcomptonprocesses that have now been killed, or at least signalled, andexec compton -bwill not be executed.If
pkill comptonfails (no process matched the name, or there was some internal error inpkill), the body of theifstatement would call yourexec compton -b, which would replace the shell process with that ofcompton -b.
add a comment |
You are getting the pgrep output in your status variable. It's just not the output that you expect it to be.
pgrep outputs the process IDs (PIDs) of the processes matching the pattern that you give it. If there is a process whose name matches compton, then $status would be the PID of that process, or of those processes. pgrep also returns an exit status, but an exit status is not captured by a command substitution as a string.
In your test, you compare $status against 1. It is unlikely that compton has PID 1.
If you want to kill any compton process if they exist, and start compton -b if no compton process exists, you may do that with
#!/bin/sh
if ! pkill compton; then
exec compton -b
fi
This uses the exit status of pkill. The pkill tool works in an equivalent way to pgrep (they are usually distributed and installed as a pair) but instead of outputting PIDs of matching processes like pgrep would do, pkill sends the TERM signal (by default) to the matching processes.
The if keyword uses the exit status of the command that you use with it.
The ! inverts the sense of the test so that
If
pkill comptonsucceeds, it means that there was one or severalcomptonprocesses that have now been killed, or at least signalled, andexec compton -bwill not be executed.If
pkill comptonfails (no process matched the name, or there was some internal error inpkill), the body of theifstatement would call yourexec compton -b, which would replace the shell process with that ofcompton -b.
You are getting the pgrep output in your status variable. It's just not the output that you expect it to be.
pgrep outputs the process IDs (PIDs) of the processes matching the pattern that you give it. If there is a process whose name matches compton, then $status would be the PID of that process, or of those processes. pgrep also returns an exit status, but an exit status is not captured by a command substitution as a string.
In your test, you compare $status against 1. It is unlikely that compton has PID 1.
If you want to kill any compton process if they exist, and start compton -b if no compton process exists, you may do that with
#!/bin/sh
if ! pkill compton; then
exec compton -b
fi
This uses the exit status of pkill. The pkill tool works in an equivalent way to pgrep (they are usually distributed and installed as a pair) but instead of outputting PIDs of matching processes like pgrep would do, pkill sends the TERM signal (by default) to the matching processes.
The if keyword uses the exit status of the command that you use with it.
The ! inverts the sense of the test so that
If
pkill comptonsucceeds, it means that there was one or severalcomptonprocesses that have now been killed, or at least signalled, andexec compton -bwill not be executed.If
pkill comptonfails (no process matched the name, or there was some internal error inpkill), the body of theifstatement would call yourexec compton -b, which would replace the shell process with that ofcompton -b.
edited 18 mins ago
answered 1 hour ago
KusalanandaKusalananda
136k17257426
136k17257426
add a comment |
add a comment |
Tube is a new contributor. Be nice, and check out our Code of Conduct.
Tube is a new contributor. Be nice, and check out our Code of Conduct.
Tube is a new contributor. Be nice, and check out our Code of Conduct.
Tube is a new contributor. Be nice, and check out our Code of Conduct.
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%2f507290%2fwhy-cant-i-get-pgrep-output-right-to-variable-on-bash-script%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