Flush logs, binary log index file
I'm trying to write a script to weekly remove MySQL logs, the general, error and binary log files. Following the MySQL documentation, I've written a script that moves all current log files, then executes mysqladmin flush-logs. My question is this on the binary logs (bin.001, bin.002, etc.): once these are removed and flush logs is executed, the binary log files start over with bin.001. HOWEVER, the binary index file does not appear affected by the flush-logs command; ie, if I'm up to bin.003 in the binary.index file, remove the files and execute the flush logs command, I'm back to a file names bin.001, although the binary.index file still has entries for bin.001, bin.002, bin.003, etc. How does the binary index file stay current when you remove the logs?? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Check table script
Hey, having trouble running mysqlcheck from a script. Running 4.0.13 on Linux. I can run the following command: /usr/local/mysql/bin/mysqlcheck -u root -p -A -a -m -v --auto-repair /var/log/mysql/check_tables.log from the command line, plug in the password at the prompt, and everything works. When I put this exact command into an executable file, and add the '=[pswd]' argument, I get an access denied error message: /usr/local/mysql/bin/mysqlcheck: Got error: 1045: Access denied for user: '[EMAIL PROTECTED]' (Using password: YES) when trying to connect p.s. I've used this exact method on mysqldump, and it works. Any suggestions? Anyone have a mysqlcheck script that they run via cron? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
mysql_history file?
We're just getting started with MySQL on Linux; I was browsing my home directory and found a file called .mysql_history. It contains a history of all mysql commands I've entered - including logging on, setting passwords for users, etc. Sure enough, other users of mysql have the same file. Questions: What are these files, are they mandatory, or can I turn off this logging? Do we need to keep an eye on growth of this files, and truncate or archive them? Most importantly - yikes, seems scary to have a clear text file with a record of Mysql username and password create commands. Any thoughts on this?? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Backup conventions
Hi, I'm a new user of MySQL on Linux. I have been an Oracle DBA; and know that anyone familiar with Oracle takes backup procedures very seriously Anyone have recommendations for nightly backup procedures for MySQL (transactional) databases? The literature seems a little ambiguous on this. I did 'turn on' the general, binary and error logs. Does anyone shut down the MySQL daemon regularly? Anyone use mysqldump, or do folks simply use a file system backup? We have tons of databases and tons of tables, so I'm not really considering the lock/flush procedure on tables... Any suggestions? -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
