Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • Take a look at this thread: unix.stackexchange.com/questions/4004/… Commented Sep 22, 2013 at 13:24
  • Also if you search through these Q's on the site you'll find additional examples and guidance: unix.stackexchange.com/search?tab=votes&q=nohup Commented Sep 22, 2013 at 13:24
  • Is your job-monitor.log not empty when you do a nohup and then empty after you logout and back in? Does script.py finish normally (with a filled log file) if you let it run long enough without login out? Apart from finding the reason for why this happens, you can try tmux or screen Commented Sep 22, 2013 at 13:30
  • 1
    @slm: This question is not a duplicate of How can I close a terminal without killing the command running in it?. The accepted answer to that question gives two methods that I explicitly stated in my question do not work in this case. Users with the same problem as I have should not be redirected to an answer that doesn't solve their problem. Commented Sep 22, 2013 at 17:58
  • Based on the information you've provided that Q&A is the most related and has all the information regarding the topic, from what I know of Unix & Linux. I understand your frustration, but we need more info to go on in order to assist you more than what's here. Commented Sep 22, 2013 at 18:11