www.ProFTPD.de

SocketBindTight in effect, ignoring DefaultServer

ich bekomme im logfile immer diese meldung, ist das normal so oder muss ich da was ändern?
ich habe proftpd an eine ip adresse mittels "bind = ipadress" in der /etc/xinet.d/proftpd einstllung gebunden. funktionieren tut alles wunderbar, einzig wenn ich "DefaulServer on" auf off stelle dann geht gar nix mehr.

ist das oke so wie es ist?

The SocketBindTight directive controls how proftpd creates and binds its initial tcp listen sockets in standalone mode (see ServerType). The directive has no effect upon servers running in inetd mode, because listen sockets are not needed or created. When SocketBindTight is set to off (the default), a single listening socket is created for each port that the server must listen on, regardless of the number of IP addresses being used by <VirtualHost> configurations. This has the benefit of typically requiring a relatively small number of file descriptors for the master daemon process, even if a large number of virtual servers are configured. If SocketBindTight is set to on, a listen socket is created and bound to a specific IP address for the master server and all configured virtual servers. This allows for situations where an administrator may wish to have a particular port be used by both proftpd (on one IP address) and another daemon (on a different IP address). The drawback is that considerably more file descriptors will be required if a large number of virtual servers must be supported.