[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-devel] Bug in hostname determination on lo-only systems
- Date: Thu, 23 Feb 2012 11:38:49 -0600
- From: Todd Tannenbaum <tannenba@xxxxxxxxxxx>
- Subject: Re: [Condor-devel] Bug in hostname determination on lo-only systems
On 2/23/2012 3:07 AM, Michael Hanke wrote:
Hi,
Condor (as of 7.7.4) is unable to determine the hostname (on Linux)
whenever no other network interface than loopback is available. This
leads to FULL_HOSTNAME being undefined and consequently all kinds of
trouble.
I have seen this behavior happening independently from the specific
settings of BIND_ALL_INTERFACES and NETWORK_INTERFACE. Running
`hostname` in a console yields the hostname of course.
Admittedly, this doesn't have much of an impact on any real Condor
machine, but I see it every time I'm practicing policy writing on my
laptop in the train.
In the no-network-but still-wanna-play w/ Condor scenarios, I usually do
NETWORK_INTERFACE = 127.0.0.1
and replace FULL_HOSTNAME with $(IP_ADDRESS).
Hmmm... what do folks think about just replacing FULL_HOSTNAME with
IP_ADDRESS in general in our default config files?
Todd
Thanks,
Michael
--
Todd Tannenbaum University of Wisconsin-Madison
Center for High Throughput Computing Department of Computer Sciences
tannenba@xxxxxxxxxxx 1210 W. Dayton St. Rm #4257
Phone: (608) 263-7132 Madison, WI 53706-1685