On Wednesday 15 April 2009 13:30:32 James Harper wrote: > > > > is what I'll do for now :) > > > > > > I think I've found the reason why... at the end of bacula-fd's main, > > > check_resources is called, and the message resource encountered > > resets > > > > the streams and tracing flag. > > > > Well, I don't quite understand the above. Does this mean that you > > have > > > resolved the problem? or are you asking me to fix something? > > I've worked around the problem, but it appears to be a bug - passing the > '-d nnn' option on the command line doesn't achieve the desired result. > I'll look into what the proper fix might be (my workaround certainly is > not that :) >
Well, Windows doesn't handle the debug output (stdout) the same way as Unix. Generally it is better to dynamically turn on debugging with the setdebug flag, but you must also turn on trace so that it outputs to a file rather than to the bit bucket -- unless you run under cygwin, which I don't really recommend. Regards, Kern ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
