Proftpd INSTALL翻译（Troubleshoot和Help部分没有翻译）

有些翻译不是很好，请指教交流. email:ownregister@126.com

 

                ProFTPD 1.2 InstallationInstructions

               =======================================

 

------------

Introduction

------------

 

ProFTPD is designed to be configured forcompilation on the target system by

a single shell script, named 'configure',located in the top-level directory

of the source distribution.  This script, originally generated by the GNU

autoconf tool, will analyze your system andcreate a 'config.h' file that

*should* allow ProFTPD to compilecleanly.  On some systems it may benecessary

to give certain options to configure or totweak manually one or both of the

config.h and the top-level Makefile filesproduced by configure.

 

ProFTPD is designed to be very flexible,which necessarily leads to extra

compile-time and run-time configurationcomplexity.  The configure script

also can be used to customize your build,setting compile-time options

based on command line options that youprovide.  In particular, optional

software modules to be compiled intoProFTPD may be chosen this way.

 

In addition to those set by the configurescript, the file 'include/options.h'

contains a number of easily tweakablecompile-time options which will affect

ProFTPD's operation.  These options are never modified by theconfigure script.

Each option is documented in the headerfile itself.  Changing these values

is rarely needed, and most can beoverridden at run-time by directives in the

proftpd.conf configuration file.

 

Note that a sample RPM spec file has beenincluded in contrib/dist/rpm/.

 

NOTE TO PACKAGE MAINTAINERS:

       Please, do NOT remove the ELF .comment and .note sections.

 

If you install ProFTPD on a slightlyuncommon (or really new or old) platform,

please consider recording and sharing yourexperience.

 

 

------------------

Build Requirements

------------------

 

       o ANSI/ISO C89/C90 C compiler, e.g. GNU gcc

       o GNU make, though most system makes should work

        o ANSI C and POSIX run-time libraries

       o BSD sockets API

       o Disk space: ~4.5 MB to unpack, 6-8 MB to build, ~2 MB to install

 

 

 

-------------------------

Installation Instructions

-------------------------

 

0. Plan your installation.

Please, read through all the installation steps beforestarting.

安装前，请通读所有安装步骤。

   There are many compile-time customizations that you may wish to make,

   particularly regarding user authentication.  Read through README.modules

   and the other README.* and contrib/README.* files.

 

   Note that the following modules are included by default and need not

   be added explicitly: mod_auth, mod_core, mod_log, mod_ls, mod_site,

   mod_auth_unix and mod_xfer.  Also,if PAM is detected by configure,

   the mod_auth_pam module will be included automatically.  However, it has

been reportedthat some systems still require it to be added explicitly.

默认包含下列模块，而不需要明确添加：mod_auth,mod_core, mod_log, mod_ls, mod_site,mod_auth_unix and mod_xfer.如果configure检测到PAM，一般mod_auth_pam模块会自动添加。然而，有些系统会要求明确添加mod_auth_pam模块。

 

   You may need to specify the shared library search path on your system.

   See your system and compiler documentation.  Frequently, the -R or -rpath

   options are used for this operation. Be especially careful to set the

path on AIXsystems.  See README.AIX.

你可能需要指定共享库的搜索路径，看你的系统和编译文档。通常，-R或-rpath选项被用于这个操作。在AIX系统上，尤其要小心设置。看README.AIX.

 

   Hint: if your configure command line becomes long or complicated,

   you might try storing it in a sh script file, say '.configcmd'.

提示：配置命令太长，可以写成shell脚本形式。

 

1. Configure the software.

   Run the GNU autoconf 'configure' script in the top level directory to

   create config.h and all the Makefiles. In addition to configuring

   ProFTPD to compile on your system, you can use this step to customize

   some parameters of or add optional features to ProFTPD.  There are many

   configuration options.  To use thedefault values, you would simply run:

 

       $ ./configure

运行’configure’在顶层目录可以创建config.h和所有的Makefile。这个步骤除可以配置proftpd编译外，还可以添加编译选项增加proftpd特性。使用默认值，可以仅仅运行：

$./configure

 

   By default the ProFTPD files will be installed as user 'root' and the

   first group with gid 0 listed in /etc/group, usually 'root' or 'wheel'.

   If you wish to install using a different user or group ownership, set

   the install_user and install_group environment variables before running

   configure.  Using a Bourne-ishstyle shell (e.g. sh, ksh, bash), you can

