620.7 MB)
Other (smaller) jobs from the same client work. This job used to work.
All parties are running 1.38.11 on Debian.
The router (running dd-wrt) has a TCP timeout of 3600 seconds, but with
the heartbeat, that shouldn't matter, and in any case doesn't match the
observed times.
Any
Bacula version 1.36.2, on Debian sarge.
I have some (bacula) clients that are external to the LAN that hosts
the rest of the system. I created an extra "Storage" resource with the
appropriate external host address, and use that one in the Jobs that run
on the external clients. Works fine.
For res
On Fri, Oct 21, 2005 at 07:04:57PM +0300, Viktorija wrote:
>
> But for now i am searching how to avoid situations with stolen passwords.
Don't allow your passwords to be stolen. You haven't explained how
someone can read a properly protected bacula-fd.conf but NOT arbitrary
other files on the sy
On Fri, Oct 21, 2005 at 05:42:18PM +0300, Viktorija wrote:
> i have some questions about authorization from client (bacula-fd) to
> server (bacula-dir). How about security? Maybe somebody can describe
> very detailed authorization process client-server-client to me? What
> if i have stolen bacula-
(No need to CC me, I'm on the list)
On Thu, Oct 20, 2005 at 10:31:04PM +0100, Martin Simmons wrote:
> A common reason for this problem is that the padding bytes at the end of the
> sockaddr_in object (called something like sin_zero) are not actually zero.
> Typically this happens when the code fai
So I battled my way through AIX configure/build process[1] and got
bacula-fd built.
However, the FD won't bind a specified address. It gets stuck in the
bind() loop in bnet_server.c with EADDRNOTAVAIL, claiming that the
address is not available.
Now, I'm pretty sure that 127.0.0.1 is available,
