Get PID of nohup process through ssh










1















I would like to get the PID of a process I start through ssh.



I have a bash script and here is what I wrote:



SSH_COMMAND='ssh'
cmd=`eval $my_cmd`
PROG_CMD="$program $cmd"
$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!'" > prog.pid"


Note that variables "program" and "my_cmd" are defined in a JSON file (and contain, respectively, my program and the command to start my program).



My program is started on the server exactly the way it is supposed to start but I do not have the correct PID (i.e : the PID of program) in the prog.pid file.



EDIT : I did an echo of the SSH_COMMAND and I got :



 ssh root@server (my_program args > output.log 2>&1 & ) & echo $! > prog.pid


args : arguments of my_program



output.log : log file of my program










share|improve this question
























  • where the prog.pid is expected in root's home directory of server ?

    – Nahuel Fouilleul
    May 26 '17 at 8:47












  • Nope, the prog.pid is located on the "local machine", where I do the ssh command. But the issues is not here. I have the prog.pid file with a PID wrote inside... it is just not the correct one !

    – klaus
    May 26 '17 at 8:59











  • in the first command prog.id was inside ssh command between double quotes so expected on remote

    – Nahuel Fouilleul
    May 26 '17 at 9:18











  • The quotes are good imho.

    – klaus
    May 26 '17 at 9:49











  • I didn't say quotes were wrong, but the command was not doing expected because as is the first command would create a file on remote server in current working directory by default root's home

    – Nahuel Fouilleul
    May 26 '17 at 10:09















1















I would like to get the PID of a process I start through ssh.



I have a bash script and here is what I wrote:



SSH_COMMAND='ssh'
cmd=`eval $my_cmd`
PROG_CMD="$program $cmd"
$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!'" > prog.pid"


Note that variables "program" and "my_cmd" are defined in a JSON file (and contain, respectively, my program and the command to start my program).



My program is started on the server exactly the way it is supposed to start but I do not have the correct PID (i.e : the PID of program) in the prog.pid file.



EDIT : I did an echo of the SSH_COMMAND and I got :



 ssh root@server (my_program args > output.log 2>&1 & ) & echo $! > prog.pid


args : arguments of my_program



output.log : log file of my program










share|improve this question
























  • where the prog.pid is expected in root's home directory of server ?

    – Nahuel Fouilleul
    May 26 '17 at 8:47












  • Nope, the prog.pid is located on the "local machine", where I do the ssh command. But the issues is not here. I have the prog.pid file with a PID wrote inside... it is just not the correct one !

    – klaus
    May 26 '17 at 8:59











  • in the first command prog.id was inside ssh command between double quotes so expected on remote

    – Nahuel Fouilleul
    May 26 '17 at 9:18











  • The quotes are good imho.

    – klaus
    May 26 '17 at 9:49











  • I didn't say quotes were wrong, but the command was not doing expected because as is the first command would create a file on remote server in current working directory by default root's home

    – Nahuel Fouilleul
    May 26 '17 at 10:09













1












1








1








I would like to get the PID of a process I start through ssh.



I have a bash script and here is what I wrote:



SSH_COMMAND='ssh'
cmd=`eval $my_cmd`
PROG_CMD="$program $cmd"
$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!'" > prog.pid"


Note that variables "program" and "my_cmd" are defined in a JSON file (and contain, respectively, my program and the command to start my program).



My program is started on the server exactly the way it is supposed to start but I do not have the correct PID (i.e : the PID of program) in the prog.pid file.



EDIT : I did an echo of the SSH_COMMAND and I got :



 ssh root@server (my_program args > output.log 2>&1 & ) & echo $! > prog.pid


args : arguments of my_program



output.log : log file of my program










share|improve this question
















I would like to get the PID of a process I start through ssh.



I have a bash script and here is what I wrote:



SSH_COMMAND='ssh'
cmd=`eval $my_cmd`
PROG_CMD="$program $cmd"
$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!'" > prog.pid"


