Hello Konstantin,

On 9/29/25 11:04, Konstantin Kharlamov wrote:
Hello, I'm writing a GUI around Bacula (yeah, another one), and my
problem is I want to receive every job status change, e.g. if it's
running, failed, etc, to display to user interactively.

After digging far and wide, I figured the only way to do this is by
changing `bacula-dir.conf` to have:

     Messages {
       Name = Daemon
       append = "/tmp/dir-messages-named-pipe" = all, events, debug
     }

Per my understanding, this should send everything to
/tmp/dir-messages-named-pipe. I know for a fact job status changes are
part of the logs, because if you launch `bconsole` (assuming you have
`console = all` option) and execute `messages`, you see job status
changes info.

I'm not sure what you mean by job status, the messages command will
display job messages, not job status change. (Running to Waiting, or Cancel,
...).
Yet somehow, even though it works for console, I never see that info
among messages coming to /tmp/dir-messages-named-pipe!

I'm not sure that the Daemon message resource is configured to get your
Job messages, double check that. After, each message is sent via STDIO
and might take time to end up written in your socket. Perhaps the syslog
destination would be more appropriate, and syslog is very flexible for
that.

Hope it helps!
Best Regards,
Eric


_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to