Re: [Condor-users] Starting condor_master on boot

[Erik Paulson <epaulson@xxxxxxxxxxx>]

On Thu, Jul 20, 2006 at 04:23:36PM +0100, James Osborne wrote:
> Hi Ian
> 
> I managed it, it was a booting sequence problem i.e. when condor starts it is
> trying to look in "linux.local" picking up the hostname before it is reassigned
> using DHCP to "hostname.local" where the files actually reside; and resultantly
> a configuration problem.  Your instructions confirmed I was doing the right
> thing before, so I...
> 
> 1) Moved the directories from linux.local up a level to the opt/condor-6.6.11
> directory (solving DHCP issue)
> 2) Altered the condor_config file to contain the variables I wanted
> 3) Put the config file in /opt/condor-6.6.11/etc/condor_config
> 4) Altered your init.d script to point to the appropriate locations
> 
> The moral of the story is that if your machines use DHCP to reassign the
> hostname, running condor_configure --install --type=execute
> --central-manager=hostname... --owner=condor doesn't configure things
> apropriately, sure condor will run when invoked from a shell post boot and DHCP
> assign, but a little rearranging is needed to get around the issue when the
> condor init.d runs before dhcp...
> 

Wouldn't it be better to just have the condor startup script run after DHCP,
since Condor depends on the network working?

-Erik