hey all,
I've had a few jobs that were recently terminated due to a broken ssh pipe, is there anything i should do to before re-running those same jobs in order to avoid any issues?
jon
Jon,
The way to solve this problem is to use the "nohup" command, for example:
$nohup recon-all -s testsubject1 -all
-Zeke
On 07/18/2013 12:41 PM, Jonathan Holt wrote:
hey all,
I've had a few jobs that were recently terminated due to a broken ssh pipe, is there anything i should do to before re-running those same jobs in order to avoid any issues?
jon _______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
Hi Jon, Also, delete the IsRunning.lh+rh file in the scripts recon dir, or add the '-no-isrunning' flag to the recon-all command when re-running. -Louis
On Thu, 18 Jul 2013, Z K wrote:
Jon,
The way to solve this problem is to use the "nohup" command, for example:
$nohup recon-all -s testsubject1 -all
-Zeke
On 07/18/2013 12:41 PM, Jonathan Holt wrote:
hey all,
I've had a few jobs that were recently terminated due to a broken ssh pipe, is there anything i should do to before re-running those same jobs in order to avoid any issues?
jon _______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
you should be able to run
recon-all -s <subject> -sd <subjects_dir> -make all
On Thu, 18 Jul 2013, Jonathan Holt wrote:
hey all,
I've had a few jobs that were recently terminated due to a broken ssh pipe, is there anything i should do to before re-running those same jobs in order to avoid any issues?
jon _______________________________________________ Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
freesurfer@nmr.mgh.harvard.edu