Hallo allerseits.
Ich habe ein Problem: Und zwar biete ich eine Mirror an und nach ca. 60-180 minuten hägt sich proftpd auf. Jetzt ist die frage warum.
Der Mirror lief mal Problemlos aber dann gingen die Probleme los und ich weiß nicht warum

Ich poste mal meine Config und hoffe ihr könnt mir helfen:
# debugLevel 1
#Serverlog /var/proftpd.debug.log
#
# /etc/proftpd.conf -- This is a basic ProFTPD configuration file.
# To really apply changes reload proftpd after modifications.
#
ServerName "OTR Mirror"
ServerType standalone
DeferWelcome off
MultilineRFC2228 on
DefaultServer on
ShowSymlinks on
TimeoutNoTransfer 30
TimeoutStalled 600
TimeoutIdle 30
MaxClientsPerHost 1 "Damit alle Benutzer einen maximalen Speed haben ist der Download von 2 oder mehr Dateien GLEICHZEITIG nicht erlaubt!"
DisplayLogin welcome.msg
DisplayFirstChdir .message
ListOptions "-l"
DenyFilter \*.*/
UseReverseDNS off
IdentLookups off
# Uncomment this if you are using NIS or LDAP to retrieve passwords:
#PersistentPasswd off
# Uncomment this if you would use TLS module:
#TLSEngine on
# Uncomment this if you would use quota module:
#Quotas on
# Uncomment this if you would use ratio module:
#Ratios on
# Port 21 is the standard FTP port.
Port 21
# To prevent DoS attacks, set the maximum number of child processes
# to 30. If you need to allow more than 30 concurrent connections
# at once, simply increase this value. Note that this ONLY works
# in standalone mode, in inetd mode you should use an inetd server
# that allows you to limit maximum number of processes per service
# (such as xinetd)
# that allows you to limit maximum number of processes per service
# (such as xinetd)
MaxInstances 100
# Set the user and group that the server normally runs at.
User nobody
Group nogroup
# Umask 022 is a good standard umask to prevent new files and dirs
# (second parm) from being group and world writable.
Umask 022 022
# Normally, we want files to be overwriteable.
AllowOverwrite on
# Delay engine reduces impact of the so-called Timing Attack described in
#
http://security.lss.hr/index.php?page=details&ID=LSS-2004-10-02# It is on by default.
#DelayEngine off
# A basic anonymous configuration, no upload directories.
defaultroot /var/www/download
<Anonymous /var/www/download>
User ftp
Group nogroup
# We want clients to be able to login with "anonymous" as well as "ftp"
UserAlias anonymous ftp
# Cosmetic changes, all files belongs to ftp user
DirFakeUser on ftp
DirFakeGroup on ftp
TransferRate RETR 200
RequireValidShell off
# Limit the maximum number of anonymous logins
MaxClients 100
# We want 'welcome.msg' displayed at login, and '.message' displayed
# in each newly chdired directory.
DisplayLogin welcome.msg
DisplayFirstChdir .message
# Limit WRITE everywhere in the anonymous chroot
<Directory *>
<Limit WRITE>
DenyAll
</Limit>
<Limit LIST>
DenyAll
</Limit>
</Directory>
# # Uncomment this if you're brave.
# # <Directory incoming>
# # # Umask 022 is a good standard umask to prevent new files and dirs
# # # (second parm) from being group and world writable.
# # # Umask 022 is a good standard umask to prevent new files and dirs
# # # (second parm) from being group and world writable.
# # Umask 022 022
# # <Limit READ WRITE>
# # DenyAll
# # </Limit>
# # <Limit STOR>
# # AllowAll
# # </Limit>
# # </Directory>
#
</Anonymous>
Ich hoffe ihr könnt mir helfen
Grüße
Strupp