On Thursday 01 November 2007 22:22:40 Dane Miller wrote:
> Eric Bollengier wrote:
> > IHMO, i think that the script doesn't close stderr, stdout and stdin
> > properly.
>
> Hey you're right!  stderr is the culprit here.  The following Client Run
> After Job script works around the problem:
>
> #!/bin/sh
> # AfterScript.sh
> /usr/local/etc/rc.d/mysql-server start 2> /dev/null
>
> It might be an issue with mysql's launcher script mysqld_safe. I'll look
> into it a bit more.
>
> But why does this cause bacula-fd to hang?

You have the same behaviour in every programs that run commands...
(I have this in ssh sessions for example)

Bacula is reading stdout/stderr to get output commands, and if they are
not closed properly (at the end of the script for example), bacula will wait
forever.

Bye

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to