INND~stopped a brief time
Russ Allbery
rra at stanford.edu
Wed Feb 7 04:34:13 UTC 2001
fukuda shinichi <fukuda at alles.ad.jp> writes:
> I found the cause this error ・・・
> → 16744 news 1 46 4 1060M 702M sleep 0:22 0.00% nnrpd
> This HUGE nnrpd ate system's memory and swap away.
Yup, that'll do it.
> After sent KILL signal to this HUGE nnrpd, system run normal
> again.(don't tell anyone)
> I believe firmly This nnrpd was the origin.
> So, Can i restrict to grow nnrpd's SIZE by inn configuration ?
I don't know of a good way if you're running nnrpd out of innd. You can
alternately run innd on a separate port (usually 433) and start nnrpd via
inetd or tcpserver, in which case one could wrap it with a program like
djb's softlimit to set up datasize limits for it.
--
Russ Allbery (rra at stanford.edu) <http://www.eyrie.org/~eagle/>
More information about the inn-workers
mailing list