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

Re:[Condor-users] MSI install

 Hmm looks very feasible.
 Thanks Colin!

 Just to understand better these issues, I installed condor on my system and
 then stopped the service (net stop condor).
 I looked at the registry and I saw these entries:


 Well, then I changed the config files and started the service again and
 the registry didn't change at all, even the ones I changed like svRelay,
 svDomain, svWriteAccess. Thing is, I see condor changing behaviour.

 Later on the road, I stopped the service again and renamed the registry
 in order to check closer these dependencies. I created an empty folder
 with just only one key:
 pointing to the proper configuration file.

 So far, so good. I was expecting Condor to refresh these entries from the
 config file but it does not. The registry remains clean.  Actually I see
 systray_cpy_0_state added but I guess this is birdwatcher working, isn't

 So the conclusion is - those are like test leftover that in some way got
 into production. Does condor use those entries at any time?


> ----- Original Message ----- 
> From: "Colin Stolley" <stolley@xxxxxxxxxxx>
> To: "Condor-Users Mail List" <condor-users@xxxxxxxxxxx>
> Sent: Friday, August 06, 2004 12:49 PM
> Subject: Re: [Condor-users] MSI install
> > > I'm trying to build a custom MSI install of condor. So far I have
> > > customized versions of condor_local and condor_local.config but not
> > > what registry keys or any further customization need to be done.
> > > Thoughts?
> >
> > Henrique,
> >
> > Here's a few tips:
> >
> > 1. You can use MSI to treat the config files in the same manner in
> > windows INI files. We allow our config files to contain lines starting
> > with '[', which to Condor is a comment, but to MSI is the beginning of
> > a section in the INI file.
> >
> > 2. The only registry key you need to worry about is:
> >
> >
> > This string tells Condor where the main config file for that machine
> > is located (path and filename).
> >
> > 3. You'll also have to install Condor as a service, and you'll want to
> > make sure that it's set up to run as local system.
> >
> > good luck,
> > Colin
> > _______________________________________________
> > Condor-users mailing list
> > Condor-users@xxxxxxxxxxx
> > http://lists.cs.wisc.edu/mailman/listinfo/condor-users
> >