daemon process.
23. 503 No PORT command issued
A bug was introduced in 1.2.0rc2 which prevented the PORT command working properly and therefore breaking the data socket
under certain conditions. The bug was documented as bug 240 and has been fixed in CVS. A rc3 release is due before the end of
Jan 2001.
24. Fatal: unable to determine IP address of
Proftpd was unable to work out what IP is associated with the hostname in the VirtualHost block. Normally caused by a problem
with the DNS resolution of the host, check the resolv.conf file and that your chosen nameservers are functional.
25. 451 append/restart not permitted, try again
AllowStoreRestart is disabled by default because it will allow any writable file to be corrupted by a malicious user. It is
recommended that this option is only used with authenticated users and then only in certain directories.
26. 501 REST not compatible with server configuration
As mentioned in the description of the HiddenStor configuration directive, use of that directive is incompatible with the FTP
command REST. Either disable use of REST with the AllowRetrieveRestart and AllowStoreRestart directives, or do not use
HiddenStor.
27. The time being displayed is wrong
The default behaviour for ProFTPD is to display all times relative to GMT. To use local time set "TimesGMT off" in the server
section of the config. There is a known issue with Redhat 7, with regard to time handling.
http://www.redhat.com/support/errata/rh7-errata-bugfixes.html
28. Authentication is taking too long
Make sure that ReverseDNS is disabled, turn off ident lookups. Additionally check the size of your /etc/passwd (or shadow)
file, if it is large then the only solution may be to move to another authentication scheme.
29. Corrupted files
There appear to be some problems with both the use of sendfile() in ProFTPD and with the implementation within certain
operating systems.
30. Can I upgrade ProFTPD without terminating the current sessions?
Short answer, no. Longer answer is no, but you can minimise the effects. The cleanest approach on servers which have
significant amounts of traffic appears to be to use ftpshut to block new connections and terminate existing ones after a pre
-determined time period and then to upgrade and restart. This approach limits the number of downloads which are terminated
part way through.
31. No such group "nogroup"
The default ProFTPD configuration file uses the user "nouser" and the group "nogroup", some systems / distributions do not
have the group "nogroup" defined. The solution is to either add the group "nogroup" to /etc/groups or to change the "nogroup"
entry in the proftpd.conf to a group which does exist.
32. Why do I see "unable to set groups: Invalid argument"?
The setting of the group privileges for a process uses the setgroups(2) system call. This call will fail with the above error
message for one of two reasons: there is a negative GID value for one of the groups, or the maximum number of groups for a
single user has been exceeded.
Ideally, all IDs, both UID and GID, will be positive. Unfortunately, it is common on many systems to use -1 or -2, especially
for such users as "nobody", or group "nogroup". Use of these values uses C"s treatment of data types to make the actual
numeric value very high; some functions, like setgroups(), do not like this, though. In general, always use positive ID
numbers.
The other limitation is the number of supplemental groups for a user (eg non-primary groups, the ones configured in
/etc/group). The maximum number of supplemental groups to which a user may belong is defined by the operating system constant
NGROUPS_MAX. On some operating systems, such as Solaris, this limitation may be tunable.
推荐阅读
- 梨的糖分含量高吗 梨的糖分含量高不高
- 棉花伏蚜的发生与防治技术
- 怎么和导师讨论论文选题
- 华为mate20pro中一键换机的操作方法
- 什么地方被称为世界屋脊的屋脊
- 待机时间超短
- 小番茄的功效与作用 小番茄的禁忌
- 土钉墙和锚杆的区别
- 劳动法哺乳期规定多长时间
- vivox27进行调整时间的操作教程
