I use SA 2.55 with MySQL per-user settings (-x -q). I believe the SQL interface is more or less still experimental, right? Because what I would like to see is a persistent MySQL connection, instead of having to open and close a new connection for each forked process.
Forking, of course, makes it a necessity that the persistent MySQL connection be established by the parent (typically with "$dbh" as Object Constructor), so it can be passed along to its children. I'm not entirely sure whether the one Object Constructor is re-entrant (that is, whether multiple children could use it concurrently; my gut tells me: no). But since all we do is get user-prefs, a simple locking mechanism could solve that. Thinking out-loud for a moment, going it a bit fancier: spamd could keep a cache of, say, 20 persistent connections, and give any of the "free" ones to its children upon forking. So, has anyone any experience with this? If people are interested, I'm sure I could write a special module for this. - Mark ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
