GabrieleManduchi
commented
3 years ago I agree on all the suggestions, as soon as I find some time I will implement them, unless........someone volunteers doing it before:-)
On 7/9/2021 8:37 PM, Stephen Lane-Walsh wrote:
Currently, it seems that jScope only reads a config file from $HOME/jscope/jScope.properties This can be changed by specifying a file on the command line with |-fp|, or by changing the path in the system properties. However, we propose adding a set of paths that it will search for and process one or all of the files it finds.
For example:
- Process /usr/local/mdsplus/jscope/jScope.properties for system-wide configuration of servers and such
- Process $HOME/jscope/jScope.properties
Any properties set by the system-wide configuration could then be overridden by the user-specific one, if desired.
Any ideas on this would be appreciated.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/MDSplus/mdsplus/issues/2345, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACCLESFSD6PQ6N3AQ5HREB3TW46WVANCNFSM5ADIB2CQ.
-- Gabriele Manduchi
Istituto Gas Ionizzati del CNR Consorzio RFX - Associazione EURATOM/ENEA sulla Fusione Corso Stati Uniti 4, 35127 Padova - Italy ph +39-049-829-5039/-5000 fax +39-049-8700718 @.***, http://www.igi.cnr.it
Currently, it seems that jScope only reads a config file from $HOME/jscope/jScope.properties This can be changed by specifying a file on the command line with
-fp, or by changing the path in the system properties. However, we propose adding a set of paths that it will search for and process one or all of the files it finds.For example:
Any properties set by the system-wide configuration could then be overridden by the user-specific one, if desired.
Any ideas on this would be appreciated.