FSLMACHINELIST: | a list of machines on which bedpost should be run. Each machine can be included more than once to make use of multiple processor machines. | FSLREMOTECALL: | The program you want to use to make the remote calls, e.g. ssh or rsh |
bash user:FSLMACHINELIST="machine1 machine1 machine2 machine3 machine5" FSLREMOTECALL=ssh export FSLMACHINELIST FSLREMOTECALLbedpost to use ssh to send jobs to two processors on machine1, and one each on machine2 machine3 machine5.fsl.sh, on each
machine listed, in one of the following places./usr/local/etc/fslconf/fsl.sh/etc/fslconf/fsl.sh${HOME}/.fslconf/fsl.shFSLDIR in sh language. e.g.:FSLDIR=/usr/local/fslexport FSLDIRFSLMACHINELIST and FSLREMOTECALL). This is absolutely fine, as long as it also sets FSLDIRcsh or tcsh user you may
already have an equivalent fsl.csh in one of the above
directories. Note that you still need to specify the
fsl.sh file as above. Parallel bedpost uses
sh not csh.FSLLOCKDIR environment variable to a directory which is
writeable by all users. Every time a bedpost starts, it will write
${FSLLOCKDIR}/.bedpost.lock which will be removed when
bedpost completes. If this file is present, new bedpost processes will
not start.
bedpost_cleanup, which
will kill all bedpost related processes owned by the user
on all machines in $FSLMACHINELIST.