do this on thecommand line like this:

        $ install_user=root install_group=wheel./configure

默认Proftpd会以root用户和/etc/group列表中第一个用户组（gid为0）安装，通常为‘root’  或 ‘wheel’。如果想以别的用户或组安装，在运行configure之前，设置安装用户和安装用户组环境变量。在bash shell下可以这样：

install_user=rootinstall_group=wheel ./configure

 

   Similarly, as is typical with GNU autoconf scripts, settings for the

   compilation system can be made, such as the compiler:

 

       $ ./configure CC=gcc CFLAGS='-O -g'

类似地，还可以设置系统可以使用的编译器：

$ ./configure CC=gccCFLAGS='-O -g'

 

   Other options can be given to configure as command line arguments.

All availablearguments can be listed by running './configure --help'.

Configure的其他配置选项也可以作为命令行参数给出。所有的可用参数可以通过

‘./configure –help’列出。

 

   By default proftpd and ftpshut are installed in /usr/local/sbin/,

   ftpcount and ftpwho in /usr/local/bin/, the configuration file in

   /usr/local/etc/, and the man pages in /usr/local/man/man?/.  Further,

   /usr/local/var/proftpd/ is used to hold the runtime scoreboard file.

    See the "Directory and file names"section of the './configure --help'

   output for the arguments to change these defaults.  For instance,

   to place all these directories under /usr/ rather than /usr/local/,

   you could use:

 

       $ ./configure --prefix=/usr

   Or, to place the configuration file in /etc/ and the runtime state

   files in /var/proftpd/, you would use:

 

       $ ./configure --sysconfdir=/etc --localstatedir=/var

默认，proftpd和ftpshut安装在/usr/local/sbin/, ftpcount and ftpwho 在/usr/local/bin/, 配置文件在/usr/local/etc/,手册页在/usr/local/man/man?/.

将来，/usr/local/var/proftpd/被用于存储运行时快报文件（scoreboardfile）。

看./configure –help输出参数来改变这些默认值。例如，用/usr/ 代替/usr/local/，

$ ./configure --prefix=/usr

 或者，为了代替在/etc/中的配置文件和在/var/proftpd/中的运行时状态文件，你可以：

  $ ./configure --sysconfdir=/etc--localstatedir=/var

 

   Optional ProFTPD modules can be included using '--with-modules=LIST',

   where 'LIST' is a colon-separated list of module names.  This applies

   only to optional modules, such as those found in the contrib/ directory

   (the core modules in the modules/ directory are either mandatory or

   included by default).  Forexample, if you wish to include both the

   readme and LDAP modules, you would use:

 

       $ ./configure --with-modules=mod_readme:mod_ldap

可选的Proftpd模块可以被包含，用  '--with-modules=LIST',这里‘LIST’使用“：”冒号分割的模块名列表。这仅仅用于可选模块，诸如那些可在contrib/目录下找到的模块（在modules/目录下的核心模块要么被强制包含要么默认包含）。例如，你想要包含readme和LDAP模块，你应该：

$ ./configure--with-modules=mod_readme:mod_ldap

 

   Some operating systems require you to use either '--enable-autoshadow'

   or '--enable-shadow' if you wish to use the system's shadow password

   file for user authentication. Using autoshadow allows proftpd to work

   with either shadow or traditional password files.

如果你想使用系统shadow密码文件给用户授权，一些系统可能要求你要么使用

'--enable-autoshadow' 要么使用'--enable-shadow'。使用自动映射允许proftpd可以使用shadow或者传统密码文件工作。

   If you wish to use SQL for user authentication, you must specify mod_sql

   and one SQL backend module, either mod_sql_mysql ormod_sql_postgres.

   Further, the backend module must be specified *later* in the modulelist,

   e.g. '--with-modules=mod_sql:mod_sql_postgres'.  Otherwise, compilation

   will succeed, but SQL authentication will not work.

如果想用SQL给用户授权，必须指定mod_sql 和一个SQL后端模块，后端要么是

mod_sql_mysql 要么mod_sql_postgres.    进一步，在模块列表中，后端模块必须指定“*later* ，例如'--with-modules=mod_sql:mod_sql_postgres'.  否则，编译成功后，SQL授权不能正常工作。

