Jacek Becla added a comment - 22/Mar/14 5:00 PM From trac ticket 2296: There are a number of env. variables that need to be set in the start up of qsrv master, to control the use. These should be moves to config values, to keep them in one place, and not be needed as env. vairables. The env. variables in use now for startup are: QSW_RESULTDIR=/u20/douglas/prod/qserv-run/tmp QSW_XRDQUERYPATH="/q" QSW_DBSOCK="/u20/douglas/prod/var/lib/mysql/mysql.sock" QSW_MYSQLDUMP="/u20/douglas/prod/bin/mysqldump" QSW_SCRATCHPATH="/u20/douglas/prod/tmp" QSW_SCRATCHDB="qservScratch" QSW_RESULTPATH="/u20/douglas/prod/xrootd-run/result" QSW_XRDQUERYPATH="/q" should be eliminated, it is baked into the code. Ask AndyH about directives in the xrootd config file that set environment variables. The qserv fs plugin can then read the environment variables by getenv. In this way, we can set these values in the xrootd configuration and they can be read by the qserv worker plugin.

Fabrice Jammes added a comment - 03/Nov/14 4:25 PM Some Qserv variables are environment variables managed in init.d files, and should by instead managed in configuration files: For mysql-proxy: QSERV_RPC_PORT QSERV_UNIX_USER, if do-able For xrootd: QSW_DBSOCK

Fritz Mueller added a comment - 08/Dec/20 6:49 PM These have meantime been either obsoleted or addressed.