 |
 |
Hello Daniel, Indeed, we should rename this file. But it does not only configure qserv_czar, it also contains the most important parameters used by all other Qserv services : mysql-proxy, mysql, xrootd, zookeeper. This file is there to avoid that, by default, the sysadmin has to edit all Qserv services configuration files : all most important parameters are centralized here (this set isn't frozen). NOTE : If sysadmin want to do a very fine tuning, the he will have to edit templates and run scons, or edit manually all Qserv configuration files. Maybe we could rename this file to something like : - configure-whole-qserv.conf - global-qserv.conf - qserv-services.conf - overall-qserv-configuration.in - qserv-motherconf.in Or something else which reflects that this file's parameters will be used to feed all templates in order to build configuration files for all Qserv services. The client configuration file could also be renamed to qserv-integration-tests.conf ? As, for now it's only used by integration tests procedure Have a nice day, Fabrice On Tue, May 27, 2014 9:06 pm, Daniel L. Wang wrote: > Hello, > >>> ./admin/templates/install/admin/qserv.conf >>> >>> >>> Can we standardize on one? >>> >>> > Also, can we rename it to qserv_czar.conf? > > > Thanks, > -Daniel > > > ######################################################################## > Use REPLY-ALL to reply to list > > > To unsubscribe from the QSERV-L list, click the following link: > https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1 > > ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1