Ah! Thanks - I see. 5.1.39 Actually I did look i the manual, but failed to note the differences between < 5.1.29 and > 5.1.29 I was using the syntax for < 5.1.29.
Now I am using the correct syntax in /etc/my.cnf $ grep general /etc/my.cnf general_log=1 general_log_file=/var/log/mysql/mysql.log Now I get a log file, but no actual sql commands appear within. $ tail -f mysql.log /usr/sbin/mysqld, Version: 5.1.39-community-log (MySQL Community Server (GPL)). started with: Tcp port: 3306 Unix socket: /var/lib/mysql/mysql.sock Time Id Command Argument Cant see anything relevant in the manual. Strange(?) Syd ++++++++++++++++++ Sorry can't remember what version you said you were using; if you have a version prior to 5.1.29 to log all queries enter the following in the [mysqld] section of your my.cnf log = /path/to/logfile/filename.log Remembering that the path you specify must be writeable by the server. If you are on version 5.1.29 or later use general_log=1 general_log_file=/path/to/logfile/filename.log If you have a very busy server the general query log will get very very big very quickly. Its best to only enable the general query log for identifying problems and performance tuning. Take a look at the manual(http://dev.mysql.com/doc/refman/5.1/en/)! You can get answers to questions like this so much quicker from there. Regards John Daisley On Fri, 2009-11-13 at 16:43 +0000, Sydney Puente wrote: > OK thanks to some help from this list I now have a blank my.cnf file in /etc > And I want to set up logging of all sql queries. > > So I have tried: > > SET GLOBAL general_log = 'ON'; > > and/or putting (only) /var/log/mysql/mysql.log > in my.cnf and doing a restart via /etc/init.d > (have a pid file now -Ta!) > > but still no sql commands in the log file. > > There are stop/start up commands in /var/log/mysqld.log > > but that is about it > > Any suggestions? > > Syd -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
