-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon LaBadie wrote:
> But there is a separate decompression setp on recovery.
> It is done before decryption.
Yes, it contained a seperate decompression step, but this was only
necessary because of my stupidity and old tests... *arg* This step is
now go
On Mon, Mar 31, 2003 at 10:50:29AM -0800, philo vivero wrote:
> On Mon, 2003-03-31 at 06:24, Jon LaBadie wrote:
> > First, during encryption+compression the compression level is "9".
> >
> > dump_to_stdout () {
> > # Encrypt it, compress it, and send it on it's way
> > ${gpg_prog} --no-tty
On Mon, 2003-03-31 at 06:24, Jon LaBadie wrote:
> First, during encryption+compression the compression level is "9".
>
> dump_to_stdout () {
> # Encrypt it, compress it, and send it on it's way
> ${gpg_prog} --no-tty -q -e -z 9 -r ${gpg_as} -r ${gpg_as_self}
> Second I question the wisdom
On Mon, Mar 31, 2003 at 02:05:01PM +0200, Nicki Messerschmidt wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi all,
> I just finished my amanda - gpg setup and now I'm capable of backup
> files and restoring files (even with amrecover!).
> For thos who are curious how I did it I pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nicki Messerschmidt wrote:
> 6. configure source with: GZIP=/gpgzip [as attached]
> ./configure
... o.k. here is the attachement...
Cheers
Nicki
- --
Linksystem Muenchen GmbH [EMAIL PROTECTED]
Schloerstrasse 10
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I just finished my amanda - gpg setup and now I'm capable of backup
files and restoring files (even with amrecover!).
For thos who are curious how I did it I provide short step-by-step
instructions:
1. get and extract source
2. create operator
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I just set up amanda with gpg the way it is mentioned on [1], but now I
have a very mean problem. If I want to use amrecover I just get '500
"/" is an invalid directory' in my debug files. When I do 'strace -o
amindx -p 204 -f -ff -s 255' I get the
