Re: [HTCondor-users] COLLECTOR_NAME

[Andrew Mole <Andrew.Mole@xxxxxxxx>]

Thank you for this. I am still not quite clear on the specifics. The condor_collector daemon is running on the central computer, so I can see that the designation on that machine is the important one. But what happens if COLLECTOR_NAME is set incorrectly on one of the pool machines? Will they fail to be able to service or submit tasks? Will they think they are in a different pool?

Andrew



On 19 Jun, 2013, at 9:01 PM, "Matthew Farrellee" <matt@xxxxxxxxxx> wrote:

> On 06/18/2013 11:35 PM, Andrew Mole wrote:
>> What exactly does the COLLECTOR_NAME do, and does it need to be set to
>> be the same on all machines in the pool?
>> 
>> I have looked in the manual, but all it says is that:
>> 
>> “The parameter is used to specify a short description of your pool. It
>> should be about 20 characters long. For example, the name of the
>> UW-Madison Computer Science Condor Pool is ``UW-Madison CS''.”
>> 
>> Does it matter if the names do not match in all the config files (and
>> are they case-sensitive)? After all, the CONDOR_HOST is set separately.
>> If it does not matter, what name is announced to the world as the pool name?
> 
> COLLECTOR_NAME is only used by the condor_collector daemon.
> 
> The name announced to the world as the pool name is the value read by the condor_collector.
> 
> Best,
> 
> 
> matt
> 
____________________________________________________________
Electronic mail messages entering and leaving Arup  business
systems are scanned for acceptability of content and viruses