For some reason, I suspect because of a faulty compilation, my
FD daemons on my SLES 9 clients go to another address on a
different network.

But this seemingly faulty as well ... Any ideas?


I have edited bacula-fd.conf on the client so I am specifically
pointing to the address/name of the server:


#
# Default  Bacula File Daemon Configuration file
#
#  For Bacula release 2.2.8 (26 January 2008) -- suse 9
#
# There is not much to change here except perhaps the
# File daemon Name to
#

#
# List Directors who are permitted to contact this File daemon
#
Director {
   Name = bacula-dir
   Address = bacula.doggy.com
   Password = "ngSHFhghkjdog"
}

#
# Restricted Director, used by tray-monitor to get the
#   status of the file daemon
#
Director {
   Name = bacula-mon
   Password = "snSDFjkseg"
   Monitor = yes
}

#
# "Global" File daemon configuration specifications
#
FileDaemon {                          # this is me
   Name = bacula-fd
   FDport = 9102                  # where we listen for the director
   WorkingDirectory = /usr/bacula/var/bacula/working
   Pid Directory = /var/run/bacula
   Maximum Concurrent Jobs = 20
}

# Send all messages except skipped files back to Director
Messages {
   Name = Standard
   director = bacula-dir = all, !skipped, !restored
}

-------------------------------------------------------------------------
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