First off, thanks for the automysqlbackup script. It is very useful.
Anyway, I just upgraded to version 3.0 rc6 and had a question. I've set the the conf file option "CONFIG_mailcontent='quiet'", but now I get e-mailed by cron when the script runs:
# Checking for permissions to write to folders:
base folder /backups … exists … ok.
backup folder /backups/<configfile> … exists … writable? yes. Proceeding.
Could there be an edit to make the "quiet" option really quiet? Shouldn't this information follow the mailcontent option (if log is set, include it in the log e-mail, if stdout is set send it to stdout, if quiet is set, don't print it because it's not an error)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well what should I do until the config file is read, therefore the option quiet set and I can establish the output redirections to logfiles, for which I need to make sure, that the directories are there?
Just run the command with &>/dev/null to get rid of all output. If there is something wrong you'll still get emails … i guess.
Is this a satisfying solution for you?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I haven't looked at the code but I assumed that the first line "Parsed config file" would be printed after the config files were read, not before. I was also confused that it did't report parsing the log file being passed by the command line argument.
I'm currently using the redirect work around, thanks for pointing that out, though. Even if I did have the CONFIG_mailcontent set to "log" or "files" I wouldn't want two e-mails, one from cron and one from automysqlbackup itself. I had been using version 2.5 and it didn't send anything to an output that cron would catch.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A real quiet option is for sysadmin who used symbolic link to automysqlbackup script in /etc/cron.daily and don't want to maintain a script where the only task is to redirect output to /dev/null .. it's realy usefull.
Regards,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey everyone,
First off, thanks for the automysqlbackup script. It is very useful.
Anyway, I just upgraded to version 3.0 rc6 and had a question. I've set the the conf file option "CONFIG_mailcontent='quiet'", but now I get e-mailed by cron when the script runs:
Parsed config file "/etc/automysqlbackup/automysqlbackup.conf"
# Checking for permissions to write to folders:
base folder /backups … exists … ok.
backup folder /backups/<configfile> … exists … writable? yes. Proceeding.
Could there be an edit to make the "quiet" option really quiet? Shouldn't this information follow the mailcontent option (if log is set, include it in the log e-mail, if stdout is set send it to stdout, if quiet is set, don't print it because it's not an error)?
Well what should I do until the config file is read, therefore the option quiet set and I can establish the output redirections to logfiles, for which I need to make sure, that the directories are there?
Just run the command with &>/dev/null to get rid of all output. If there is something wrong you'll still get emails … i guess.
Is this a satisfying solution for you?
I haven't looked at the code but I assumed that the first line "Parsed config file" would be printed after the config files were read, not before. I was also confused that it did't report parsing the log file being passed by the command line argument.
I'm currently using the redirect work around, thanks for pointing that out, though. Even if I did have the CONFIG_mailcontent set to "log" or "files" I wouldn't want two e-mails, one from cron and one from automysqlbackup itself. I had been using version 2.5 and it didn't send anything to an output that cron would catch.
Hi, this is my command.
root@ptLWL01:/etc/cron.daily# cat runautomysqlbackup #!/bin/sh /usr/local/bin/automysqlbackup /etc/automysqlbackup/myserver.conf #chown root.root /home/backup/db* -R #find /home/backup/db* -type f -exec chmod 400 {} \; #find /home/backup/db* -type d -exec chmod 700 {} \; root@ptLWL01:~#Where I have to put &>/dev/null ?
Michael
You would want it on the line that runs automysqlbackup, so:
In my case I haven't seen the need for the ampersand, so my command line is:
Hi,
A real quiet option is for sysadmin who used symbolic link to automysqlbackup script in /etc/cron.daily and don't want to maintain a script where the only task is to redirect output to /dev/null .. it's realy usefull.
Regards,