-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Matt Brookings wrote: > aledr wrote: >> Wasn't --enable-sql-logging replaced by --enable-auth-logging >> configurable in backends? > > No. I think you're thinking of --enable-mysql-logging and > --enable-pgsql-logging. > These were replaced with a single configure option, --enable-sql-logging. > > SQL logging creates a vlog table that logs authentication, and auth > logging updates the lastauth file for users. If you have SQL logging > enabled, it makes sense to disable auth logging. > > It looks like --enable-sql-logging was another soldier that went missing > during the move to authentication modules. I'll pop it back in. > >> And also can't find --disable-mysql-limits on backends/mysql/configure >> or backends/mysql/configure.ac > > Another missing configuration flag. Thanks for finding all these. > I'll have it back in the configure script in trunk shortly.
Changes just submitted to the trunk: - Re-added some missing configure flags for the MySQL and PostgreSQL modules - Renamed module occurrences of 'valias' to 'native valias' - Fixed a missing variable in PostgreSQL module with SQL logging enabled - -- /* Matt Brookings <m...@inter7.com> GnuPG Key FAE0672C Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqYJ3kACgkQIwet2/rgZyyUoQCfUsRzoaBhZQDv62S8AKFy8HTG o8sAmgK+Bp9I0abI6+GFvyYXv+7ZCylx =03JR -----END PGP SIGNATURE-----