>I discovered the problem while using amrecover and this exited with
>something like: An error occured: A child exited with status: 2
It would be useful to know exactly what the messages were, i.e. the
entire amidxtaped*debug file or wherever you saw them.
>I then tried to follow the procedure which I thought amrecover would
>run:
>1. grep the index files for the correct tapes
>2. load the correct tapes
>3. extract the appropriate image
>4. run tar to retrieve files
That's basically what it does, except step 3 is done by running amrestore
with the output piped back across the network to tar (step 4) running
on the client and reading it from stdin.
>The last part of my question covers amanda. I wonder why amrecover
>calls amrestore without the -p option ...
It doesn't. Amrecover (actually, amidxtaped) calls amrestore *with* the
-p option. Here's a sample amidxtaped*debug file from one of my systems:
amidxtaped: debug 1 pid 16285 ruid 2875 euid 2875 start time Mon May 21 16:38:39 2001
amidxtaped: version 2.4.2p2
> SECURITY USER root
bsd security: remote host champion.cc.purdue.edu user root local user backup
amandahosts security check passed
> 6
amrestore_nargs=6
> -h
> -p
> /tmp/tape.champion.cc.15700
> champion.cc.purdue.edu
> ^/home/champion/z$
> 20010508
Ready to execv amrestore with:
path = /opt/amanda-2.4.2p2/sbin/amrestore
argv[0] = "amrestore"
argv[1] = "-h"
argv[2] = "-p"
argv[3] = "/tmp/tape.champion.cc.15700"
argv[4] = "champion.cc.purdue.edu"
argv[5] = "^/home/champion/z$"
argv[6] = "20010508"
amrestore: WARNING: not at start of tape, file numbers will be offset
amrestore: 0: restoring champion.cc.purdue.edu._home_champion_z.20010508.0
amrestore: write error: Broken pipe
amidxtaped: amrestore terminated normally with status: 2
Rewinding tape: done
amidxtaped: pid 16285 finish time Mon May 21 18:43:38 2001
See "argv[2]"? Amrecover asked amidxtaped to pass "-p" to amrestore.
>Nicki
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
