Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!ux1.cso.uiuc.edu!ux1.cso.uiuc.edu!randy
From: randy@ux1.cso.uiuc.edu
Newsgroups: comp.sys.next
Subject: Greedy lookupd(8)
Message-ID: <18600003@ux1.cso.uiuc.edu>
Date: 16 Jan 90 01:40:24 GMT
Lines: 13
Nf-ID: #N:ux1.cso.uiuc.edu:18600003:000:763
Nf-From: ux1.cso.uiuc.edu!randy    Jan 15 19:28:00 1990


We've had a problem with lookupd for a while now. I don't know when it
started, but at one point lookupd just acquired an insatiable appetite
for memory.  The virtual memory allocated for it (as indicated by ps)
just grows (roughly linearly) until our file system fills up (660 Meg
HD)! I would say the rate of growth is on the order of 20 Meg/day.
Needless to say, we periodically have to reboot it when we begin
running short of space (about once every two days or three days now).
Of course, this is the swapfile that's growing - as lookupd demands
more and more virtual memory. I don't have a single solitary lead as to
how to fix this (or even where to go for info - as lookupd is NeXT
specific). AAAAAAH!  Please, can someone help us? Our NeXT is
crippled!