Hello Alexander,
I have been using 'lftp' for a short while now and like its ease-of-use. Thank
you
for the work you have done on it. My possible contribution is a patch for the
FAQ.
It was created with;
$ diff -Naur FAQ new_FAQ > FAQ.diff
This should apply it correctly:
$ ls
FAQ FAQ.diff
$ patch -p0 < FAQ.diff
This is my first attempt at proofreading someone else's writing, I hope it has
some value. The 'lftp' version is: 3.3.4.
Yours, Norm
====================================================================================
--- FAQ 2005-12-11 02:41:18.174766047 -0700
+++ new_FAQ 2005-12-11 02:05:16.755938744 -0700
@@ -1,40 +1,40 @@
Q: I have compile/link problems.
A: Some common installation problems are described in the INSTALL file.
- If your case is not covered, please send problem report.
+ If your case is not covered, please send a problem report.
-Q: How can I see greeting message from server?
-A: Try `debug 3'. It is disabled by default to keep screen clear in case
+Q: How can I see the greeting message from the server?
+A: Try `debug 3'. It is disabled by default to keep the screen clear in case
of several simultaneous connections.
Q: Why doesn't lftp download files like this: `lftp ftp://host/path/file'?
-A: It expects an URL of directory. To download a file use `lftpget URL'.
+A: It expects an URL of a directory. To download a file use `lftpget URL'.
Q: What is the %2F in ftp URL's?
A: RFC1738 specifies that clients handling ftp URL's should interpret them
as HOME relative by default. %2F stands for leading slash pointing to
root directory.
-Q: Why do secure protocols https and ftps give "PRNG not seeded" error message?
-A: Your system probably lacks /dev/random-like device. Create ~/.rnd file
- containing random characters and SSL will work. See also OpenSSL FAQ
+Q: Why do the secure protocols https and ftps give the "PRNG not seeded" error
message?
+A: Your system probably lacks a /dev/random-like device. Create a ~/.rnd file
+ containing random characters and SSL will work. See also the OpenSSL FAQ
about this.
Q: Why does lftp say that locking fails all the time? (on linux)
A: You have compiled lftp with large file support (>2G) but your kernel
- does not support 64 bit file locking. Either install a better kernel
+ does not support 64-bit file-locking. Either install a better kernel
(e.g. linux-2.4.x) or compile lftp without large file support
(configure --disable-largefile)
Q: Where is lls?
A: !ls
-Q: Why doesn't mirror download files starting with a dot? I can see the files
+Q: Why doesn't `mirror' download files starting with a dot? I can see the files
using `ls -a'.
A: Try `set ftp:list-options -a'.
Q: ^Z doesn't work in Cygwin.
A: Use "SET CYGWIN=TTY". This must be done before starting a shell, if any.
-Q: lftp consumes 100% CPU on MacOS X Tiger just waiting at command prompt.
+Q: lftp consumes 100% CPU on MacOS X Tiger just waiting at the command prompt.
A: See http://www.mail-archive.com/lftp%40uniyar.ac.ru/msg02101.html for
a workaround for MacOS X bug.
=========================================================================================
