18 Feb
2013
18 Feb
'13
11:23 p.m.
On 02/18/2013 06:09 PM, Michael B. Brutman wrote:
Chuck - I don't use ncftp, but that looks like the
symptoms of a broken
socket connection to me. I have no idea why your client feels the need
to invoke tar though. There is nothing in the incoming directory that
should set it off.
Mike, NCFTP has been around for years--it has both *nix and Windows
versions. It has many extensions, one of them being a recursive
directory crawl. So "get -R <filespec>" gets files and crawls the
directory tree. The message happens when the root directory has
finished and the first file from the next directory is fetched. I can
make it happen over and over again.
Would you like a log? I think NCFTP can get one. This was invoked from
Linux; I can also try it from Windows.
--Chuck