>>
>> Well, now i feel stupid.
>> The moment i read that, i thought about all relevant names being
>> resolved correct, but then i realised that the client might get the
>> sd's fqdn to connect to, which would resolv to the "wrong" ip.
>> Adding the sd's fqdn to /etc/hosts (which i first didn't, because i
>> already added the names of all "relevant" interfaces), i tried a small
>> backup set and it worked like a charm.
>>
>> Thanks for the quick response!

>I forgot to mention, that i don't think this is the perfect solution.
>This works, but i have to tweak the clients resolver to get bacula to
>use the right ip. Since the server has multiple interfaces and
>multiple names for these interfaces, i would prefer to configure the
>name/ip i want to use inside bacula instead of relying on the fqdn.

I feel the same way, but it's the only option we have at the moment as Bacula 
operates only on distinguished name. You can try submitting a feature request 
to fix this however, the documentation on how to do so is on the website.

>Kind regards

>Ariano Bertacca
>Systemmanagement

-Blake

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users