On 05 Dec 07, Tom Collins wrote: > On Dec 5, 2007, at 2:51 AM, Hartmut Wernisch wrote: > >So now I am wondering why line 197-202 is setting the values to > >MYSQL_READ_SOCKET and MYSQL_READ_PORT instead of MYSQL_UPDATE_SOCKET > >and MYSQL_UPDATE_PORT? > > > >In my opinion these values should be set to MYSQL_UPDATE_SOCKET and > >MYSQL_UPDATE_PORT? > > > You are correct, and that probably fixes an outstanding bug report on > SourceForge. Most people use the same info for read and update, so > no one has fixed the problem before.
In the current vpopmail version with mysql support tries to reconnect to the update server for database queries if an update server was configured in the vpopmail.mysql. I have extended vpopmail to do the same with updates to the update database server. This was realy hard work ;) vpopmail.mysql is extended by a third server configuration line and also the parser in vmysql.c is. It is not a beautiful but a simple patch which works well for me. I have a fully automated setup where also updates happens to non office times. Therefor "failover" for update server queries are good for my sleep ;) Maybe you are interessed in it for an upcoming release? (Or do a better solution) Best, Hartmut > > Rick, another fix for the next release. > > -- > Tom Collins - [EMAIL PROTECTED] > Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ > QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/ > > > > > !DSPAM:4758040732004317911302!
