comparison README @ 72:84c7edc1a619

Add note about Perl memory allocator behaviour.
author Matti Hamalainen <ccr@tnsp.org>
date Thu, 27 Aug 2009 00:28:43 +0300
parents adb4795f451e
children 5d722da1392b
comparison
equal deleted inserted replaced
71:cc6d710886e5 72:84c7edc1a619
31 - Perl 5.8 or later 31 - Perl 5.8 or later
32 - Date::Parse (libtimedate-perl) 32 - Date::Parse (libtimedate-perl)
33 - Net::IP (libnet-ip-perl) 33 - Net::IP (libnet-ip-perl)
34 - Net::DNS (libnet-dns-perl) 34 - Net::DNS (libnet-dns-perl)
35 - LWP::UserAgent (libwww-perl) 35 - LWP::UserAgent (libwww-perl)
36
37
38 Memory requirement considerations
39 =================================
40 Because Maltfilter is written in Perl, it (or rather the Perl interpreter
41 it is running under) tends not to free any allocated memory. This is NOT
42 a memory leak per se, but a feature of Perl's memory allocator. Currently
43 allocated memory is simply reused for other structures when needed,
44 thus making the VIRT consumption periodically rise.
45
46 However, there may be some situations (none that I have experienced myself
47 as of yet, but as usual anything is possible) where Maltfilter's memory
48 consumption rises to unbearable level. In high-volume servers it may be
49 useful to periodically restart (as in complete restart, not reload via HUP)
50 the daemon to free the memory.
36 51
37 52
38 Installation 53 Installation
39 ============ 54 ============
40 Copy maltfilter script to /usr/sbin and set permissions 55 Copy maltfilter script to /usr/sbin and set permissions