Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
1 1 11
Newest
 Curious
Impact
~18k people reached

  • 0 posts edited
  • 0 helpful flags
  • 16 votes cast
Apr
30
comment Why %H%M%S is not working in .screenrc?
Ok, I understand, thank you
Apr
30
comment Why %H%M%S is not working in .screenrc?
@cas Oops, thank you correcting
Apr
30
comment Why %H%M%S is not working in .screenrc?
Thank you very much. That is the list I am looking for. But is there really no way to manipulate the filename to delete the semicolon?
Apr
30
comment Is there a difference between nohup and nohup in a screen?
Sorry for my unclear post. Actually my program generate outputs at first, however sometimes it just stopped in the middle without any error message. Just "peacefully" stopped without any traceable info. Ok, I want to make sure one point: Is nohup at the same safety level as screen in terms of background job stability?
Apr
30
comment Is there a difference between nohup and nohup in a screen?
Hi, Anthon. Thank you for answering. I don't understand " if it doesn't output anything when using nohup you will not get more information when running inside screen". If all the output including error are redirected to file, what else am I missing from nohup.out?
Apr
30
comment how to force `screen -L` to overwrite log?
Ok, I'll accept yours. Thank you very much :)
Apr
30
comment how to force `screen -L` to overwrite log?
I updated my post. I think these two questions closely related. So I make it one. And I guess you know both answers : )
Apr
30
comment how to force `screen -L` to overwrite log?
So you mean your method probably the only way? I just saw this unix.stackexchange.com/a/257859/31374 ? However I can't reproduce the result, don't know why
Apr
30
comment how to force `screen -L` to overwrite log?
This works! Thank you very much. But do you know why redirection is not working in screen command? for example, screen -dmS xxx ls>ls.dat
Apr
30
comment how to force `screen -L` to overwrite log?
Hi, EightBitTony. Thank you for answering. But generally, we start screen in different folder(corresponding to different job), the logfiles are then in different folder.
Apr
30
comment Do I really need -dmS option in screen to run background job stably even log out?
Thank you very much for detailed information, very useful : )
Apr
30
comment Do I really need -dmS option in screen to run background job stably even log out?
Thank you nanovad
Apr
30
comment Do I really need -dmS option in screen to run background job stably even log out?
Thank you so much. I tried to write a summary, to see if I am wrong somewhere : )
Apr
30
comment How do I kill all screens?
Hi, Rahul Patil. why screen is not listed in Top
Apr
29
comment Do I really need -dmS option in screen to run background job stably even log out?
Hi, Eric Renouf. I don't quite understand "You would only use -dm if you want to run a command in a screen session and not enter it interactively" . -dm mean detached, how could I run command without enter it? If I enter the screen, then it is interactive. Am I right?
Apr
20
comment Why “lsof” is not working when it used in ssh?
-of really works. Since my a.out is an MPI executable. -of found the PID of the oldest a.out command, that is mpiexec.hydra -n 6 ./a.out, and the sshed lsof could resolve this PID properly. Though I still don't know why it can't resolve the MPI process correctly.
Apr
20
comment Why “lsof” is not working when it used in ssh?
Hi, cuongnv. I probably can't agree with you. The -n option just gives the newest generated process, but as I tested, this doesn't include pgrep itself, you can see from pgrep -lf sleep. The reason you got different PID maybe because there are many sleep command running that you don't know.
Apr
20
comment Why “lsof” is not working when it used in ssh?
The output is like this s000.tinyupload.com/?file_id=81160837964911972942
Apr
20
comment Why “lsof” is not working when it used in ssh?
actually, if I grep txt, it gives /bin/bash, while it should be the path to a.out
Apr
20
comment Why “lsof” is not working when it used in ssh?
a.out is the exectuable. I just tried ssh i01n10 'pgrep -nf a.out | xargs /usr/sbin/lsof -p', though it gives output now, but the results is wrong. It should give the path where the running a.out is located.