Note that variables "program" and "my_cmd" are defined in a JSON file (and contain, respectively, my program and the command to start my program).



My program is started on the server exactly the way it is supposed to start but I do not have the correct PID (i.e : the PID of program) in the prog.pid file.



EDIT : I did an echo of the SSH_COMMAND and I got :



 ssh root@server (my_program args > output.log 2>&1 & ) & echo $! > prog.pid


args : arguments of my_program



output.log : log file of my program







bash ssh pid






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 26 '17 at 11:04







klaus

















asked May 26 '17 at 7:55









klausklaus

322214




322214












  • where the prog.pid is expected in root's home directory of server ?

    – Nahuel Fouilleul
    May 26 '17 at 8:47












  • Nope, the prog.pid is located on the "local machine", where I do the ssh command. But the issues is not here. I have the prog.pid file with a PID wrote inside... it is just not the correct one !

    – klaus
    May 26 '17 at 8:59











  • in the first command prog.id was inside ssh command between double quotes so expected on remote

    – Nahuel Fouilleul
    May 26 '17 at 9:18











  • The quotes are good imho.

    – klaus
    May 26 '17 at 9:49











  • I didn't say quotes were wrong, but the command was not doing expected because as is the first command would create a file on remote server in current working directory by default root's home

    – Nahuel Fouilleul
    May 26 '17 at 10:09

















  • where the prog.pid is expected in root's home directory of server ?

    – Nahuel Fouilleul
    May 26 '17 at 8:47












  • Nope, the prog.pid is located on the "local machine", where I do the ssh command. But the issues is not here. I have the prog.pid file with a PID wrote inside... it is just not the correct one !

    – klaus
    May 26 '17 at 8:59











  • in the first command prog.id was inside ssh command between double quotes so expected on remote

    – Nahuel Fouilleul
    May 26 '17 at 9:18











  • The quotes are good imho.

    – klaus
    May 26 '17 at 9:49











  • I didn't say quotes were wrong, but the command was not doing expected because as is the first command would create a file on remote server in current working directory by default root's home

    – Nahuel Fouilleul
    May 26 '17 at 10:09
















where the prog.pid is expected in root's home directory of server ?

– Nahuel Fouilleul
May 26 '17 at 8:47






where the prog.pid is expected in root's home directory of server ?

– Nahuel Fouilleul
May 26 '17 at 8:47














Nope, the prog.pid is located on the "local machine", where I do the ssh command. But the issues is not here. I have the prog.pid file with a PID wrote inside... it is just not the correct one !

– klaus
May 26 '17 at 8:59





Nope, the prog.pid is located on the "local machine", where I do the ssh command. But the issues is not here. I have the prog.pid file with a PID wrote inside... it is just not the correct one !

– klaus
May 26 '17 at 8:59













in the first command prog.id was inside ssh command between double quotes so expected on remote

– Nahuel Fouilleul
May 26 '17 at 9:18





in the first command prog.id was inside ssh command between double quotes so expected on remote

– Nahuel Fouilleul
May 26 '17 at 9:18













The quotes are good imho.

– klaus
May 26 '17 at 9:49





The quotes are good imho.

– klaus
May 26 '17 at 9:49













I didn't say quotes were wrong, but the command was not doing expected because as is the first command would create a file on remote server in current working directory by default root's home

– Nahuel Fouilleul
May 26 '17 at 10:09





I didn't say quotes were wrong, but the command was not doing expected because as is the first command would create a file on remote server in current working directory by default root's home

– Nahuel Fouilleul
May 26 '17 at 10:09












2 Answers
2






active

oldest

votes


















3














Don't use (command &) &. Just use (command) & (or just command &). With (command &) &, Bash needs to fork another sub-shell to run the command so $! would be the PID of the sub-shell other than the command.



See following example:



