On Saturday 30 October 2010 07:03:38 Blake Dunlap wrote:
> On Fri, Oct 29, 2010 at 20:47, Dan Langille wrote:
> > On 10/29/2010 4:19 PM, Dylan Vanderhoof wrote:
> > > On 10/23/10 11:30 AM, "Dan Langille" wrote:
> > >
> > > On 10/22/2010 11:13 PM, Dylan Vanderhoof wrote:
> > >> This appears to be
On Fri, Oct 29, 2010 at 20:47, Dan Langille wrote:
> On 10/29/2010 4:19 PM, Dylan Vanderhoof wrote:
> > On 10/23/10 11:30 AM, "Dan Langille" wrote:
> >
> > On 10/22/2010 11:13 PM, Dylan Vanderhoof wrote:
> >> This appears to be a bacula-fd bug, as best I can tell. Perhaps
> somebody can shed so
On 10/29/2010 4:19 PM, Dylan Vanderhoof wrote:
> On 10/23/10 11:30 AM, "Dan Langille" wrote:
>
> On 10/22/2010 11:13 PM, Dylan Vanderhoof wrote:
>> This appears to be a bacula-fd bug, as best I can tell. Perhaps somebody
>> can shed some enlightenment as to how I might get around it?
>>
>> We ha
Sorry it took so long for me to get back on this.
I'm on 5.0.3, ipv6 support is compiled in, and the client is correctly
resolving (on an OS level) the and A record for the SD.
-D
On 10/23/10 11:30 AM, "Dan Langille" wrote:
On 10/22/2010 11:13 PM, Dylan Vanderhoof wrote:
> This appears
On 10/23/2010 6:48 AM, Michael Stapelberg wrote:
> Hi Dylan,
>
> Excerpts from Dylan Vanderhoof's message of 2010-10-23 05:13:02 +0200:
>> I can use FDAddresses in the bacula-fd.conf on the client to prevent the
>> client from listening on its IPv4 address. However, when I actually try to
>> run a
On Saturday 23 October 2010 05:13:02 Dylan Vanderhoof wrote:
> This appears to be a bacula-fd bug, as best I can tell. Perhaps somebody
> can shed some enlightenment as to how I might get around it?
>
> We have a bacula server running v4 and v6, with an A and record. All
> functional clients
On 10/22/2010 11:13 PM, Dylan Vanderhoof wrote:
> This appears to be a bacula-fd bug, as best I can tell. Perhaps somebody can
> shed some enlightenment as to how I might get around it?
>
> We have a bacula server running v4 and v6, with an A and record. All
> functional clients are IPv4 a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/23/2010 03:13 AM, Dylan Vanderhoof wrote:
> This appears to be a bacula-fd bug, as best I can tell. Perhaps somebody can
> shed some enlightenment as to how I might get around it?
>
> We have a bacula server running v4 and v6, with an A and AA
Hi Dylan,
Excerpts from Dylan Vanderhoof's message of 2010-10-23 05:13:02 +0200:
> I can use FDAddresses in the bacula-fd.conf on the client to prevent the
> client from listening on its IPv4 address. However, when I actually try to
> run a backup, the client contacts the SD by name and ignores t
This appears to be a bacula-fd bug, as best I can tell. Perhaps somebody can
shed some enlightenment as to how I might get around it?
We have a bacula server running v4 and v6, with an A and record. All
functional clients are IPv4 and are working great.
I'm trying to add a hosts that bac
10 matches
Mail list logo
