>Just to make sure (and for the enlightenment of anyone else trying to
>duplicate the problem): you have removed /tmp/jrj/zli before every tar
>command, right? ...
Yes. What I posted was really the list of commands I put into a little
test script. The cp of /dev/null to zli is part of that and happens on
each run.
>'cause I can't seem to be able to duplicate this
>problem on my machines. ...
That also doesn't surprise me. By now this mailing list would have been
flooded with "why is Amanda broken" letters :-) if it was universal.
Not that that should make anyone feel warm and fuzzy about what *their*
GNU tar is doing.
>Do you know which compiler was used to build this version of GNU tar?
Looks like gcc 2.8.1.
>Did you try to read this tar-file with some other tar program? ...
Using Solaris tar (not exactly known for its stellar quality, either):
$ tar tvf z.tar
drwxr-xr-x 10281/1233 62 Jun 8 13:53 1999 07301033644/./
-rwxr-xr-x 10281/1233 10412 Jun 8 13:53 1999 07277623352/./getMailHostName
-rw-r--r-- 10281/1233 15044 Jun 7 18:16 1999 07277623352/./res_init.c
No complaints, but it also didn't show all four files, just the first
two (and with bogus names, but that's just Solaris tar being stupid).
AIX tar did the same thing (two files) but without the bogus directory
name.
On a whim, I changed the test to write to a pipe to cat instead of
directing stdout to the file since I know GNU tar looks at what it's
writing to (e.g. so it can detect /dev/null). Didn't help.
I also tried writing direcly via --file instead of "--file -". Ditto.
>Alexandre Oliva
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
