On 04/04/06, Kern Sibbald <[EMAIL PROTECTED]> wrote: > On Tuesday 04 April 2006 18:30, Will McDonald wrote: > > Yeah, I did kinda jump in in the middle, I got side-tracked by > > skipping down to how to build a rescue CD for multiple hosts so I > > haven't run a configure. > > > > But again, reading this: > > > > "For users of the bacula-rescue rpm the static bacula-fd has already > > been built and placed in /etc/bacula/rescue/linux/cdrom/bin/ along > > with a symbolic link to your /etc/bacula/bacula-fd.conf file. Rpm > > users only need to do the second step:" > > > > Implies I could just start straight at: > > > > cd /etc/bacula/rescue/linux/cdrom > > su (become root) > > make all > > It seems pretty clear to me. It states two times that the instructions are for > rpm users. You apparently loaded the source.
No, I haven't. This is a purely RPM install. I grabbed the SRPM bacula-1.38.5-4.src.rpm and rebuilt it for CentOS4 (effectively RHEL4). On the main Bacula server I have... [EMAIL PROTECTED] ~]# rpm -qa | grep bacula bacula-mysql-1.38.5-4 bacula-mtx-1.38.5-4 And on all the clients I have... [EMAIL PROTECTED] ~]# rpm -qa | grep bacula bacula-client-1.38.5-4 The Bacula 1.38.5-4 SRPM doesn't include a separate bacula-rescue RPM anymore, it appears all this functionality's been rolled into the client packages. > > But this system doesn't have the static bacula-fd or a symlink to > > bacula-fd.conf. Do I need to get the Bacula source on this system and > > run through the ./configure stage? > > The directory must be configured, which is pre-done for the rescue rpm. For > rescue loaded from source, you must do the ./configure, but I think that is > quite clear from the doc. But this configuration doesn't appear to have been carried out when using the bacula-client RPM. Most of the rescue stuff's there, just not the /etc/bacula/rescue/linux/cdrom/bin/ directory, statically linked bacula-fd or the symlink. > > And I don't need the source on each client system to carry out the > > "Putting Two or More Systems on Your Rescue Disk" section of the > > instructions do I? Which says that for a client system that has Bacula > > installed via RPM all I should need to do (or at least this is how I'm > > reading it) is: > > > ssh client2 > > cd /etc/bacula/rescue/linux/cdrom > > su > > (enter root password) > > make bacula > > exit > > This is absolutely true if you loaded everything from rpms. If you load from > source, you must follow the instructions for the source. And like I said, I have, sorry if this wasn't clear from the start. I did mention it in the original post :) "All hosts are CentOS 4.2 or 4.3 and I have bacula-mysql-1.38.5-4 and bacula-mtx-1.38.5-4 installed from RPM." Though perhaps I should've more accurately said "All hosts are CentOS 4.2 or 4.3, the server has bacula-mysql-1.38.5-4 and bacula-mtx-1.38.5-4 installed from RPM and all clients have bacula-client-1.38.5-4". Will. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
