Hi, > this is a normal kernel behaviour, when *memory* is getting too full kernel > kill process to free up some.. you can change this by some /proc setting but > ive forgot where.. anyway something will still go bad if your fillup all > your memory...
That's exactly what I've been thinking of... > i think your problems caused by some process eating up all the memory... > (maybe dansguardian?) you should investigate which process grow up mad > and even swap. im sure that when you fix or disable this service you wont > have anymore this kind of issue :) dansguardian is essential service for this box... First i thought that mysql is eating up memory, but now I'm not sure of it. Can you give a hint on how to make sure which process is it ? > why not upgrading to latest tsl 2.2 kernel ?? whos 2.4.32-1tr ? Because i don't have physical access to the box, most of the time. This box is also for source based routing and a traffic shapping. And i haven't finished a problem ( day has only 24 hours and i have to be doing my fulltime job ;-) ) with ifup/ifdown scripts to be able to restart box remotely without loosing connection to the box... There is also problem with lilo, where i'm not experienced with kernel upgrades (I only did it on TSL 3.0 with grub, which went fine...) -- Jaroslav Vrbicky _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
