known-bugs

ftp服务器源程序

List of known bugs and problems:
- The -R argument to list seems to ignore the argument given to it (this is not
  very high on the list ATM).
- Some commands are still not implemented (see the file RFC-COMPLIANCE). There
  are very few I actually miss now... None, actually.
- There are several hardcoded limits, instead of using constants such as
  PATH_MAX.
- We should move the remaining bugs listed from the source (in the comments)
  to this file ;-)
- If a command that requires a parameter doesn't have one, BetaFTPD will send
  500 instead of 501. This behaviour is very useful in the command lookup
  (for code simplicity) :-)
- We could (perhaps) use a hash table instead of a straight linear command search?
- REST does not work in ASCII mode. (This is partly as a security measure --
  enabling resuming on ASCII files could need a lot of CPU power if we had to
  resume in the middle of a big file, and still stay RFC/ftpext-compliant.) 
- In general, nonroot support has problems. For instance, security is generally
  weak, and anonymous FTP is not supported (all users will need a password).
  Nonroot is not even worked on at the moment. Don't use it :-)
- Occasionally, a directory listing may cause unwanted output in the fullscreen
  mode, for some weird reason.
- There are reports of the server not working at all in fullscreen mode. We're
  working to find and fix these problems.
- Some features like ftpshut and ftpaccess files (no, root can't FTP anymore,
  that is blocked) are missing.

Obscure bugs I haven't seen in a long time (probably fixed):
- The server is still known to segfault from time to time, but unfortunately,
  most kernel versions won't dump core if the program has changed uid :-(
- Sometimes (after an error) the server doesn't respond to the connection
  anymore. Weird.
- Some times, for no reason at all, mmap() on my machine will fail with a
  EINPROGRESS, which is a non-legal error code. I'm not sure if this is
  a bug in BetaFTPD or glibc :-)