When connecting to remote servers (Solaris/ksh) we set the
environment up for 'nohup' and start our multi-hour job
(redirecting stdout/stderr to a file) in the background.
Should that window 'disappear' (due to network instability)
then the job dies; should we just 'logout' the job keeps
Our understanding is that nohup and redirecting stdout/stderr
and backgrounding should keep the job alive regardless.
Incidentally there is no 'tee' command in the script.
% nohup pt_shell -f ../scripts/m12_master.pt > m12_master.log 2>&1 &