As long as *tj* user has no jobs in any of the HTCondor schedd queues, he can be moved to a new schedd merely by changing the contents of =/home/tj/.condor/user_config= file. This can happen even while *tj* is logged in, since the file is re-parsed by each invocation of =condor_q= or =condor_submit=
-Whether or not *tj* has any jobs in any of the schedd's can be determined by running {term}condor_status -submit tj@chtc.wisc.edu -af Machine 'HeldJobs+IdleJobs+RunningJobs+LocalJobsIdle+LocalJobsRunning'{endterm} or the equivalent command via the HTCondor python bindings.
+Whether or not *tj* has any jobs in any of the schedd's can be determined by running {term}condor_status -submit tj@chtc.wisc.edu -af Machine 'HeldJobs+IdleJobs+RunningJobs+LocalJobsIdle+LocalJobsRunning'{endterm}{verbatim} submit-3.chtc.wisc.edu 3{endverbatim} or the equivalent command via the HTCondor python bindings.
{subsection: Schedd failover}
-to be written
+
+If the schedd's job queue is stored on the shared file system, HTCondor can be configured so that when a given machine fails, any schedd's running on it will be automatically restarted on the backup machine, but with the same schedd name.
+
+*details to be written*