[STEP 124] # (nohup sleep 1234 > /dev/null 2>&1 &) &
[1] 44420 <=== this is the PID of the sub-shell which died immediately
[STEP 125] #
[1]+ Done ( nohup sleep 1234 > /dev/null 2>&1 & )
[STEP 126] # ps p 44420 <=== as you can see this PID does not exist any more
PID TTY STAT TIME COMMAND
[STEP 127] # ps -C sleep u
USER PID TTY STAT START TIME COMMAND
root 44421 pts/13 S 17:48 0:00 sleep 1234
[STEP 128] # kill 44421
[STEP 129] #


This would work fine:



[STEP 131] # (nohup sleep 1234 > /dev/null 2>&1) &
[1] 44424 <=== this is the PID of the sleep command
[STEP 132] # ps p 44424 u
USER PID TTY STAT START TIME COMMAND
root 44424 pts/13 S 17:49 0:00 sleep 1234
[STEP 133] #





share|improve this answer

























  • You were right, I deleted the & and the PID was the correct one. Moreover, your answer explains perfectly what happens, thank you a lot.

    – klaus
    May 26 '17 at 11:33


















0














To write the file prog.pid (with remote pid) on the local machine just put out the redirection from inside quotes



$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!' > prog.pid


If the pid wanted is ssh local process echo $! must be taken out ssh command



$SSH_COMMAND root@server "(nohup $PROG_CMD)" & echo $! > prog.pid





share|improve this answer























  • Nope, I tried and it did not change anything. The issue is not about writing PID in a file but writing the good PID !

    – klaus
    May 26 '17 at 9:49











  • Have you read correctly the answer as in the question it is not clear which PID is interesting, the first command gives the PID of nohup command executed on remote server, whereas the second the PID of local ssh command

    – Nahuel Fouilleul
    May 26 '17 at 9:56











  • I am interested in getting the PID of nohup command, I tried your answer putting out the redirection from inside quotes and the PID in the prog.pid was 11043 whereas the real PID of my program was 11044.

    – klaus
    May 26 '17 at 11:24











  • it may be due to parentheses that were initially they start a sub-shell so 11043 is the PID of remote shell process and 11044 of the sub-shell, just remove the parentheses

    – Nahuel Fouilleul
    May 26 '17 at 12:00












  • I’m not sure but the answer from @whjm solved the issue.

    – klaus
    May 26 '17 at 12:04











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
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44196445%2fget-pid-of-nohup-process-through-ssh%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









3














Don't use (command &) &. Just use (command) & (or just command &). With (command &) &, Bash needs to fork another sub-shell to run the command so $! would be the PID of the sub-shell other than the command.



See following example:



[STEP 124] # (nohup sleep 1234 > /dev/null 2>&1 &) &
[1] 44420 <=== this is the PID of the sub-shell which died immediately
[STEP 125] #
[1]+ Done ( nohup sleep 1234 > /dev/null 2>&1 & )
[STEP 126] # ps p 44420 <=== as you can see this PID does not exist any more
PID TTY STAT TIME COMMAND
[STEP 127] # ps -C sleep u
USER PID TTY STAT START TIME COMMAND
root 44421 pts/13 S 17:48 0:00 sleep 1234
[STEP 128] # kill 44421
[STEP 129] #


This would work fine:



[STEP 131] # (nohup sleep 1234 > /dev/null 2>&1) &
[1] 44424 <=== this is the PID of the sleep command
[STEP 132] # ps p 44424 u
USER PID TTY STAT START TIME COMMAND
root 44424 pts/13 S 17:49 0:00 sleep 1234
[STEP 133] #





share|improve this answer

























  • You were right, I deleted the & and the PID was the correct one. Moreover, your answer explains perfectly what happens, thank you a lot.

    – klaus
    May 26 '17 at 11:33















3














Don't use (command &) &. Just use (command) & (or just command &). With (command &) &, Bash needs to fork another sub-shell to run the command so $! would be the PID of the sub-shell other than the command.



