On 05/05/2014 05:08 PM, Cristian Rodríguez wrote:
spamd is a perl program right ? it might be expected that it does not free memory. I do not know if perl frees memory only at exit, has a garbage collector or a combination of both.
With perl there is the interpreter written in C and the script which is a text file, and then there is the data-that-is-data. I realise also that there are some plugins that are compiled C code. So what is being reported here? As far as the interpreter itself goes, I expect it will be treated like any other compiled program with a core 'working set'. That code will be shared with any other instance of perl and with the user-context-client that is spawned to process a client's mail message. That client copy will process the mail message as data-that-is-data, and if I read correctly with exit when done. Strictly speaking there only needs to be one copy of spamd the parent process. :-) HA HA. See how Apache works and wonder how many 'parent' copies you want to be able to deal with various incoming mail streams. I'm the only user of my system, and mail comes in via fetchmail+procmail and procmail invoking spamc, only one source at a time, so having only one parent process and only one child at a time (-max-children) is all I need. YMMV. -- To do anything in this world worth doing, we must not stand back shivering and thinking of the cold and danger, but jump in, and scramble through as well as we can. Sydney Smith -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org