0b2f9152b1
This is preferable for binary package use as it allowes the user to choose which features to enable by changeing the configuration file instead of recompiling. This is also how ProFTPD is usually packaged in other systems. For details about ProFTPD and DSO see: http://www.proftpd.org/docs/howto/DSO.html This change removes the following PKG_OPTIONS.proftpd: ban, ldap, mysql, pgsql, proftpd-readme, quota, tls and wrap The modules that were previously compiled when enabling ban, proftpd-readme, quota or tls are now always included. To load them use a configuration directive like: LoadModule mod_ban.c In addition the proftpd package includes by default many other modules that were previously unavailble like: mod_load, mod_radius, mod_sftp and more. The module that was provided by the wrap option is replaced by the wrap2 module which is also always included. The ldap option is superseded by the proftpd-ldap package. The mysql option is superseded by the proftpd-mysql package. The pgsql option is superseded by the proftpd-postgresql package. Using proftpd-postgresql will create one binary package for each PostgreSQL version in pkgsrc. In addition the following added packages provide new functionality: - proftpd-geoip (access GeoIP details) - proftpd-memcached (mod_memcache and mod_tls_memcache) - proftpd-odbc (access any ODBC database) - proftpd-sqlite (access to sqlite3)
4 lines
229 B
Text
4 lines
229 B
Text
The ProFTPD mod_conf_ldap module can be used to store configuration
|
|
information, as would normally be found in the proftpd.conf file, in LDAP
|
|
directories, and to have proftpd consequently retrieve that configuration
|
|
information.
|