See following example:



[STEP 124] # (nohup sleep 1234 > /dev/null 2>&1 &) &
[1] 44420 <=== this is the PID of the sub-shell which died immediately
[STEP 125] #
[1]+ Done ( nohup sleep 1234 > /dev/null 2>&1 & )
[STEP 126] # ps p 44420 <=== as you can see this PID does not exist any more
PID TTY STAT TIME COMMAND
[STEP 127] # ps -C sleep u
USER PID TTY STAT START TIME COMMAND
root 44421 pts/13 S 17:48 0:00 sleep 1234
[STEP 128] # kill 44421
[STEP 129] #


This would work fine:



[STEP 131] # (nohup sleep 1234 > /dev/null 2>&1) &
[1] 44424 <=== this is the PID of the sleep command
[STEP 132] # ps p 44424 u
USER PID TTY STAT START TIME COMMAND
root 44424 pts/13 S 17:49 0:00 sleep 1234
[STEP 133] #





share|improve this answer

























  • You were right, I deleted the & and the PID was the correct one. Moreover, your answer explains perfectly what happens, thank you a lot.

    – klaus
    May 26 '17 at 11:33













3












3








3







Don't use (command &) &. Just use (command) & (or just command &). With (command &) &, Bash needs to fork another sub-shell to run the command so $! would be the PID of the sub-shell other than the command.



See following example:



[STEP 124] # (nohup sleep 1234 > /dev/null 2>&1 &) &
[1] 44420 <=== this is the PID of the sub-shell which died immediately
[STEP 125] #
[1]+ Done ( nohup sleep 1234 > /dev/null 2>&1 & )
[STEP 126] # ps p 44420 <=== as you can see this PID does not exist any more
PID TTY STAT TIME COMMAND
[STEP 127] # ps -C sleep u
USER PID TTY STAT START TIME COMMAND
root 44421 pts/13 S 17:48 0:00 sleep 1234
[STEP 128] # kill 44421
[STEP 129] #


This would work fine:



[STEP 131] # (nohup sleep 1234 > /dev/null 2>&1) &
[1] 44424 <=== this is the PID of the sleep command
[STEP 132] # ps p 44424 u
USER PID TTY STAT START TIME COMMAND
root 44424 pts/13 S 17:49 0:00 sleep 1234
[STEP 133] #





share|improve this answer















Don't use (command &) &. Just use (command) & (or just command &). With (command &) &, Bash needs to fork another sub-shell to run the command so $! would be the PID of the sub-shell other than the command.



See following example:



[STEP 124] # (nohup sleep 1234 > /dev/null 2>&1 &) &
[1] 44420 <=== this is the PID of the sub-shell which died immediately
[STEP 125] #
[1]+ Done ( nohup sleep 1234 > /dev/null 2>&1 & )
[STEP 126] # ps p 44420 <=== as you can see this PID does not exist any more
PID TTY STAT TIME COMMAND
[STEP 127] # ps -C sleep u
USER PID TTY STAT START TIME COMMAND
root 44421 pts/13 S 17:48 0:00 sleep 1234
[STEP 128] # kill 44421
[STEP 129] #


This would work fine:



[STEP 131] # (nohup sleep 1234 > /dev/null 2>&1) &
[1] 44424 <=== this is the PID of the sleep command
[STEP 132] # ps p 44424 u
USER PID TTY STAT START TIME COMMAND
root 44424 pts/13 S 17:49 0:00 sleep 1234
[STEP 133] #






share|improve this answer














share|improve this answer



share|improve this answer








edited Nov 15 '18 at 2:30

























answered May 26 '17 at 9:58









pynexjpynexj

10.1k41836




