*BSD News Article 90883


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!goanna.cs.rmit.edu.au!news.apana.org.au!cantor.edge.net.au!news.teragen.com.au!news.access.net.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!newsfeeds.sol.net!worldnet.att.net!howland.erols.net!newsfeed.internetmci.com!news.mem.net!usenet
From: Ken <welk@mem.net>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: FTP problem
Date: Wed, 12 Mar 1997 11:00:18 -0600
Organization: Synapse Internet Connections
Lines: 36
Message-ID: <3326E122.6174@mem.net>
Reply-To: welk@mem.net
NNTP-Posting-Host: dyn015.tc-1.mem.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.01 (Win95; I)
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:36944

Problem of the day for this newbie:
FTP transfers from client to FreeBSD 2.1.5 server usually fail or are so
slow that
I abort the process. The result typically is that the file is created in
the
target directory but with zero bytes. Sometimes a partial transfer
occurs.
Occasionally, a full, successful transfer occurs. Subsequent to
failures,
it seems additonal FTP requests, without breaking the FTP link, are
very, very slow or fail. Slow is defined here as minutes for a 10K
transfer
(or until I give up on the transfer). When using an FTP client
application
that indicates transfer progress, it may be giving a useful clue in that
it
appears that 8K may get transfered quickly but then there is virtually
no
additional movement of data. However, smaller files also either fail to
transfer or
take so long I abort the process.

This is a single client communicating with the FreeBSD server via
10baseT.
Permissions for the server's target directory are set to rwx for the
owner,
who is the user doing the FTP transfers.

Transfers from the server to the client are as fast as expected.

Will anyone give me guidance in what is being done incorrectly here?

Thanks.

Ken Welch
welk@mem.net