Is anyone else checking the .sig file against the
tar.gz source file? I can't check it against any
keyserver. Can someone tell me what keyserver
actually has the info these days?
TIA,
ZK
Looking for l
Martin Simmons wrote:
> Also, you could attach gdb to each daemon and run the gdb command
>
> thread apply all bt
>
11th Nov 07---
Have attached /sbin/bacual-dir /sbin/bacula-fd and /sbin/bacula-sd to
gdb, run the commands
and will now wait
As far as I have checked it, char encoding trouble is seen only
between non-Unicode and Unicode clients, i.e., files from non-Unicode
systems can be restored to non-Unicode systems (same for Unicode). If
the chars are not properly displayed on the director's interface,
there's no need to worry, but
> On Wed, 5 Dec 2007, Martin Simmons wrote:
>
>> If that is OK, then I suggest running the SD with debug level 200, which
>> might give us a clue where the error occurs.
>
> So far I have been unable to get it to fail using -d200, while it does
> fail if I don't specify a debug level. Maybe there i
On Wed, 5 Dec 2007, Martin Simmons wrote:
> If that is OK, then I suggest running the SD with debug level 200, which
> might give us a clue where the error occurs.
So far I have been unable to get it to fail using -d200, while it does
fail if I don't specify a debug level. Maybe there is a timi
Just a short update: Fedora 5 RPMs are online since last week. RPMs for Fedora
8
are currently blocked due to a glibc 2.7 issue. I'm still investigating this
(help welcome as always ;-).
fs
-
SF.Net email is sponsored by