10.1k41836












  • You were right, I deleted the & and the PID was the correct one. Moreover, your answer explains perfectly what happens, thank you a lot.

    – klaus
    May 26 '17 at 11:33

















  • You were right, I deleted the & and the PID was the correct one. Moreover, your answer explains perfectly what happens, thank you a lot.

    – klaus
    May 26 '17 at 11:33
















You were right, I deleted the & and the PID was the correct one. Moreover, your answer explains perfectly what happens, thank you a lot.

– klaus
May 26 '17 at 11:33





You were right, I deleted the & and the PID was the correct one. Moreover, your answer explains perfectly what happens, thank you a lot.

– klaus
May 26 '17 at 11:33













0














To write the file prog.pid (with remote pid) on the local machine just put out the redirection from inside quotes



$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!' > prog.pid


If the pid wanted is ssh local process echo $! must be taken out ssh command



$SSH_COMMAND root@server "(nohup $PROG_CMD)" & echo $! > prog.pid





share|improve this answer























  • Nope, I tried and it did not change anything. The issue is not about writing PID in a file but writing the good PID !

    – klaus
    May 26 '17 at 9:49











  • Have you read correctly the answer as in the question it is not clear which PID is interesting, the first command gives the PID of nohup command executed on remote server, whereas the second the PID of local ssh command

    – Nahuel Fouilleul
    May 26 '17 at 9:56











  • I am interested in getting the PID of nohup command, I tried your answer putting out the redirection from inside quotes and the PID in the prog.pid was 11043 whereas the real PID of my program was 11044.

    – klaus
    May 26 '17 at 11:24











  • it may be due to parentheses that were initially they start a sub-shell so 11043 is the PID of remote shell process and 11044 of the sub-shell, just remove the parentheses

    – Nahuel Fouilleul
    May 26 '17 at 12:00












  • I’m not sure but the answer from @whjm solved the issue.

    – klaus
    May 26 '17 at 12:04
















0














To write the file prog.pid (with remote pid) on the local machine just put out the redirection from inside quotes



$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!' > prog.pid


If the pid wanted is ssh local process echo $! must be taken out ssh command



$SSH_COMMAND root@server "(nohup $PROG_CMD)" & echo $! > prog.pid





share|improve this answer























  • Nope, I tried and it did not change anything. The issue is not about writing PID in a file but writing the good PID !

    – klaus
    May 26 '17 at 9:49











  • Have you read correctly the answer as in the question it is not clear which PID is interesting, the first command gives the PID of nohup command executed on remote server, whereas the second the PID of local ssh command

    – Nahuel Fouilleul
    May 26 '17 at 9:56











  • I am interested in getting the PID of nohup command, I tried your answer putting out the redirection from inside quotes and the PID in the prog.pid was 11043 whereas the real PID of my program was 11044.

    – klaus
    May 26 '17 at 11:24











  • it may be due to parentheses that were initially they start a sub-shell so 11043 is the PID of remote shell process and 11044 of the sub-shell, just remove the parentheses

    – Nahuel Fouilleul
    May 26 '17 at 12:00












  • I’m not sure but the answer from @whjm solved the issue.

    – klaus
    May 26 '17 at 12:04














0












0








0







To write the file prog.pid (with remote pid) on the local machine just put out the redirection from inside quotes



$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!' > prog.pid


If the pid wanted is ssh local process echo $! must be taken out ssh command



$SSH_COMMAND root@server "(nohup $PROG_CMD)" & echo $! > prog.pid





share|improve this answer













To write the file prog.pid (with remote pid) on the local machine just put out the redirection from inside quotes



$SSH_COMMAND root@server "(nohup $PROG_CMD) & echo "'$!' > prog.pid


If the pid wanted is ssh local process echo $! must be taken out ssh command



$SSH_COMMAND root@server "(nohup $PROG_CMD)" & echo $! > prog.pid






share|improve this answer












share|improve this answer



share|improve this answer










answered May 26 '17 at 9:22









Nahuel FouilleulNahuel Fouilleul

14.6k11726