Be aware that if you ever need to rerun theconfigure script, you first

   should run 'make distclean'.

如果你需要重新运行configure脚本，你应当先运行’make distclean’.

 

2. Verify correct configure operation.(验证配置操作正确性)

   Watch the output of the configure script.  After configure has run,

   you may wish to inspect the config.h file to make sure configure didn't

make any wrong"guesses" for your platform.

观察configure脚本的输出。在运行配置configure文件后，你可能看到config.h文件，并确保没有任何’guesses’在你的平台上。

3. Compile the software.（编译软件）

   Run 'make' from the top-level directory. On some systems (e.g. BSDI),

   you may need to use GNU make (often 'gmake' or 'gnumake') instead of

   the default system make.  Watchthe output of the compile process and

   make sure no errors occur.  Onsome platforms (notably AIX and IRIX)

   you may see some compilation or link warnings.  These generally can

   be ignored.

Make编译软件。确保没有错误输出。在一些平台（尤其AIX和IRIX）一些编译或者链接警告，一般可以忽略。

 

4. Test the software.（测试软件）

   As of ProFTPD 1.2.0, there are no automated regression tests.

   However, you are encouraged to perform your own ad-hoc, manual tests.

    1.2.0没有自动回归测试。然而，你可以执行自己专门的手动测试。

   Note that you can start proftpd directly from your shell prompt, but do

   remember that it must run as root for all functions to operate properly.

   Nonetheless, many operations can be verified without root privileges.

   An alternate configuration file can be specified using the '-c' command

   line switch.  In the configurationfile, the TCP ports may be changed

    from the standard default ftp (21) andftp-data (20) ports, and an

    alternate passwd file may bespecified.  Since such a daemon will notbe

    able to change its uid, you also mustspecify the user and group names

    to match those used to start the daemon.

   To demonstrate this process, a set of example config files have been

included in thesample-configurations subdirectory.

你可以直接从你的shell启动proftpd，但是记住必须用root用户运行所有的函数操作。然而，许多操作没有root特权也可以被验证。可选的配置文件可以用‘-c’命令行开关指定。在配置文件中，TCP端口可以被改变从标准默认的21号和ftp数据端口（20号），并且可选的密码文件可以被指定。因为守护进程不能改变它的uid，你必须指定用户和组名以匹配那些过去启动的守护进程。为展示这个过程，配置例子放在sample-configurations目录。

 

% sh sample-configurations/PFTEST.install

       Sample test files successfully installed in /tmp/PFTEST.

       % ./proftpd -n -d 5 -c /tmp/PFTEST/PFTEST.conf

 

   Then, in another window, connect to the unprivileged port.  PFTEST.conf

   uses port 2021, and PFTEST.passwd defines a user "proftpd"with password

   "proftpd".  Using thetraditional Unix ftp client, it might look something

like this:

在另一个窗口，连接非特权端口。PFTEST.conf使用端口2021，PFTEST.passwd定义一个用户“proftpd“，其密码是”proftpd“。使用传统unix ftp客户端，按下面这样：

       % ftp -n -d

       ftp> open <hostname> 2021

       ftp> user proftpd

       ---> USER proftpd

       331 Password required for proftpd.

       Password: [proftpd]

       ---> PASS proftpd

       230 User proftpd logged in.

       ftp>

 

   The supplied PFTEST.passwd is in traditional Unix format.  Your system

   may use a different file format, so you may have to create your own.

   Further, you may have to use another method to insert your user andgroup

   names into the PFTEST.conf file, if the PFTEST.install script fails.

   If you encounter any problems, be sure to see the"Troubleshooting" and

   "Help" sections below.

提供的PFTEST.passwd是传统Unix格式。你系统可能是不同文件格式，你应该创建自己的。甚至，如果PFTEST.conf脚本失败，你可能需要用别的法把你的用户名和组名插入PFTEST.conf文件。如果你遇到任何问题，非常必要看下边“Troubleshooting“和”Help“部分。

5. Package the software.

   As of ProFTPD 1.2.0, no packaging procedures are provided other than

   the inclusion of an RPM spec file in the contrib/dist/rpm/ directory.

