On Wed, Aug 12, 2015 at 8:15 AM, Heitor Faria wrote:
> I agree with Ana with the fact it is probably not a bug. Even in the
> hypothesis Bacula is sending delayed messages this is the reason there is a
> time stamp on each log message. Yes: the connection error happened. Yes:
> daemon messages ca
Hello Lukas,
I forgot to mention that you can have two copy jobs running and sending to
different pools (in this case, you would need more than one pool per
client, but this way you will have your backups replicated to two different
groups of volumes) setting the next pool in the schedule resource
My mailbox is in CDT (5 hours behind UTC). The backup host is in UTC, hence
the log entries (and mail headers, too, btw) show times in UTC.
This is why I created the logging frontend script: in order to debug
Becula's mail messaging, I want to see what *Bacula* is trying to do; I
don't want to get
On Tuesday 2015-08-11 17:40:17 Jing Yang wrote:
> Here is my init.d script file, i did not see the -u option …. BUSER and
> BGROUP are the two things some other mailing list user told me to put
> there, however, that does not work either.
Hi!
I am not sure what OS you are using so my advice here