14.6k11726












  • Nope, I tried and it did not change anything. The issue is not about writing PID in a file but writing the good PID !

    – klaus
    May 26 '17 at 9:49











  • Have you read correctly the answer as in the question it is not clear which PID is interesting, the first command gives the PID of nohup command executed on remote server, whereas the second the PID of local ssh command

    – Nahuel Fouilleul
    May 26 '17 at 9:56











  • I am interested in getting the PID of nohup command, I tried your answer putting out the redirection from inside quotes and the PID in the prog.pid was 11043 whereas the real PID of my program was 11044.

    – klaus
    May 26 '17 at 11:24











  • it may be due to parentheses that were initially they start a sub-shell so 11043 is the PID of remote shell process and 11044 of the sub-shell, just remove the parentheses

    – Nahuel Fouilleul
    May 26 '17 at 12:00












  • I’m not sure but the answer from @whjm solved the issue.

    – klaus
    May 26 '17 at 12:04


















  • Nope, I tried and it did not change anything. The issue is not about writing PID in a file but writing the good PID !

    – klaus
    May 26 '17 at 9:49











  • Have you read correctly the answer as in the question it is not clear which PID is interesting, the first command gives the PID of nohup command executed on remote server, whereas the second the PID of local ssh command

    – Nahuel Fouilleul
    May 26 '17 at 9:56











  • I am interested in getting the PID of nohup command, I tried your answer putting out the redirection from inside quotes and the PID in the prog.pid was 11043 whereas the real PID of my program was 11044.

    – klaus
    May 26 '17 at 11:24











  • it may be due to parentheses that were initially they start a sub-shell so 11043 is the PID of remote shell process and 11044 of the sub-shell, just remove the parentheses

    – Nahuel Fouilleul
    May 26 '17 at 12:00












  • I’m not sure but the answer from @whjm solved the issue.

    – klaus
    May 26 '17 at 12:04

















Nope, I tried and it did not change anything. The issue is not about writing PID in a file but writing the good PID !

– klaus
May 26 '17 at 9:49





Nope, I tried and it did not change anything. The issue is not about writing PID in a file but writing the good PID !

– klaus
May 26 '17 at 9:49













Have you read correctly the answer as in the question it is not clear which PID is interesting, the first command gives the PID of nohup command executed on remote server, whereas the second the PID of local ssh command

– Nahuel Fouilleul
May 26 '17 at 9:56





Have you read correctly the answer as in the question it is not clear which PID is interesting, the first command gives the PID of nohup command executed on remote server, whereas the second the PID of local ssh command

– Nahuel Fouilleul
May 26 '17 at 9:56













I am interested in getting the PID of nohup command, I tried your answer putting out the redirection from inside quotes and the PID in the prog.pid was 11043 whereas the real PID of my program was 11044.

– klaus
May 26 '17 at 11:24





I am interested in getting the PID of nohup command, I tried your answer putting out the redirection from inside quotes and the PID in the prog.pid was 11043 whereas the real PID of my program was 11044.

– klaus
May 26 '17 at 11:24













it may be due to parentheses that were initially they start a sub-shell so 11043 is the PID of remote shell process and 11044 of the sub-shell, just remove the parentheses

– Nahuel Fouilleul
May 26 '17 at 12:00






it may be due to parentheses that were initially they start a sub-shell so 11043 is the PID of remote shell process and 11044 of the sub-shell, just remove the parentheses

– Nahuel Fouilleul
May 26 '17 at 12:00














I’m not sure but the answer from @whjm solved the issue.

– klaus
May 26 '17 at 12:04






I’m not sure but the answer from @whjm solved the issue.

– klaus
May 26 '17 at 12:04


















draft saved

draft discarded
















































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.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f44196445%2fget-pid-of-nohup-process-through-ssh%23new-answer', 'question_page');

);

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







Popular posts from this blog

Darth Vader #20

How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

Ondo