-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Screen and nohup are both handy tools; I read the original post as saying that the netcat instance was actually crashing rather than just not persisting through a closed window (though in this case, netcat would need to be run in screen/nohup in any case - I had assumed this was the case originally).
Cheers, James Harrison On 11 May 2012 15:03:55, drew Roberts wrote: > On Friday 11 May 2012 08:11:59 Wayne Merricks wrote: >> nohup basically means the process will keep running after the terminal >> is closed (or your ssh session has ended). >> >> e.g on start up run: >> >> nohup command_to_run > path_to_file_to_save_output & >> >> This should make the command run in the background with all output >> logged to the file specified > > I like screen. I can reattach and see what is going on rather than looking at > a file. Control things that can be controlled. > > I need to think if there are times where nohup would make more sense though. > > all the best, > > drew > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+tLV0ACgkQ22kkGnnJQAwjLACgtDTKOAUbMijYDkjZJmSW5xm6 MZkAnjFKuwVaTDmszbUFerUBkulXlSud =Ha6v -----END PGP SIGNATURE----- _______________________________________________ Rivendell-dev mailing list [email protected] http://lists.rivendellaudio.org/mailman/listinfo/rivendell-dev
