Hello,
the signature file don't corrospond to the file:
$ /cygdrive/c/Programme/Internet/GnuPT/GPG/gpg.exe -d winbacula-2.0.3.exe.sig
gpg: Signature made 03/01/07 10:03:11 using DSA key ID 10A792AD
gpg: BAD signature from Bacula Distribution Verification Key (www.bacula.org)
$
On Sunday 11 March 2007 17:08, Pierre Bernhardt wrote:
Hello,
the signature file don't corrospond to the file:
$ /cygdrive/c/Programme/Internet/GnuPT/GPG/gpg.exe -d
winbacula-2.0.3.exe.sig gpg: Signature made 03/01/07 10:03:11 using DSA key
ID 10A792AD
gpg: BAD signature from Bacula
Kern Sibbald schrieb:
Hello,
Hi,
Unless I am mistaken, even if there is a duplicate CN as you fear, it seems
to
me it should pose no problems because the certificate would not match.
Does someone more experienced with TLS know the answer to that?
Hmm. I'm not an expert but I've learned
Kern Sibbald schrieb:
On Sunday 11 March 2007 17:08, Pierre Bernhardt wrote:
Hello,
Hi,
the signature file don't corrospond to the file:
$ /cygdrive/c/Programme/Internet/GnuPT/GPG/gpg.exe -d
winbacula-2.0.3.exe.sig gpg: Signature made 03/01/07 10:03:11 using DSA key
ID 10A792AD
gpg: BAD
Hi Arno,
I made some tests and this is what I
think.
When there is a tape change after an
out of space error susequent block write continue to get that error even
after the tape change by the robot. This continue.
I made some changes to the block.c routine
(very simple, because I'm not a C
On Sat, 10 Mar 2007 12:46:04 +0100
Mikael Kermorgant [EMAIL PROTECTED] wrote:
How about using mirroring using raid1 ? (you'd probably have to buy
a thirs 200gb).
This way, you achieve data synchronisation easily, always have a
local copy from which to run restores and you cycle between 2
Bacula 2.0.3-1 released for SuSE 10.1 and 10.2 (x86_64) - see
sourceforge.net rpms-contrib-psheaffer or (soon to be) the sbarnin repo.
Thanks,
PattiMichelle
-
Take Surveys. Earn Cash. Influence the Future of IT
Join
Greetings Listers,
Last week I upgraded my Bacula install to 2.0.2 without any issues during the
upgrade process.
All seemed to be working well until Friday, but that was only because I hadn't
discovered this issue yet.
I run several jobs each night, with Full backups on Friday night and