Jacek,
> As you may recall we recently decided to rely on my.cnf type file
> in place of pex_policy to deal with passing mysql connection and
> authentication related values. (I've been using "~/.lsst.my.cnf"
> as default location)
Hmm. For human users, I'd rather just use the standard .my.cnf
instead of a custom file, if we could. The goal should be to make it
work just like the mysql client. This should even be possible for qserv
worker usage, I would think.
> I am considering going with something similar for zookeeper.
> Specifically, I am thinking about allowing a subset of the
> options described here:
>
> http://kazoo.readthedocs.org/en/latest/api/client.html
>
> host, timeout, randomize_hosts
>
> in a file with default location ~/.lsst.css.cnf.
That's not good. If we have a lot of these, they should go back
in a .lsst subdirectory.
--
Kian-Tat Lim, LSST Data Management, [log in to unmask]
########################################################################
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
|