[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Condor-users] RE: condor_config_val macro bug?



Thx Steve.  I'll use that for now.  I really did like the -config option
because it provided both the local and global config paths with a single
Process instance.  I'll have to use two instances now to get both paths.
Not too big a deal.  Beggars can't be choosers. :)

Thanks again!

Sean

-----Original Message-----
From: condor-users-bounces@xxxxxxxxxxx
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of Steven Timm
Sent: Thursday, July 21, 2005 7:53 AM
To: Matt Hope; Condor-Users Mail List
Subject: Re: [Condor-users] RE: condor_config_val macro bug?


condor_config_val -name (collector.host) LOCAL_CONFIG_FILE
(i.e, the variable name instead of the -config option) will
give you the LOCAL_CONFIG_FILE variable of the central host.

Steve


On Thu, 21 Jul 2005, Matt Hope wrote:

> On 7/21/05, Steven Timm <timm@xxxxxxxx> wrote:
> > 
> >
> <reformatted>
> > > LOCAL_CONFIG_FILE =
> > > $(NET_DIR)\etc\globalClient\$(HOSTNAME)\condor_config.local
> > >
> > >
> > > When I run 'condor_config_val -name dell001 -config' on dell001, I
get
> > > this output:
> > >
> > > Config file:
> > >
> > >         //manager/condor/etc/globalMaster/condor_config
> > >
> > > Local config file:
> > >
> > >
\\manager\Condor\etc\globalClient\dell001\condor_config.local
> > >
> > >
> > >
> > > However, when I run 'condor_config_val -name dell001 -config' on
> > > dell015, I get this output:
> > >
> > >
> > >
> > > Config file:
> > >
> > >         //manager/condor/etc/globalMaster/condor_config
> > >
> > > Local config file:
> > >
> > >
\\manager\Condor\etc\globalClient\dell015\condor_config.local
> > >
> > >
> > >
> > > It appears that condor_config_val is substituting the $(HOSTNAME)
macro
> > > based on the querying machine and not the machine being queried.
Is
> > > this intended or have I discovered a bug?
> > >
> > >
> > >
> > > Sean
> > >
> > >
> >
> > I hope the behavior Sean is describing below is a feature, because
> > I use it to make different config files for different hosts.
> 
> I believe Sean is objecting not to the evaluation of $(HOSTNAME) at
> the initial config file parsing stage (i.e. daemon startup/reconfig)
> but by the remote config interrogation provided by condor_config_val.
> It is being evaluated in relation to the *requesting* machine rather
> than the *responding* machine when remote requesting the value from
> another machine, which sounds like a bug to me...
> 
> Matt
> 
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-users
> 

-- 
------------------------------------------------------------------
Steven C. Timm, Ph.D  (630) 840-8525  timm@xxxxxxxx
http://home.fnal.gov/~timm/
Fermilab Computing Div/Core Support Services Dept./Scientific Computing
Section
Assistant Group Leader, Farms and Clustered Systems Group
Lead of Computing Farms Team
_______________________________________________
Condor-users mailing list
Condor-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/condor-users