Re: [qmailadmin] Major bug in qmailadmin when using MySQL replication.

2002-10-22 Thread Matt Simerson
Apologies, I meant to click SAVE instead of send as I left work yesterday. Anyway, appended to this email is The Rest of The Story. On Monday, October 21, 2002, at 06:24 PM, Matt Simerson wrote: OK, this will be fun to explain. I have a large vpopmail install that I'm running this on so the

Re: [qmailadmin] Major bug in qmailadmin when using MySQL replication.

2002-10-22 Thread Bill Shupp
On Tuesday, October 22, 2002, at 07:49 AM, Matt Simerson wrote: Apologies, I meant to click SAVE instead of send as I left work yesterday. Anyway, appended to this email is The Rest of The Story. On Monday, October 21, 2002, at 06:24 PM, Matt Simerson wrote: OK, this will be fun to explain.

Re: [qmailadmin] Major bug in qmailadmin when using MySQL replication.

2002-10-22 Thread Tom Collins
On Tuesday, October 22, 2002, at 07:49 AM, Matt Simerson wrote: If you read through user.c, you'll find a subroutine modusergo. In there, is the guts of what happens when you click on modify user and then submit. Reading through that, it appears that if we get a new password, we make a call

Re: [qmailadmin] Major bug in qmailadmin when using MySQL replication.

2002-10-22 Thread Bill Shupp
Sorry, didn't mean to take this off-list... On Tuesday, October 22, 2002, at 09:08 AM, Matt Simerson wrote: On Tuesday, October 22, 2002, at 11:27 AM, Bill Shupp wrote: After only getting the first half of the story yesterday, I duplicated your process to see if I could figure it out. The

Re: [qmailadmin] Major bug in qmailadmin when using MySQL replication.

2002-10-22 Thread Bill Shupp
On Tuesday, October 22, 2002, at 09:30 AM, Bill Shupp wrote: I think that having qmailadmin always read from the master is the best solution. Unfortunately, it would require updating the vpopmail API to add an argument specifying whether to use a read server or not. Unless someone knows a