HEX
Server: Apache/2.4.29 (Ubuntu)
System: Linux bareserver 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64
User: root (0)
PHP: 7.2.24-0ubuntu0.18.04.17
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
Upload Files
File: //usr/share/doc/proftpd-doc/misc/README.classes
Classes
-------

Classes of connections in ProFTPD are defined using <Class> sections.  An
example configuration would thus be:

  <Class foo>
    From 127.0.0.1
    From *.evil.com
  </Class>

For more information on classes, see:

  doc/howto/Classes.html

Classes can only be defined in the "server config" context, not on a <Global>
or per-<VirtualHost> basis.  This is because the class for a client is
determined as soon as the client connects to the server, before the server
determines which <VirtualHost> the client is trying to reach.  Therefore,
class definitions always apply to the entire daemon.