No. It will not solve any problem (ignoring that there was no problem in the first place).
//art Pete Vickers <[email protected]> writes: > alternatively you could run/spawn ftpd from inetd, which will > presumably mean that all the resources will be 'returned' as soon as > the connection closes. However significant performance hit on a busy > ftp server. > > /Pete > > > > On 17. nov.. 2009, at 10.25, Artur Grabowski wrote: > >> "MK" <[email protected]> writes: >> >>> 1. Is it normal that memory is not freed after I kill ftpd daemon? >> >> yes. because the ftp daemon didn't allocate it. >> >>> 2. Is it normal ftpd can take about 800MB of real memory while >>> serving >>> GET requests? (only 1 client is able to consume that portion of >>> memory) >> >> If you serve 800MB of file data through ftpd then yes. >> >>> 3. Is it normal that this memory seems to be lost from the system? >> >> yes. The keyword here is "seems". >> >> The memory is used for caching the file contents in case you decide to >> read those files again. It's reused for more useful things when it's >> needed. >> >> //art >> > > Pete Vickers > > [email protected] | +47 48 17 91 00 > > SystemNet AS
