From: Kern S. <ke...@si...> - 2006-08-03 08:09:03
|
On Thursday 03 August 2006 03:28, Robert Nelson wrote: > Dave was the one I was working with over the weekend to get the > cross-compile environment working on FreeBSD. We were able to get bconsole > working with TLS so the only issue is the lack of files being backed up > (certainly a very large issue :-). I expect that either there is some > (unintended) incompatibility between the 1.38.11 director and the 1.39 > client or some issue with the fileset configuration. Hmm. There was an incompatibility, but it involved the ClientRunBeforeJob directive. Recently, Eric has corrected it so that the 1.39 now supports the old 1.38.11 calls. However, I think that problem completely terminated the job. > > Right now I'm out of the country visiting my folks in Canada. Once I get > back home to the US tonight, I'll take a look at it. OK, thanks. > > But the very good news coming out of this exercise is the TLS now works with > Windows machines. Yes. I'd like to get to the point that it is running here. Then the other problems can be resolved rather quickly (I hope). > > > -----Original Message----- > > From: bac...@li... > > [mailto:bac...@li...] On Behalf > > Of Kern Sibbald > > Sent: Wednesday, August 02, 2006 8:00 AM > > To: Dave > > Cc: bacula-devel > > Subject: Re: [Bacula-devel] winbacula cvs fileset issue > > > > Hello, > > > > On Tuesday 01 August 2006 19:45, Dave wrote: > > > Hello Kern, > > > I'm using winbacula compiled from cvs on an xpsp2 > > machine utilizing tls. > > > > Well, that is already quite an accomplishment. It is > > difficult to build Bacula > > on a Windows machine especially to add tls to it. > > > > > I'm getting an error on backup stating that my fileset is > > incorrect. I'm > > > using the same set as i did with 1.38.11 and am wondering > > if this is a > > > difference between the cvs and release versions of bacula. > > I don't get any > > > kind of syntax error when i verify the file. One of my file > > declarations > > > looks like: > > > > > > File = "c:/openssl" > > > > > > And here's the error msg: > > > > > > 01-Aug 12:36 satellite-fd: Could not open directory > > C:/openssl: ERR=The > > > filename, directory name, or volume label syntax is incorrect. > > > > I suspect that c:/openssl does not really exist on that > > client, or there is > > some problem with your build. This wouldn't be surprising if > > you are pulling > > code from the CVS as it has been under heavy development and > > the build > > procedures have been changing frequently. > > > > > > > > I thought i should write in case this is an issue you > > should be aware of > > > prior to release. > > > > It is something that we will carefully test. > > > > > Also, is there a list of features for cvs bacula which > > > will be 1.40? > > > > No, but the *beginning* of such a list is in ReleaseNotes in > > the current CVS. > > > > > I've heard of data encryption as it's being written to tape or > > > disk and would like to try that out! > > > > Please do so when we release our first beta version. Your > > testing would be a > > big help. > > > > > So far despite the fileset error > > > winbacula tls worked great, communications were encrypted > > with all clients, > > > the only issue with it was bconsole.exe didn't start, no > > errors were given, > > > i'm probably missing a dll. > > > > Yes, it is not easy. > > > > > Thanks a lot. > > > Dave. > > > > > > > -------------------------------------------------------------- > > ----------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the > > chance to share your > > opinions on IT & business topics through brief surveys -- and > > earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge > > &CID=DEVDEV > > _______________________________________________ > > Bacula-devel mailing list > > Bac...@li... > > https://lists.sourceforge.net/lists/listinfo/bacula-devel > > > |