Re: [BackupPC-users] Error log for pre or post command errors?

[Dustin P. <du...@pu...>]

Yes, one of our guys noted the 3.x support for errors the other day. As
far as XferLOG in 2.x, obviously, that's not enough if you have critical
jobs running in a -pre command (e.g., mysqldump).

We went ahead and created templates for scripts that run -pre and -post
commands that will ensure an admin is notified of any errors. We'd be
happy to submit them regardless.

--
Puryear Information Technology, LLC
Baton Rouge, LA * 225-706-8414
http://www.puryear-it.com

Author, "Best Practices for Managing Linux and UNIX Servers"
  http://www.puryear-it.com/pubs/linux-unix-best-practices

Identity Management, LDAP, and Linux Integration


Craig Barratt wrote:
> Dustin writes:
> 
>> We noticed that BackupPC never reports any issues with a -pre or -post
>> command. This is odd. If a -pre command fails, then it is very likely
>> that the backup will be moot (e.g., if you don't dump a MySQL database).
>>
>> Are there any plans to enable reporting for errors in -pre or -post
>> commands?
> 
> Any output is written to the XferLOG file.
> 
> The exit status is ignored in 2.x, while in 3.x it can be used
> to abort the backup by setting $Conf{UserCmdCheckStatus}.
> 
> Craig