Hello.
Leave --log-error option for mysqld_safe. As far as I understand it uses it for it's own log file (different from which mysqld uses). Utilities like strace could help you to find which process creates certain file. MySQL supports debugging as well. See: http://dev.mysql.com/doc/mysql/en/debugging-server.html Ed Kasky <[EMAIL PROTECTED]> wrote: > I added the line to the configuration file and removed "--log-error=" line > from startup line but it still creates the /usr/local/mysql/var/yoda2.err > as well as /var/log/mysql/error.log > > I am assuming it is reading from my.cnf as I get the following when I run > "mysqladmin variables" > log_error | /var/log/mysql/error.log > > I also checked for possible duplicate my.cnf files but there is only one. > > Is there another way to check to be sure it's reading the configuration file? > > At 12:40 PM Sunday, 6/5/2005, Gleb Paharenko wrote -=> -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
