Paul Bijnens wrote:
>
> Chris Karakas wrote:
>
> > ? /bin/gtar: : Cannot stat: No such file or directory
> > ? /bin/gtar: : Warning: Cannot stat: No such file or directory
> > | Total bytes written: 53729280 (51MB, 20kB/s)
> > ? /bin/gtar: Error exit delayed from previous errors
> > sendbackup: error [/usr/local/bin/gtar-wrapper returned 2]
> > \--------
>
> 2. It seems somehow that an empty element or something with an invisible
> character (space? backspace? etc) is passed to gtar, and it says "No
> such file dor directory".
> Could this be caused by your gtar wrapper script?
>
Bingo! That indeed seems to be the case! I invoke tar in the
gtar.wrapper script as follows:
$DEBUG $GTAR "$1" "$2" "$3" "$6" "$7" "$8" "$9" "${10}" "${11}" "${12}"
"${13}" "${14}" "${15}" "${16}"
Now, the problem is that parameter nr. 16 may, or may not be filled,
depending on whether the "--exclude-from=" option is passed. And this
depends on the dumptype. ("--exclude-from=" is not parameter nr. 16, but
rather parameter nr. 15, but if it is not passed, then ".", which is
always the last parameter passed to tar/gtar-wrapper, becomes the nr. 15
and nr. 16 is empty, which causes it to be interpreted as a
filename...).
Thanks Paul! :-)
So the solution will be to pass *exactly* the non-empty parameters to
GTAR. This is Korn shell (ksh). Any elegant, compact suggestions from
the script profs?
--
Regards
Chris Karakas
Don´t waste your cpu time - crack rc5: http://www.distributed.net
