> You should be able to spot it your logs.  Look for "=failed" in your
> policyd logs.  Look at the next one or two policyd logs and see if they
> make sense.  The easiest thing to spot is when you get "greylist=failed"
> followed by "whitelist=update" and the whitelisted host isn't in your
> whitelist.
> 
> What version of MySQL are you using?

Might be a good idea to identify exactly which versions of MySQL are
affected, as far as I can determine this is a MySQL issue and not a
Policyd issue. ie. Doing a query and aborting it or having it timeout
should also nuke the results for that query, not return them in a
subsequent query. No harm in adding a work-around though.

Let me know how it goes, test for a few days an I'll commit the
workaround.

-N

Attachment: signature.asc
Description: This is a digitally signed message part

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
policyd-users mailing list
policyd-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/policyd-users

Reply via email to