ulimit tor's memory usage

[Giorgos Pallas]

At last, I found out some messages in my /var/log/messages which solved 
the mystery that I had reported some weeks ago, about processes being 
killed for no ...apparent reason on my system:

Jan 20 23:38:11 postmortem kernel: __alloc_pages: 0-order allocation 
failed (gfp=0x1d2/0)
Jan 20 23:38:11 postmortem kernel: VM: killing process cron
Jan 20 23:38:15 postmortem kernel: __alloc_pages: 0-order allocation 
failed (gfp=0x1d2/0)
Jan 20 23:38:16 postmortem kernel: __alloc_pages: 0-order allocation 
failed (gfp=0x1d2/0)
Jan 20 23:38:16 postmortem kernel: VM: killing process tor
Jan 20 23:38:21 postmortem kernel: __alloc_pages: 0-order allocation 
failed (gfp=0x1f0/0)
Jan 20 23:38:23 postmortem kernel: __alloc_pages: 0-order allocation 
failed (gfp=0x1d2/0)
Jan 20 23:38:23 postmortem kernel: VM: killing process proftpd
Jan 20 23:38:28 postmortem kernel: __alloc_pages: 0-order allocation 
failed (gfp=0x1d2/0)
Jan 20 23:38:28 postmortem kernel: VM: killing process tor

Tor blackholes all my memory... et voila!

So, does anybody know how to use this cryptic shell command 'ulimit' so 
that I can set a limit to the amount of memory that tor can take?

Any help appreciated...

Giorgos

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5882 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.torproject.org/pipermail/tor-talk/attachments/20050121/7a2bcc78/attachment.bin>