Davide Bolcioni wrote:
further investigation about the following
Job { Name = "First backup" Schedule = "MonthlyCycle" RunBefore = "/script/stop/first" RunAfter = "/script/start/first" FileSet = first ... }
shows that after the job completed, which I infer is the RunAfter case (no such problem appears for RunBefore, although the script is actually the same with a "start" or "stop" argument) the script gets executed and I have:
bacula-dir(1616)---bacula-dir(1620)-+-bacula-dir(1621) |-bacula-dir(1622) |-bacula-dir(29152)---first(29385) `-bacula-dir(4018)
with:
# ps l 29152 F UID PID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 1 0 29152 15 0 28264 2124 pipe_w S ? 0:00 /usr/sbin/bacula-dir
# ps l 29385 F UID PID PRI NI VSZ RSS WCHAN STAT TTY TIME COMMAND 4 0 29385 15 0 0 0 > Z ? 0:00 [highway <defunct>]
i.e. bacula-dir is sitting on pipe_w but pid 29385 is defunct (zombie). The scripts run with >/dev/null 2>&1 </dev/null.
Just in case: bacula-dir [1616] is running with LD_ASSUME_KERNEL=2.4.19 and so do all children.
Back on my own post ... got it working by using
ClientRunAfterJob = "sh -c \"/etc/init.d/highway start >/dev/null 2>&1 </dev/null\""
which suggests that the problem might have been with I/O redirections.
Thank you for your consideration, Davide Bolcioni -- There is no place like /home.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
