Re: [Duplicity-talk] First full backup has no errors, but --verify does

[Paul Walker]

I've hit reply on one of Kenneth's mails, but this might be more relevant to
the original poster.

> OTOH, if you run 'ncftp -u user site.org' and do an ls, it works.  I
> think the problem may be in ncftpls itself.

I did a bit of digging. Quick background - there seem to be two ways to get
a file listing from the server, NLST and LIST. LIST is not intended to be
machine readable.

The problem seems to be that ncftpls uses NLST (as you would expect), but
adds arguments to it. RFC959 does not mention any arguments being allowed.
PureFTPd appears to implement the RFC strictly (for some sense of that
word), and so returns an empty filelist.

You can get around this (if willing) by changing the ncftpls source to
remove the addition of "-CF" to the arguments. I have no idea why they're
there; I assume the ncftp author does.

Googling showed up a number of posts about this. The pureftpd guys claim to
be in the right according to the RFC, and aren't willing to change. On the
gripping hand, other servers appear to accept arguments, though whether they
do anything with them is debatable.

See also:

http://bugs.proftpd.org/show_bug.cgi?id=2322

It appears you can get pure-ftpd to play nicely by passing it "-b" when it
starts, for BrokenClient mode. If this is run by a host, though, that might
be hard.

I think we either get ncftpls fixed, or find a solution that involves not
using it...

Hope that helps someone; apologies for the length of the mail!

-- 
Paul

signature.asc
Description: Digital signature