Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Brian Kelly" <reedfish AT ix DOT netcom DOT com>
To: <cygwin AT cygwin DOT com>
Subject: Mysterious FTP failure
Date: Thu, 19 Dec 2002 09:15:53 -0500
Message-ID: <001801c2a769$24f7f5f0$0100a8c0@maxstars8g31h2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id gBJEEcY31667

I’ve been using cygwin’s ftp.exe client program on my NT 4.0 SP 6
machine for quite a while. It’s
worked flawlessly for months. I have not made any changes to the box and
have not upgraded any
cygwin components in months. Sometime in the last 48 hours “something”
changed. Now when
I attempt to ftp a tar file, it sends about 98-99% of it or so, and then
mysteriously quits – “thinking”
it had sent the whole thing. (It does not report any transmission
errors). It’s not tar, because if I
ftp TO the box via inetd/ftpd and retrieve the file – the whole thing
transfers just fine. I’ve rebooted the
box numerous times, as well cold shutdown (to reset the network card) –
same problem. I haven’t
tried uninstalling or reinstalling any cygwin components, because I’d
really like to understand what’s
CAUSING the problem. I’m writing automation software that has advanced
error checking and I’d
like to trap and “identify” this condition (if possible) and advise in
an error message what the possible
genesis of the condition is and what hints one can follow to remedy
and/or prevent the problem. The
automation software essentially “automates” cross-network unix
command-line environments and is
100% perl. As such, it relies on cygwin for this environment on MSWin
boxes. If one “node” fails – it
can switch boxes automatically – but being able to determine WHY a box
has a problem and reporting
it successfully is VERY important to the overall approach of the
software.
 
If anyone’s got a clue what’s happened to break ftp – or can suggest
what other things I can investigate
to get the “bottom” of this problem – I’d REALLY appreciate it.
 
Brian Kelly


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/