Bug 7450 - wu-ftpd-2.6.0-1 doesn't work with mirror-2.8-6
wu-ftpd-2.6.0-1 doesn't work with mirror-2.8-6
Product: Red Hat Powertools
Classification: Retired
Component: mirror (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Powers
Depends On:
  Show dependency treegraph
Reported: 1999-11-30 14:26 EST by Cindy Sellers
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-01-18 10:33:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Cindy Sellers 1999-11-30 14:26:00 EST
using mirror.pl with wu-ftpd-2.5.0-9 I am able to mirror directories
correctly. When I upgrade to wu-ftpd-2.6.0-1 mirror.pl no longer works.
The first error that appears (when using '-d -d -d' to increase debugging
info) is in response to: LIST -lRAT
The contents of the directory is listed correctly but then the words:
'timed out' appear instead of '226 Transfer complete'
Later in the process I get the message:
'Failed to put <file>'
Still later I get:
"'SITE CHMOD 666': command not understood" (presumable because it's
trying 		to chmod a file that isn't there based on the previous error?)

Eventually I get the message:
'426 Data Connection: Connection reset by peer'

The files do not get mirrored.

I can recreate the error by uninstalling the old package and reinstalling
the new one. I can remove it by reverting to the old package (I uninstall
the new one first).

I can provide output from running mirror.pl in both cases as well as the
mirror confguration file as needed.
Comment 1 Bernhard Rosenkraenzer 2000-01-18 10:33:59 EST
This is a bug in mirror (see http://www.wu-ftpd.org/broken-clients.html).
We've fixed it a while ago in mirror-2.9-6.

Sorry for the delay, we just changed wu-ftpd maintainers.

Note You need to log in before you can comment on or make changes to this bug.