6. Install the software.（安装软件，需root用户权限）

   Note: this and the following steps likely require root privileges.

   Unless a system specific installation package was created, e.g. an RPM,

    run'make install' from the top-level build directory.  This installs

   the ProFTPD executables, man pages, and a basic configuration file,

   copied from 'sample-configurations/basic.conf'.  The full path to the

   configuration file will be '/usr/local/etc/proftpd.conf', unless it was

   changed in Step 1.

 

   If an installation package was created, install the ProFTPD package

   according to procedures appropriate for that packaging system.

‘make install’，这将安装Proftpd可执行文件，手册页和一个基本的配置文件（从‘sample-configurations/basic.conf’拷贝）。配置文件的全路径为’/usr/local/etc/proftpd.conf’，除非第一步改变了它。

 

7. Modify the proftpd configuration file.（修改proftpd配置文件）

   If the User and Group specified in proftpd.conf do not exist on your

   system proftpd WILL NOT RUN.  Editand modify proftpd.conf as needed.

   Many systems have the group "nobody" instead of the group"nogroup".

    Decide how you want to run proftpd, either started by inetd(or xinetd)

    or as a standalone daemon.  Then edit the proftpd.conffile and change

   the ServerType directive to match your choice, either "ServerTypeinetd"

   or "ServerType standalone". The "basic.conf" config file, installed by

   'make install' in Step 4, has a default setting of"standalone".

如果在proftpd.conf中指定的用户名和组在你系统中不存在proftpd不会运行。编辑修改proftpd.conf文件。许多系统用“nobody“代替”nogroup“。决定逆行怎么运行proftpd，是网络运行还是作为单机运行。在ServerType指示匹配项，ServerType inetd"or "ServerTypestandalone"。默认是”standalone“。

8. Modify the inetd superserver configuration file.（修改inetd超级服务配置文件）

    Edit/etc/inetd.conf and then send the inetd process the -HUP signal,

   so that it will reread the updated configuration file.  On some systems

   there are other mechanisms to tell inetd to reread its configurationfile,

   e.g. 'refresh -s inetd' on AIX. Check your system documentation to see

   what command is appropriate.

编辑/etc/inetd.conf，给inetd进程发送HUP信号，以便inetd重新读取已更新的配置文件。在一些系统，有另外的机制通知inetd重新读取它的配置文件，例如'refresh -s inetd' on AIX.检查你的系统文档，看看合适的命令。

   If proftpd is to be run from inetd, find the line in /etc/inetd.conf

that lookssomething like:

如果proftpd是由inetd启动，看/etc/inetd.conf，它看起来像下边这样：

       ftp stream tcp nowait root     /usr/sbin/in.ftpd in.ftpd

 

    And replace it with:（用下边这样的替换上边的）

 

       ftp stream tcp nowait root      /usr/local/sbin/proftpdproftpd

 

   Or, if the tcp wrappers package is installed on your system, you may

   use a line something like:

或者，如果tcp封包器在你系统上被安装，你可以用下边这行：

       ftp stream tcp nowait root     /usr/sbin/tcpd /usr/local/sbin/proftpd

 

   If proftpd is to be run in standalone mode, you should comment out any

   ftp line in the /etc/inetd.conf file by inserting a '#' at the beginning

   of the line.  Then signal theinetd process to reread /etc/inetd.conf.

如果proftpd以‘standalone’模式运行，你应该在/etc/inetd.conf中注释掉所有的

ftp行，然后发信号给inetd进程重新读取/etc/inetd.conf配置文件。

   If your system is using xinetd instead of inetd then either edit

   your /etc/xinetd.conf file or add a proftpd file in /etc/xinetd.d/

如果你系统使用xinetd，要么编辑/etc/xinetd.conf文件，要么在/etc/xinetd.d/目录下添加一个proftpd文件，内容如下：

   service ftp

    {

      flags           = REUSE

      socket_type     = stream

      instances       = 50

      wait            = no

      user            = root

      server          =/usr/sbin/proftpd

      bind            = <the-ip-you-wish-to-bind-to>

      log_on_success  = HOST PID

      log_on_failure  = HOST

    }

 

   More information can be found in the FAQ and Userguide and in the

   xinetd documentation for your system

更多信息看FAQ和Userguide和Xinetd文档。

9. Modify the system boot scripts.（修改系统启动脚本）

   If running in standalone mode, you probably will want to edit your boot

   scripts to start proftpd at boot time. For systems that use SysV-style

   individual startup scripts, the source distribution includes an example

   init script, "contrib/dist/rpm/proftpd.init.d".

