Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-19 Thread Dimitri Maziuk
On 03/19/2015 11:54 AM, Peter Wood wrote: > Thank you for the reply. > > Yes, I've done all the debug steps I can think of. > > Permissions is a good point though. The file permissions are 600 root:root. > Only root can remove the file. > > Bacula-fd process runs as root so I'm expecting it will

Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-19 Thread Peter Wood
Thank you for the reply. Yes, I've done all the debug steps I can think of. Permissions is a good point though. The file permissions are 600 root:root. Only root can remove the file. Bacula-fd process runs as root so I'm expecting it will be able to remove the file, right? SELinux is disabled.

Re: [Bacula-users] Bacula 5.2.13 ClientRunAfterJob

2015-03-19 Thread Ana Emília M . Arruda
Hi Peter, Have you checked if the job falis or not? The Client Run After Jog do not runs if the job falis. You can use the bellow if you want that the script runs despite of the job falis or not: Run Script { RunsWhen = After RunsOnFailure = yes Commnad = "/bin/rm -f /backup/daily/mysql-Sl