From: Kern S. <ke...@si...> - 2003-01-14 20:15:13
|
On Tue, 2003-01-14 at 19:26, Phil Stracchino wrote: > On Tue, Jan 14, 2003 at 08:09:42AM +0100, Kern Sibbald wrote: > > Phil, > > > > The "trick" is to ensure that the Director's name is correct > > in the Windows bacula-fd.conf as well as that the > > password for that Director matches the one on the > > appropriate Client resource in the Director's conf file. > > > Uhhh.... I'm not 100% certain I follow you. Let me make sure: > > The director.conf contains multiple Client resources, each of which > contains a password the Director uses to speak to that client's fd. > That password, and the password in the client's fd.conf, must match, as > that password is not the password the fd uses to talk to the director, > but the password the director talks to the fd. Yes. In addition, a single FD can have multiple passwords, one for each Director, so you need to make sure that the Director's names match as well as their individual passwords. > So a single password is > essentially "shared" between the director and a client fd. Yes. > The > passwords used between the director and the various fds not only need > not be the same from client to client, but probably should not. Yes. > The > password in the bacula-dir.conf Director resource is actually only used > by the colsole, and should be shared with console.conf but probably no > other. Yes > > Is my understanding of the password interrelationships now correct? > Yes Good going. It is logical but a bit complicated, which is why I fill in the passwords for you. BTW there is no need to remember the passwords as the program always gets them from the conf file. You just need to protect the conf files. |