Kill all queued jobs
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I need to kill all the queued and running jobs on my ID. I have tried
at -l | awk 'print $1'| at -r
But I keep getting
does not exist
Which leads me to believe that I am parsing the statement wrong.
shell arguments at
add a comment |
up vote
1
down vote
favorite
I need to kill all the queued and running jobs on my ID. I have tried
at -l | awk 'print $1'| at -r
But I keep getting
does not exist
Which leads me to believe that I am parsing the statement wrong.
shell arguments at
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I need to kill all the queued and running jobs on my ID. I have tried
at -l | awk 'print $1'| at -r
But I keep getting
does not exist
Which leads me to believe that I am parsing the statement wrong.
shell arguments at
I need to kill all the queued and running jobs on my ID. I have tried
at -l | awk 'print $1'| at -r
But I keep getting
does not exist
Which leads me to believe that I am parsing the statement wrong.
shell arguments at
shell arguments at
edited Nov 20 at 22:29
Rui F Ribeiro
38.2k1475125
38.2k1475125
asked Jun 22 '14 at 17:04
mlegge
1781211
1781211
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
|
pipes the output to the standard input of the next command, not to its command line arguments.
To remove all queued jobs, run
at -l | awk 'print $1'| xargs at -r
alternatively, you can use
at -r $( at -l | awk 'print $1' )
$( ... )
is replaced by the output of the commands it contains.
See also this related question.
Please note, that this just removes the jobs from atq, but does not kill running jobs.
If the processes command line matches to a PATTERN and there are no other similar processes running on your username, you can kill them with
pgrep -u $USER PATTERN
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
|
pipes the output to the standard input of the next command, not to its command line arguments.
To remove all queued jobs, run
at -l | awk 'print $1'| xargs at -r
alternatively, you can use
at -r $( at -l | awk 'print $1' )
$( ... )
is replaced by the output of the commands it contains.
See also this related question.
Please note, that this just removes the jobs from atq, but does not kill running jobs.
If the processes command line matches to a PATTERN and there are no other similar processes running on your username, you can kill them with
pgrep -u $USER PATTERN
add a comment |
up vote
2
down vote
accepted
|
pipes the output to the standard input of the next command, not to its command line arguments.
To remove all queued jobs, run
at -l | awk 'print $1'| xargs at -r
alternatively, you can use
at -r $( at -l | awk 'print $1' )
$( ... )
is replaced by the output of the commands it contains.
See also this related question.
Please note, that this just removes the jobs from atq, but does not kill running jobs.
If the processes command line matches to a PATTERN and there are no other similar processes running on your username, you can kill them with
pgrep -u $USER PATTERN
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
|
pipes the output to the standard input of the next command, not to its command line arguments.
To remove all queued jobs, run
at -l | awk 'print $1'| xargs at -r
alternatively, you can use
at -r $( at -l | awk 'print $1' )
$( ... )
is replaced by the output of the commands it contains.
See also this related question.
Please note, that this just removes the jobs from atq, but does not kill running jobs.
If the processes command line matches to a PATTERN and there are no other similar processes running on your username, you can kill them with
pgrep -u $USER PATTERN
|
pipes the output to the standard input of the next command, not to its command line arguments.
To remove all queued jobs, run
at -l | awk 'print $1'| xargs at -r
alternatively, you can use
at -r $( at -l | awk 'print $1' )
$( ... )
is replaced by the output of the commands it contains.
See also this related question.
Please note, that this just removes the jobs from atq, but does not kill running jobs.
If the processes command line matches to a PATTERN and there are no other similar processes running on your username, you can kill them with
pgrep -u $USER PATTERN
edited Apr 13 '17 at 12:36
Community♦
1
1
answered Jun 22 '14 at 17:09
jofel
19.9k34780
19.9k34780
add a comment |
add a comment |
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%2f138565%2fkill-all-queued-jobs%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