-
comment out the last few lines of the script
eval rm -f "$LOGFILE"
eval rm -f "$LOGERR"
and set MAILCONTENT="quiet"
you'll still get the log if there are errors, otherwise the log file is saved on disk.
2009-09-03 13:13:36 UTC in AutoMySQLBackup
-
Why not just use the PREBACKUP and POSTBACKUP which are already there?
PREBACKUP="cp /etc/my.cnf $BACKUPDIR ; mysqldump --version ; mysql -e \"show slave status\G\" ; mysqladmin stop-slave flush-tables flush-logs flush-status"
POSTBACKUP="mysqladmin start-slave".
2007-10-12 12:50:36 UTC in AutoMySQLBackup
-
check your line endings.
2007-09-17 17:37:56 UTC in AutoMySQLBackup
-
That sounds like it is on a PC. Can't help you there.
2007-08-19 22:50:45 UTC in AutoMySQLBackup
-
certainly.
In the script you change BACKUPDIR to point to a directory on the MyBook
BACKUPDIR="/mybook/somedir/DB-backups"
assuming that you named the backup script mbackup.sh the following cron entry will run backups at 2:15 every morning
15 2 * * * /u/me/mbackup.sh.
2007-08-19 13:03:19 UTC in AutoMySQLBackup
-
private is now a reserved word in PHP5.
change all of the define("PRIVATE", whatever) to define("NJPRIVATE", whatever). Change test in lib/inc-common.php of PRIVATE == true to NJPRIVATE == true.
Change play.php call to "header()" to 2 calls to header(), one for each of the headers being sent.
Bingo - PHP5 and it works.
2006-12-03 20:56:57 UTC in Netjuke
-
It is 2-Jan-2005, the week number is currently 53
Weekly backups should probably be saved using the week number and the year that the week belongs to (use %G in date)
What I see for my weekly backup taken on Saturday is a name like 'week.53.2005-01-01.sql.bz2' which looks odd.
Something like 'week.53.2004.sql.bz2' would make a lot more sense, and be correct.
Of course if one runs...
2005-01-02 09:47:59 UTC in AutoMySQLBackup
