[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Hostname problem, OSX 10.5
- Date: Thu, 4 Oct 2012 02:26:47 +0000
- From: "Jewell, Chris" <C.P.Jewell@xxxxxxxxxxxx>
- Subject: Re: [Condor-users] Hostname problem, OSX 10.5
On 4 Oct 2012, at 15:19, Kevin Buckley wrote:
> On 2 October 2012 17:04, Chris Jewell <c.p.jewell@xxxxxxxxxxxx> wrote:
>> Does anyone have any tips for how I might delay the start of the Condor
>> daemons until after networking is up, or prevent them from binding to the
>> loopback address?
> Fixing the NETWORK_INTERFACE in a per-machine condor file isn't a good
> thing if you think that it might change at some later time.
I agree. However, as our institute (Massey University) uses the 184.108.40.206/16 address pool, this shouldn't be an issue for us.
> You really want to be delaying the start of the Condor invocation by making it
> depend on the networking script that fetches the DHCP lease has been run.
> Can the Mac OS initialisation scripts not be made to depend on others?
If only. According to the Apple doc, launchd apparently delegates evaluation of dependencies to the daemon itself, cf. init or upstart on Linux...