On Wednesday 01 March 2006 15:23, Michel Meyers wrote: > Arunav Mandal wrote: > > On Tuesday 28 February 2006 17:19, Arno Lehmann wrote: > >> Hello, > >> > >> On 2/28/2006 2:14 PM, Arunav Mandal wrote: > >>> We are running Bacula 1.36.3 in both director and storage daemon and on > >>> clients as well. We are now planning to upgrade the director and > >>> storage daemon do I have to upgrade the client as well or just the > >>> director and storage daemon will work? > >> > >> No, you'll have to upgrade all machines involved. > >> > >>> Is there any easy way to upgrade a lot of client > >>> machines at the same time? > >> > >> None that I know of. The simple solution might be to prepare packages > >> tailored to your needs and install them as you do in your organization. > >> The windows package is, as far as I know, created using an open source > >> installation program, so t shold be possible to adapt it to your needs > >> (paths mainly, I think). > > The Windows package uses the Nullsoft Scriptable Install System > (http://nsis.sf.net) and I think I'm the original author of the install > script.
Yes, the script we are using winbacula.nsi.in was adapted from the one you originally created. Thanks. :-) > I initially integrated some 'silent-install' functionality into > my version and unless that got removed when it went into the main > project, it should still be there (at least with winbacula-1.38.4.exe I > can still use it). > > Example: winbacula-1.38.4.exe /S /service > It only works if you use the default path of c:\bacula though. > > See http://tcnnet.dyndns.org/winbacula/ for some documentation on the > installer. You can also find the original script there (The newer > versions are in CVS at > http://cvs.sourceforge.net/viewcvs.py/bacula/bacula/src/win32/ . Look > for .nsi and .nsh files.) > > >> Creating .rpms or .debs for linux should also be possible, but that's > >> nothing I know much about. > > > > What about the client name and password in the bacula-fd.conf as if I > > make a generic package I have to manually change it. > > Just don't overwrite it. I don't think there was a change there and the > normal behaviour of the installer leaves bacula-fd.conf alone as well > (if it detects presence of the .conf file, it writes out the default > ones with extension .conf.new). > > If you search the ML archives, you should also find a script that I > wrote that uses Samba-TNG and Windows' RPC Service to remotely stop the > FD, push the upgrades and then restart the FD afterwards. I still use > that method to maintain Bacula on the 6 machines that I have. > > I don't have any particular advice for Unix/Linux systems but those are > easily scriptable anyway. > > Hope that helps. > > Greetings, > Michel > > > ------------------------------------------------------- > 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&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users ------------------------------------------------------- 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&kid=110944&bid=241720&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
