My nohup.out file is growing fast.
I am running an application in the background, it's writing nohup.out file,
now I need to rotate nohup.out file without killing my application. Can this be done?
Is it possible to let a process started with nohup, write to stdout instead of in a file? or maybe in the file and on the screen?
nohup python start.py &
writes to nohup.out, but I'd like it to output to the screen, nohup is only meant as a hedge when the connection breaks.
Ive seen tons of examples where a & follows the end of a command string, but I can't seem to find an explanation on what it does. It's not even in nohup's man page. Is this a shell thing?
Either using & or not, I find that any process ran with nohup seems to exhibit immunity to any hangup signal.
nohup runs a process in the background. There is any equivalent for Windows?
I'm doing some test-runs of long-running data migration scripts, over SSH. Let's say I start running a script around 4 PM; now, 6 PM rolls around, and I'm cursing myself for not doing this all in screen.
Is there any way to "retroactively" nohup a process, or do I need to leave my computer online all night? If it's not possible to attach screen to/nohup a process I've already started, then why? Something to do with how parent/child proceses interact? (I won't accept a "no" answer that doesn't at least address the question of 'why' -- sorry ;) )