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/mysq
variable basedir else change a param. in what you have as file, stop start and
see.
Mathias
Selon Ed Kasky <[EMAIL PROTECTED]>:
> 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 /v
resubmitted
Selon [EMAIL PROTECTED]:
> variable basedir else change a param. in what you have as file, stop start
> and
> see.
>
> Mathias
>
> Selon Ed Kasky <[EMAIL PROTECTED]>:
>
> > I added the line to the configuration file and removed "--log-error=" line
> > from startup line but it still cr
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
Hello.
Unfortunately I could give suggestion only about your second question.
Is it possible that /var/log/mysql/error.log created by mysqld_safe
(you're specifying it with --log-error command line option) and
/usr/local/mysql/var/yuda2.err is created by mysqld process if it
founds problems
Hello there -
I have a couple of questions regarding a new install of MySql 4.1.12 on RH
7.2. Being new to this list, I sure do hope this hasn't been covered
before. I have scrubbed Google and searched the archives for this list but
can't find an explanation or a solution to 2 issues:
1.
