The processes are
started as root but run as the user condor. The execute nodes get their
/home/condor served up by NFS and the dirs are auto-mounted. My global
condor_config is in /opt/condor/etc/condor_config and there is a symlink
from /home/condor/condor_config to this file.
I'm seeing some strange behavior both when I start up condor_master and
when I submit jobs to the pool. In the case of condor_master, if I start
this process without first doing an 'ls /home/condor' it dies with a
complaint about not having CONDOR_CONFIG set, not being able to find
/etc/condor/condor_config, or not being able to find
/local/condor/condor_config. The complaint also mentions not finding
~/condor. When I trace the condor_master with strace, however, it doesn't
look like an open() attempt is ever made on ~/condor_config. Eventhough
df shows /home/condor as already mounted, if I 'ls /home/condor', however,
it succeeds in checking for and finding this directory. It seems there is
some reason condor is not even attempting to open
/home/condor/condor_config.
Best, Tim