运行于Standalone模式，可能想要修改启动时的启动脚本。SysV风格启动脚本，例子

"contrib/dist/rpm/proftpd.init.d".

10. Create the runtime state directory.（创建运行时状态目录）

    In order for the MaxClients and MaxClientsPerHost directivesand the

    ftpwho and ftpcount utilities to work,proftpd must have a scoreboard

    file.  The default is'/usr/local/var/proftpd/proftpd.scoreboard', though

   it may have been changed in the configuration process in Step 1.

   The default location also can be overridden at run-time by using the

   ScoreboardFile directive in the proftpd.conf configuration file.

   If the indicated file does not exist, it will be created when the daemon

   starts up.  If you have installedfrom an installation package, the

   installation scripts may have created the default directory.

为了MaxClients and MaxClientsPerHost指令和ftpwho及ftpcount工具工作，proftpd必须有快报文件。默认'/usr/local/var/proftpd/proftpd.scoreboard'。通过使用在proftpd.conf配置文件中的快报文件指令，默认位置可能被运行时重写。如果被指明的文件不存在，当守护进程启动时，该文件会被创建。如果你从安装包安装了，这些安装脚本可以创建默认的目录。

11. Verify operation.（验证操作）

   Once proftpd either has been configured to be started by inetd or has

   been started in standalone mode, try ftp'ing to your system to make

   sure that everything works.  Asbefore, if you run into any problems,

   see the "Troubleshooting" and "Help" sections below.

无论proftpd以inetd方式还是standalone方式启动，尽力ftp’ing你的系统，确保一切正常。如果有问题，看"Troubleshooting" and "Help"sections below.

12. Customize theproftpd configuration file.（定制proftpd配置文件）

   If you wish to add anonymous ftp or otherwise create a moresophisticated

   ftp configuration, read more about configuring ProFTPD:

