summaryrefslogtreecommitdiff
path: root/files
diff options
context:
space:
mode:
authormh <mh@immerda.ch>2009-11-19 02:34:21 +0100
committermh <mh@immerda.ch>2009-11-19 02:36:13 +0100
commit911dbc4426a7a42dbc6fc48ab61958fa6c6e1234 (patch)
tree9135c88d6c2a7272ba04a9fd0e1ec4ba55b31780 /files
parenta818f61a078b4f4367d11173049993c5c54ee067 (diff)
be nicer during mysql backup
sometimes it can happen that by locking all tables we run into error 24, which means to many open files. According to http://rackerhacker.com/2007/08/19/mysql-errcode-24-when-using-lock-tables/ we can use single-transaction to be nicer during backups.
Diffstat (limited to 'files')
-rw-r--r--files/backup/mysql_backup.cron2
1 files changed, 1 insertions, 1 deletions
diff --git a/files/backup/mysql_backup.cron b/files/backup/mysql_backup.cron
index 705a854..1cb21ff 100644
--- a/files/backup/mysql_backup.cron
+++ b/files/backup/mysql_backup.cron
@@ -1 +1 @@
-00 01 * * * root /usr/bin/mysqldump --default-character-set=utf8 --all-databases --all --flush-logs --lock-all-tables | gzip > /var/lib/mysql/data/mysqldump.sql.gz && chmod 600 /var/lib/mysql/data/mysqldump.sql.gz
+00 01 * * * root /usr/bin/mysqldump --default-character-set=utf8 --all-databases --all --flush-logs --lock-tables --single-transaction | gzip > /var/lib/mysql/data/mysqldump.sql.gz && chmod 600 /var/lib/mysql/data/mysqldump.sql.gz