Jon Schewe wrote:
>
> A little more information. I'm able to get the client status now, 
> however once I add the "TLS Enable" line to the FileDaemon resource on 
> the windows client I am no longer able to start the windows service. I 
> get the generic "service quit unexpectedly" error. The event viewer only 
> shows that the bacula service died.
>
> Any ideas?
>
>   
I figured it out, I missed escaping a slash in a path name. Once I found 
that I could run bacula-fd.exe with -t and redirect to a file I was able 
to start debuging, but printing the line number in the file would really 
help. The error reporting under windows really needs work.

-- 
Jon Schewe | http://mtu.net/~jpschewe
If you see an attachment named signature.asc, this is my digital signature.
See http://www.gnupg.org for more information.

For I am convinced that neither death nor life, neither angels nor demons,
neither the present nor the future, nor any powers, neither height nor
depth, nor anything else in all creation, will be able to separate us from
the love of God that is in Christ Jesus our Lord. - Romans 8:38-39


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users