6 Apr
2010
6 Apr
'10
11:22 a.m.
Brian A. Seklecki wrote:
Did anyone ever track this down? I'm assuming the consensus is that the kernel is SIGTERM'ing the process when it exceeds login_class(3) restrictions in login.conf(5)
Try the git 'v2.1.x' branch. There are a number of fixes there. Maybe one will help.
As for the root cause, are we talking about a memory leek introduced in a recent version or something less insidious, such as threading/process concurrency defaults that exceed defaults for non-root users?
I don't know. Try using a tool to watch the server memory over time. If it keeps growing... that would be an issue. Alan DeKok.