} this is prepared for an (not installed) director on client. so i defined a second Message-resource, but how can i tell the fd to use the right one ? i disabled the original Message
and i added (as i found in www) 'append = "/var/log/bacula/bacula.log" = all, .. '
2) logging: i tried -d100 in dir, sd and fd service scripts. but messages on console.
why is logging into /var/log/bacula/bacula.log so poor.
when a job with default-timeout writes to log when it gives up, not as soon as the errors occur ?
3) on server in dir- and sd-config a password is given.
when a job starts the director connects to sd and fd
dir <-authentication-> sd
dir -> fd -> sd
what actually goes on here ?
is there no authentication between fd and sd or does the dir tells the fd how to authenticate against the sd ? or does the dir tells the sd what connection to expect within the next minutes ? ( there is an sd-option (similiar) time_to_wait_for_client )
why the connection fd > sd can fail and how can i find out what goes wrong ?