如果你想添加匿名ftp或者创建更多复杂ftp配置，读更多的Proftpd 配置：

       Configuration Examples: sample-configurations/*.conf

      Configuration Reference: doc/Configuration.html

                 Documentation:http://www.proftpd.org/docs/

                           FAQ:http://www.proftpd.org/docs/faq/linked/faq.html

 

   Note that some systems will require special system-specific preparation

   of the anonymous ftp and any other chroot directories.  PLEASE NOTE

   that the configuration directives "PersistentPasswd","RequireValidShell",

   and "UseFtpUsers" may require special attention.

注意：一些系统需要为匿名ftp做特殊准备或者chroot目录。请注意the configuration directives"PersistentPasswd", "RequireValidShell",and"UseFtpUsers"。

 

   To check the syntax of a new or modified configuration file, you may

   run 'proftpd -t -c <new_conf_file>' from the command line.

检查新的或者修改过的配置文件的语法，可以运行'proftpd -t -c <new_conf_file>'命令。

   You can test the runtime function of your configuration file without

   interfering with a running server, by running a separate test server

   on a different port.  Specify theport to use with the "Port" directive

   in the configuration file, but don't forget to restore the port setting

   before installing the new configuration file for the production server.

在一个不同的端口上运行单独的测试服务，你可以测试你的配置文件的运行时函数，而不妨碍正在运行的服务。在配置文件中用“Port“指令指定端口，并保存端口设置。

 

Good luck!

 

 

 

---------------

Troubleshooting

---------------

 

This section is far fromcomprehensive.  See the FAQ and otherresourses

for further assistance.

 

 

T1. Compile time problems are often easy tosort out by giving the right

   options and search paths to the compiler.  However, at other times they

   can be rather difficult to debug. Problems often result from header

   file or C preprocessor macro name conflicts.  A few packages have been

   known to install conf.h headers in /usr/local/include.  Occasionally,

   one must resort to looking at the preprocessor output.  Consult your

   compiler documentation for how to do this, though a command similar

   to `cc -E file.c` often works.

 

   Some common error messages include:

 

       o "symbol ap_signal undefined in main.o"

         This usually means that the fnmatch.h header is including

         the Apache ap_config.h header, though proftpd does not link

         with the Apache library.  Thismostly happens on Solaris 8,

         though a similar problem has been reported on Red Hat 6.0

         systems with the <hsregex.h> header.

 

 

T2. If you encounter run-time problems,first check your syslog messages.

   The proftpd daemon logs all the error conditions that it encounters,

   including problems parsing the configuration file.  Authentication related

   messages are logged using the syslog facility "auth" or, ifavailable,

   "authpriv".  All othermessages use the syslog "daemon" facility, unless

   redirected by the "-n" command line switch or by theSyslogFacility or

   SystemLog directives.  Check yoursyslogd.conf to see what syslogd does

   with these messages.

 

   Some common error messages include:

 

       o "inet_create_connection() failed: Operation not permitted"

         This usually means that proftpd was not started as root.

 

       o "bind: unable to bind to port" or "Address already inuse"

         This usually means that another process, either inetd, xinetd or

         another standalone ftp server, is already using the ftp port.

 

       o "Fatal: Socket operation on non-socket"

         This usually means that proftpd.conf ServerType directive is

         configured for inetd rather than standalone mode.

 

       o "received: PASS (hidden)"

         "ProFTPD terminating (signal 11)"

         This usually means that shadow passwd file support is required

         but was not compiled in.  Trystarting the build over at Step 1,

         adding either '--enable-autoshadow' or '--enable-shadow' to

         the configure command line.

 

   If users can not login and your system uses PAM authentication, you may

   need to configure PAM to work for FTP. For further details, consult your

   system PAM documentation.  If youhave installed from a package, hopefully

   this was done automatically.  OnLinux systems, the following may work:

 

       % cp -p contrib/dist/rpm/ftp.pamd /etc/pam.d/ftp

 

   If your client sees something like "server error 500, server shutdown",

   that probably means that you have a stale /etc/shutmsg file, which you

   should delete.

 

 

T3. You can generate additional debuggingmessages by starting the proftpd

   daemon with the "-d N" command line option, where N rangesfrom 1 to 10,

    withhigher values increase the number of debugging messages.  If you are

   running the daemon standalone, you also may wish to use the"-n" option,

   which will keep the daemon from disassociating from your terminal and

   cause all messages to display directly on your terminal rather than

   being syslogged.

 

 

T4. If you encounter problems not readilydiagnosed by the error messages,

   you might check for a newer ProFTPD release at the official distribution

   sites to see if your problem has already been fixed.  Reading the

   ChangeLog file in each new distribution is often the fastest way to

   see what bugs have been fixed.

 

 

T5. If your system has a system call traceutility, you may wish to use it

   to diagnose what is failing. Often this method is useful to spot a

   file open failures, including shared libraries.

 

   Some system call trace utilities:

       o truss (Solaris, SVR4 derivatives, Unixware, AIX5L, FreeBSD)

       o trace (SunOS 4.x)

       o tusc (HP/UX 11.x: ftp://ftp.cup.hp.com/dist/networking/tools/)

         trace

           http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/trace-1.6/

           http://devresource.hp.com/devresource/Tools/ToolLibrary.html#perfhp

       o syscalls, trace (AIX 4.x); sctrace

       o par (IRIX)

       o alpha-trace (Digital Unix: ftp://ftp.mrc-lmb.cam.ac.uk/pub/jkb/)

       o ktrace/kdump (FreeBSD, OpenBSD, NetBSD)

       o strace, ktrace/kdump, ltrace (Linux)

 

 

T6. Another diagnostic technique is tomonitor the FTP protocol communication

   between the proftpd server and the ftp client.  Many ftp clients have a

   debug or trace option.  Thoughrequiring detailed knowledge of the FTP

   protocol, telnet can be used to connect and directly converse with the

   proftpd server.  Lastly, the FTPconverstation can be traced using a

   network monitoring tool, such as tcpdump, ethereal, snoop or netsnoop.

 

 

T7. Further debugging probably will requirethe use of a debugger,

   which may require recompiling proftpd with debugging symbols.

   Consult your compiler and debugger documentation.

 

 

 

----

Help

----

 

H1. Before asking for help on the mailinglist, look through the available

   documentation, including the FAQ and the searchable archives of the

   mailing lists.  Not only are manycommon questions answered in those

   documents, but they will often yield answers faster than a question

   sent to the mailing list.

 

   See the "Resources" section below for documentation pointersand links.

 

 

H2. When posting to the mailing list, tryto be clear and concise, but give

   enough information to enable people to help.  Merely stating something

   like "It doesn't work. Help!" is unlikely to elicit any useful answers.

   Describe your problem as completely as possible, including what youthink

   is wrong, what behavior you expect, and any relevant error log messages

   or debug output.  Unless theproblem occurs with the base proftpd.conf

   file or a minimal derivative, it may be useful to include part or all of

   your proftpd.conf file.

 

   So, at a minimum, you should include:

       o OS type and version (e.g. `uname -a`)

       o ProFTPD extended version info (`proftpd -V` and `proftpd -vv`)

       o ProFTPD module list (`proftpd -l`)

 

   The following may help to further identify compilation information,

   especially if you are installing a vendor supplied package rather than

   building from sources yourself:

       o `what proftpd` or `ident proftpd`

 

   And still more compilation information may be available if your system

   uses the ELF object file format:

       o `objdump -f proftpd` or `dump -v -f proftpd`

         or `elfdump -v -f proftpd`

       o `objdump -j .comment proftpd` or `dump -n .comment proftpd`

         or `elfdump -n .comment proftpd`

       o `mcs -p proftpd`

       o `objdump -j .note proftpd` or `dump -v -n .note proftpd`

          or `elfdump -v -n .note proftpd` or `mcs -p -n .note proftpd`

 

 

H3. Please, please, do NOT use the bugreporting system for compilation or

    configurationproblems and questions.  Those should besent to the

   mailing list.

 

   In order conserve development resources, please only submit bug reports

   when you have reasonable confidence that there is an actual code bug,

    aportability problem, or problems with the build and compilation system.

   Even then, please first search the bug system to see if your bug hasbeen

   reported already.  If it has, useyour own best judgement about adding

   comments to the existing report, especially either to confirm the bug's

   existence or to provide additional diagnostic and debugging information.

 

   For some more suggestions about reporting bugs, see:

       http://bugs.proftpd.org/bugwritinghelp.html

 

 

 

---------

Resources

---------

 

R1. Basics.

 

   Various Subjects: README.*, contrib/README.*

  Configuration Ref: doc/Configuration.html

 Config/Problem FAQ: doc/faq.html

 

                 WWW: http://www.proftpd.org

                 FTP:ftp://ftp.proftpd.org/distrib/

   Mirror Site List: http://www.proftpd.org/wwwmirror.html

 

 

R2. ProFTPD Documentation Project.

   Documents include a Configuration Reference, draft User Guide, and FAQ.

   Formats include linked and single HTML files, PostScript, PDF and text.

 

   Note that this Configuration Reference may refer to a newer code base

   than you are using.  So, referringto doc/Configuration.html file in

   your source distribution may be less confusing.

 

              (main):http://sourceforge.net/projects/pdd

 

 

R3. E-Mail Lists.

 

      End User List

      (submissions): proftp-user@lists.sourceforge.net

        (subscribe): proftp-user-request@lists.sourceforge.net

         (archives):http://sourceforge.net/mailarchive/forum.php?forum_name=proftp-user

 

     Developer List

      (submissions): proftp-devel@lists.sourceforge.net

        (subscribe): proftp-devel-request@lists.sourceforge.net

         (archives):http://sourceforge.net/mailarchive/forum.php?forum_name=proftp-devel

 

  Announcement List

        (subscribe): proftp-announce-request@lists.sourceforge.net

         (archives):ttp://sourceforge.net/mailarchive/forum.php?forum_name=proftp-announce

 

   Security Reports: security@proftpd.org

 

 

R4. Bug Tracking System (Bugzilla).

 

 BugReports/Patches: http://bugs.proftpd.org

                     proftp-devel@lists.sourceforge.net

 

 

R5. CVS Repositories.

 

      Anonymous CVS: cvs.proftp.sourceforge.net

     (instructions): http://www.proftpd.org/cvs.html

       CVS tarballs: ftp://ftp.stikman.com/pub/proftpd/

                     ftp://ftp.linuxceptional.com/proftpd/

 

    Development CVS:http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/proftp/proftpd/

 

 

R6. Statement about proftpd.org andproftpd.net.

 

   The www.proftpd.org and www.proftpd.net sites now should be effectively

   mirrors of one another.  Theofficial proftpd site is www.proftpd.org,

   however www.proftpd.net will remain in operation at a physically remote

   location in order to provide redundancy.