Feature #2172: Making config file location optional during reconfig
Changing the location of setup scripts factory.sh and frontend.sh
While we are streamlining the startup scritps we might as well change the location of setup scrips factory.sh and frontend.sh to their respective configuration directory or the workspace. I like the config dir better. There is no reason to keep them hanging and wandering about in the glideinsubmit and frontstage area.
#5 Updated by John Weigand over 8 years ago
Suggestion to think about:
The only data in these 2 scripts is:
- exports X509_CERT_DIR
only needed if /etc/grid-security/certificates is not available
- and it is sourcing the wms collectors condor.sh env script
- only sourcing the frontend's condor condor.sh env script
We would not need these scripts if we included these attributes
in the configuration xml files of each. That would make it all very self-contained.
OK... I am prepared to get slammed on this great idea. Fire away.
#6 Updated by John Weigand over 8 years ago
- Status changed from New to Feedback
- Assignee changed from John Weigand to Parag Mhashilkar
I never got any feedback on my original suggestion regarding
including the pieces of data in the setup scripts in
the respective config files. The startup scripts created for
both can have this included thus making it all very
self-contained and insures the environment is set correctly.
It would eliminate those 2 files completely.
It makes it "one-stop shopping" so to speak.