>Is amrestore supposed to take a really long time to exit after a "quit"
>command? ...
Not sure what you mean by a "quit" command to amrestore. Did you mean
amrecover?
It could be cause by three things:
* amrestore might still be shipping the image to the restore program.
If you've already gotten the "set mode" question (assuming you're
using dump/restore), you can kill amrestore at this point because
restore has already seen everything it needs. Some restore programs
will go ahead and exit, others soak up the rest of the image.
* If amrestore quit in the middle of the image (because the reader
side, e.g. restore, terminated), the OS skips to the next file mark.
There isn't anything you can do about this.
* When everything is done, amidxtaped rewinds the tape.
Once you're sure you've got everything back you want, you might try
killing the amrestore child of amidxtaped on the tape server and see if
that speeds things up. That's what I do.
>Drew
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
