 |
 |
The thing is, for now, it should abort. In production, I'm not sure it should. At the very least, it should retry for some time. -Daniel (this wouldn't be such a problem if the worker embedded its own mysqld or was responsible for starting it) On 03/05/2014 09:27 AM, Becla, Jacek wrote: > Daniel > > I noticed xrootd will happily start even if it can't connect > to mysql. It will only print a message: > > Configration invalid: Unable to connect to MySQL with config: > > which can be easily overlooked. I propose to make this a fatal > error and abort. Sounds ok? Should I open a ticket? > > Jacek ######################################################################## 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