From: Oli K. <du...@nc...> - 2015-02-04 21:02:22
|
Thanks for the clarification. Filed a bug at http://bugs.proftpd.org/show_bug.cgi?id=4152 Cheers, -ok On 04 Feb 2015, at 19:31, TJ Saunders <tj...@ca...> wrote: > >> The customer thinks that the performance of the server is affected (i.e. >> normal clients fail to establish a session) when being scanned > > This is not the case; the performance of proftpd is not affected by > connections such as the above. > >> 1: As this is a fatal error, our logs are filled with it - we seem to be scanned very often recently. >> Is there a way to prevent this from being logged at all? > > This particular error is indeed NOT fatal. It happens to fall into the > general error handling case at that point in the proftpd code. > > Could you file a bug report, on bugs.proftpd.org, to address this? It > will be relatively easy to handle in a much better manner (i.e. by > ignoring that particular error, and possibly others in a similar vein). > |