One way is to start a recover:
root> amrecover <config>
setdisk /myDLE
ls
cd <somedir>
ls
repeat until you are sure the contents you wanted is in there.
Recover 1 or 2 of the files, (to a scratch area) to be sure you
wholly trust the contents.
Actually, another way, once you’ve done
root> amrecover <config>
setdisk /myDLE
is to go to your log directory, in another window, while that first
window is STILL paused there, and has not exited am recover.
The content listing will be sitting in the logs /index / name-of-DLE
directory, unpacked, but only for as long as you are still inside the
amrecover process.
You can copy that file elsewhere, and your purloined copy will stick
around.
Deb Baddorf
Fermilab
> On Oct 24, 2017, at 9:33 PM, Jobst Schmalenbach <jo...@barrett.com.au> wrote:
>
> Hi
> How can I see the contents of gnutar-list files?
>
> I tried tar/gunzip, ckecked amadmin etc but it seems I cannot read the
> content.
>
> Need to know whats in those files to see whether my inclusion/exclusion list
> is correct and why it takes too much time to backup one particular host.
>
>
> Jobst
>
>
>
>
> --
> Computers run on smoke, once the smoke gets out they don't work anymore!
>
> | |0| | Jobst Schmalenbach, General Manager
> | | |0| Barrett & Sales Essentials
> |0|0|0| +61 3 9533 0000, POBox 277, Caulfield South, 3162, Australia
