From: zitter at zitterwebdesign dot com Operating system: Vista PHP version: 5.2.6 PHP Bug Type: *General Issues Bug description: Mysql and Mysqli features selected but not installed.
Description: ------------ Simply put, I checked five features, and only three showed up on phpinfo(). http://www.zitterwebdesign.com/hosted/php5inst.gif -- Edit bug report at http://bugs.php.net/?id=46081&edit=1 -- Try a CVS snapshot (PHP 5.2): http://bugs.php.net/fix.php?id=46081&r=trysnapshot52 Try a CVS snapshot (PHP 5.3): http://bugs.php.net/fix.php?id=46081&r=trysnapshot53 Try a CVS snapshot (PHP 6.0): http://bugs.php.net/fix.php?id=46081&r=trysnapshot60 Fixed in CVS: http://bugs.php.net/fix.php?id=46dvance. > > Paul > > I personally prefer the hourly dump, because we have enough load that running 100s of relay_recipient checks a minute (peaks of thousands) would be another load on a particular LAN segment and the AD that I'd rather avoid. Better to have a minute of high load, and fast lookups on the gateway boxes the rest of the time. Also, if your accounts don't change that often, you could do a 8-hourly/16-hourly/24-hourly cron job for your AD dump, as long as it's a reasonable turn-around for your organisation. I do a load 8am in the morning, every two hours during normal business hours (because our accounts creation people require that fast a turnaround), and then a final one at 6pm. Another aspect to consider is if you use Postfix as the Exchange "bridgehead" server, as we do. It would be difficult to deliver mail to the various Exchange servers using a standard LDAP query - we use the dump process to munge the HomeMDB server attribute in AD into a useable transport maps entry. But as everyone has said, there is no one-size-fits-all.
