Hi i didn\'t get the exact problem. I have gone through eap.conf. Pls make little bit clear abt the problem Anoop freeradius-users-request@lists.freeradius.org:
Send Freeradius-Users mailing list submissions to freeradius-users@lists.freeradius.org
To subscribe or unsubscribe via the World Wide Web, visit http://lists.freeradius.org/mailman/listinfo/freeradius-users or, via email, send a message with subject or body \'help\' to freeradius-users-request@lists.freeradius.org
You can reach the person managing the list at freeradius-users-owner@lists.freeradius.org
When replying, please edit your Subject line so it is more specific than \"Re: Contents of Freeradius-Users digest...\"
Today\'s Topics:
1. Re: MySQL and postauth_query (George Embrey) 2. Re: FreeRadius crash (A.L.M.Buxey@lboro.ac.uk) 3. Re: MySQL and postauth_query (Peter Nixon) 4. Re: rlm_sqlippool in freeradius 1.1.6 (Peter Nixon) 5. Re: IP billing with freeradius (satish patel) 6. Re: IP billing with freeradius (Peter Nixon) 7. Re: eap-tls authentication with free radius 1.1.5 (Alan DeKok)
----------------------------------------------------------------------
Message: 1 Date: Tue, 08 May 2007 14:38:39 +1000 From: George Embrey <george@vmail.net.au> Subject: Re: MySQL and postauth_query To: FreeRadius users mailing list <freeradius-users@lists.freeradius.org> Message-ID: <463FFECF.7080101@vmail.net.au> Content-Type: text/plain; charset=\"us-ascii\"
Hugh Messenger wrote:
George Embrey <george@vmail.net.au> says:
Queries to Windows MySQL servers from Linux Systems often fail unless the lower_case_table_names parameter is set to 0 in the my.ini file in the MySQL directory.
I\'m familiar with that issue, and I checked all the table case-ness. The problem seems to be with providing an empty string (\'\') as the value for an auto-incrementing integer primary index.
Yes that is true \'\' or empty strings are not nulls or integers... I suggest replacing the \'\' with the word null, this will sort out the issue based on the query you specified.
The problem with setting lower_case_table_names to 0 is that I could end up blowing away my MyISAM tables elsewhere in that server, as per the warning the service control gives, if I moof a query on those and use the \"wrong\" case:
I would rename the MyISAM tables using phpmyadmin or using SQL and sort out the Database to run case sensitive in the first place like the ANSI standard.
Or much better still mysqldump the entire MySQL server into a file \"textfilename.sql\", sort out the table names etc... using a good text editor, place a drop table if exists before each create table entry, save the file then run mysql -uroot -p < \"textfilename.sql\" to recreate all of the databases including data with tablenames in the correct case...
Maybe I am just too fussy...
\"You have forced lower_case_table_names to 0 through a command-line option, even though your file system \'E:MySQLData\' is case insensitive. This means that you can corrupt a MyISAM table by accessing it with different cases. You should consider changing lower_case_table_names to 1 or 2\"
Only if you live in an all windows world... \"Compatability is a bitch it demands the use of standards, the little things which M$ don\'t adhere to very well\" ;-)
It\'s working fine with my modifie query, so I\'m just going to put this down to \"a 5.x thing\" and live with my change. Compared to the wholesale hack and slash job I\'ve had to do on the sqlippool queries to get them to work, it\'s no Big Whoop, LOL!
But thanks for the suggestion, I appreciate your time.
-- hugh
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
George Embrey CEO / Senior Systems Architect. Vmail Internet Services Pty Ltd. 318 Shoal Point Road Shoal Point QLD 4750 Australia