ranganathanm
commented
9 years ago I did not realize /var/tmp is root only access (on our linux installs it is not). I wonder why it is owned by root in your system.
From: Douglas Anderson notifications@github.com Sent: Monday, May 18, 2015 10:44 AM To: usnistgov/SpectrumBrowser Cc: Ranganathan, Mudumbai Subject: [SpectrumBrowser] Having ant install MSODConfig.json creates difficulties (#175)
@ranganathanmhttps://github.com/ranganathanm,
I know you asked me for input on this, so I apologize for getting back to you about it after you implemented it.
Using ant to dynamically create/install the the MSODConfig is causing a few problems. Now you have to run the build with root privs (to write to /var/tmp), and that in turn nukes the environment, unless run with "sudo -E", so the build fails on finding GWT_HOME.
As part of my Makefile branch, I've implemented an "install" target that does exactly what we need for the MSOD config: it takes a existing conf file saved somewhere in the SpectrumBrowser dir structure, modifies it if necessary (like hard-coding the location of the repository) and then installs them into the /etc directory, which is the preferred location for system-wide config files.
I propose to revert the changes to ant build, create a "msod.conf" file with some default parameters, then use Makefile to install that into /etc/msod.conf. It can still be json.
Again, I know you asked me for comments on this before. I just picked this back up after about 2 weeks "off".
What do you think?
Reply to this email directly or view it on GitHubhttps://github.com/usnistgov/SpectrumBrowser/issues/175.
djanderson
@ranganathanm,
I know you asked me for input on this, so I apologize for getting back to you about it after you implemented it.
Using ant to dynamically create/install the the MSODConfig is causing a few problems. Now you have to run the build with root privs (to write to /var/tmp), and that in turn nukes the environment, unless run with "sudo -E", so the build fails on finding GWT_HOME.
As part of my Makefile branch, I've implemented an "install" target that does exactly what we need for the MSOD config: it takes a existing conf file saved somewhere in the SpectrumBrowser dir structure, modifies it if necessary (like hard-coding the location of the repository) and then installs them into the /etc directory, which is the preferred location for system-wide config files.
I propose to revert the changes to ant build, create a "msod.conf" file with some default parameters, then use Makefile to install that into /etc/msod.conf. It can still be json.
Again, I know you asked me for comments on this before. I just picked this back up after about 2 weeks "off".
What do you think?