Message: 4
Date: Thu, 03 May 2007 02:28:52 +0200
From: Arno Lehmann <[EMAIL PROTECTED]>
Subject: Re: [Bacula-users] SetDebug / Trace
To: bacula-users
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
On 5/3/2007 1:01 AM, Darien Hager wro
.
Regards,
Kern
==
Message: 1
Date: Wed, 02 May 2007 16:01:56 -0700
From: Darien Hager <[EMAIL PROTECTED]>
Subject: Re: [Bacula-users] SetDebug / Trace
To: bacula-users
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Thanks, that
Hi,
On 5/3/2007 1:01 AM, Darien Hager wrote:
> Thanks, that worked, found my files. (Oddly enough, lsof on my system
> shows items for "bacula-dir" as for process "bacula-di". Wierd. No
> wonder grepping gave nothing.)
Looks like the output fields are length limited.
> Assuming my set up is re
Thanks, that worked, found my files. (Oddly enough, lsof on my system
shows items for "bacula-dir" as for process "bacula-di". Wierd. No
wonder grepping gave nothing.)
Assuming my set up is representative (Bacula 2.0.1 and 2.0.3), it
appears that the documentation needs some revision.
First, a
Hello,
On 5/2/2007 9:09 PM, Darien Hager wrote:
> I don't seem to have any .trace files from using setdebug.
Which versions? I did create trace files using 'setdebug level= trace=1
client/sd/dir' commands on unix, FreeBSD, Solaris and Windows, so I
think it's safe to say it does work :-)
> Am
I don't seem to have any .trace files from using setdebug. Am I doing
something wrong, misreading the documentation, etc?
Running the command, everything appears okay...
> *setdebug
> Enter new debug level: 200
> Available daemons are:
> 1: Director
> 2: Storage
> 3: Client
>
