Why does nohup command interrupt?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I put a command in .bash_profile file. The command is:
nohup stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &
While I am working on terminal it appears:
[1]+ Done nohup stdbuf -oL -eL sysdig -c spy_users >> /path/to/out 2>> /path/to/err
Whu do I have this interruption?
bash background-process nohup interrupt
asked Jul 5 at 6:33
yasin
183
add a comment |Â
up vote
0
down vote
favorite
I put a command in .bash_profile file. The command is:
nohup stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &
While I am working on terminal it appears:
[1]+ Done nohup stdbuf -oL -eL sysdig -c spy_users >> /path/to/out 2>> /path/to/err
Whu do I have this interruption?
bash background-process nohup interrupt
asked Jul 5 at 6:33
yasin
183
Why do you feel you need thenohup? Have you tried just putting thesysdigdirectly into your.bash_profileand backgrounding it?
– slm♦
Jul 5 at 6:55
what do you mean? how can I have better background command?
– yasin
Jul 5 at 6:56
Try this:sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &.
– slm♦
Jul 5 at 6:56
Thank you, I am going to check:stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &I will let you know ther result.
– yasin
Jul 5 at 6:58
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I put a command in .bash_profile file. The command is:
nohup stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &
While I am working on terminal it appears:
[1]+ Done nohup stdbuf -oL -eL sysdig -c spy_users >> /path/to/out 2>> /path/to/err
Whu do I have this interruption?
bash background-process nohup interrupt
asked Jul 5 at 6:33
yasin
183
I put a command in .bash_profile file. The command is:
nohup stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &
While I am working on terminal it appears:
[1]+ Done nohup stdbuf -oL -eL sysdig -c spy_users >> /path/to/out 2>> /path/to/err
Whu do I have this interruption?
bash background-process nohup interrupt
asked Jul 5 at 6:33
yasin
183
asked Jul 5 at 6:33
yasin
183
asked Jul 5 at 6:33
yasin
183
asked Jul 5 at 6:33
yasin
183
183
Why do you feel you need thenohup? Have you tried just putting thesysdigdirectly into your.bash_profileand backgrounding it?
– slm♦
Jul 5 at 6:55
what do you mean? how can I have better background command?
– yasin
Jul 5 at 6:56
Try this:sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &.
– slm♦
Jul 5 at 6:56
Thank you, I am going to check:stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &I will let you know ther result.
– yasin
Jul 5 at 6:58
add a comment |Â
Why do you feel you need thenohup? Have you tried just putting thesysdigdirectly into your.bash_profileand backgrounding it?
– slm♦
Jul 5 at 6:55
what do you mean? how can I have better background command?
– yasin
Jul 5 at 6:56
Try this:sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &.
– slm♦
Jul 5 at 6:56
Thank you, I am going to check:stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &I will let you know ther result.
– yasin
Jul 5 at 6:58
Why do you feel you need the
nohup? Have you tried just putting the sysdig directly into your .bash_profile and backgrounding it?– slm♦
Jul 5 at 6:55
Why do you feel you need the
nohup? Have you tried just putting the sysdig directly into your .bash_profile and backgrounding it?– slm♦
Jul 5 at 6:55
what do you mean? how can I have better background command?
– yasin
Jul 5 at 6:56
what do you mean? how can I have better background command?
– yasin
Jul 5 at 6:56
Try this:
sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &.– slm♦
Jul 5 at 6:56
Try this:
sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &.– slm♦
Jul 5 at 6:56
Thank you, I am going to check:
stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err & I will let you know ther result.– yasin
Jul 5 at 6:58
Thank you, I am going to check:
stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err & I will let you know ther result.– yasin
Jul 5 at 6:58
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f453538%2fwhy-does-nohup-command-interrupt%23new-answer', 'question_page');
);
Post as a guest
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
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
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
Why do you feel you need the
nohup? Have you tried just putting thesysdigdirectly into your.bash_profileand backgrounding it?– slm♦
Jul 5 at 6:55
what do you mean? how can I have better background command?
– yasin
Jul 5 at 6:56
Try this:
sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &.– slm♦
Jul 5 at 6:56
Thank you, I am going to check:
stdbuf -oL -eL sysdig -c spy_users 1>>/path/to/out 2>>/path/to/err &I will let you know ther result.– yasin
Jul 5 at 6:58