[352] in linux-net channel archive
Re: Does NcFTP tickle a race?
daemon@ATHENA.MIT.EDU (Matti E. Aarnio [OH1MQK])
Fri May 19 18:01:07 1995
From: "Matti E. Aarnio [OH1MQK]" <mea@mea.cc.utu.fi>
To: steve@erinet.com (Steven J. Madsen)
Date: Sat, 20 May 1995 00:14:08 +0300 (EET DST)
Cc: linux-net@vger.rutgers.edu
In-Reply-To: <199505191701.NAA03872@localhost.erinet.com> from "Steven J. Madsen" at May 19, 95 01:01:04 pm
> I'm running NcFTP 2.0.5 on Linux 1.2.8, w/out the 1.3 networking
> code. My net connection is a 28.8 PPP link, which has otherwise worked just
> fine.
>
> It seems that either NcFTP has a bug, or it tickles a race condition
> in the old networking code. I've contacted the author, and he hasn't been
> terribly helpful, but I'm sure he's quite busy, so I thought I'd try here.
Frankly this sounds like interrupted write (for any reason),
and mishandled recovery after it.
Hmm.. At least the code on ncftp183/cmds.c[sendrequest()]
does sensible processing -- at least on BINARY-mode -- the
ASCII-mode path uses stdio's putc(), of which I can not, if
it is ok in this output file...
Which mode were you using when put:ing files ? ASCII or BINARY ?
(ncftp183 is on Slackware 2.2.0)
...
> Since 1.3 is probably coming quite soon, should I just abandon the
> 1.2.x networking code and start working with the 1.3 code, or is this more
> likely a problem with NcFTP?
>
> --
> Steve Madsen <steve@erinet.com>
> Finger smadsen@cs.muohio.edu for PGP public key
/Matti Aarnio <mea@utu.fi>
