Jon LaBadie said:
> Interesting.  Of course as I do not amverify I would not have
> encountered that problem.  I looked at amverify.  It is a shell
> script.  In there is a section:
>
>     if [ X"$1" = X"program" -a X"$2" != X"" ]; then
>       if [ X"$TAR" != X"" \
>            -a \( X"`basename $2`" = X"`basename $TAR`" \
>                  -o X"`basename $2`" = X"gtar" \
>                  -o X"`basename $2`" = X"gnutar" \
>                  -o X"`basename $2`" = X"tar" \) ]; then
>               CMD=$TAR
>               ARGS="tf -"
>       elif [ X"$TAR" != X"" \
>              -a X"$SAMBA_CLIENT" != X"" \
>              -a X"$2" = X"$SAMBA_CLIENT" ]; then
>               CMD=$TAR
>               ARGS="tf -"
>
> Which on first inspection would suggest there is a limitation.
> I'll see if I can look at this closer in the future.  Now I'm
> taking down my system and updating the OS.

Kewl. I didn't realize amverify is just a shell script. I'm using
2.4.2p2, and my version of amverify appears not include gtar or
gnutar. I'm adding gtar and nttar to the "accepted" list in my
amverify script. I'll see how well it works...

-- 
Kurt Yoder
Sport & Health network administrator