We've been using MySQLD for a few years now quite happily. It's amazing
how well it performs. However, I have a minor issue, and I'm not sure how
to deal with it. I've scoured the manual, searched list archives, the
web, etc., and am coming up empty.
Somehow, the server is recording the Binary log in the data directory.
Each of these log files takes up a gigabyte. This would be all well and
good if we were using the server in as a master in a replication setup,
but we are not. It WAS formerly acting as a master in a replication
environment, but we've long since made it the only SQL server on our
network. We've removed (commented) all the lines in my.cnf that deal with
replication, and the log-bin is one of these lines. To clarify: the
log-bin line in the my.cnf file IS commented with a hash-mark (#). The
server has been restarted since this change, and "SHOW MASTER STATUS"
returns an empty set of data (only showing the field names.)
the SQL command RESET MASTER does nothing. It does not delete the
hostname-bin.### files.
the mysqld commandline parameters follow:
/usr/sbin/mysqld --basedir=/ --datadir=/var/lib/mysql --user=mysql
--pid-file=/var/lib/mysql/inferno.pid --skip-locking
We're running version 3.23.41 for pc-linux-gnu on i686, running on SuSE
Linux 7.1, kernel 2.4.18 #2 SMP on a Dual-Processor Pentium II 450MHz
server
So, if any of you can shed some light as to why it would be saving the
binary log against our will, or as to how to stop it, it would be greatly
appreciated.
Brian
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/my***********...ie.nctu.edu.tw
