limits of maxproc on SUN E450 with FreeBSD 5.3 Beta7
DanGer
danger at wilbury.sk
Mon Oct 18 12:38:03 PDT 2004
Hello Doug,
Monday, October 18, 2004, 7:57:53 PM, you wrote:
> On Fri, 15 Oct 2004, Borghesi Guilhem wrote:
>> I've installed a FreeBSD 5.3 Beta7 on a Sun sparc64 Enterprise 450.
>> This machine is a Terminal and application server for University
>> students. They are using this server for system programming (C for
>> example) and they often use the command "fork ()" into "while" loops.
> We call that a "forkbomb."
>> This kind of bad programming is quite frequent at the university, and
>> that's the reason why I'm trying to limit the number of maxproc per
>> user. I've limited the maxproc with the /etc/login.conf file at 100 and
>> make a "cap_mkdb /etc/login.conf", but it doesn't work. Worst, when the
I'm not very sure about this, but, did you turned on in
/etc/ssh/sshd_config option UseLogin? like
UseLogin yes
>> number of processes reach the limit, the server crash with the console
>> message :"panic: trap: data access error".
>>
>> I've tried to put "unlimited" in place of "100", but it does'nt change
>> anything because the system has an implicit limit for users
>> (kern.maxprocperuid: 5547).
> It should change the soft limit on maxproc, and the kernel sysctl is the
> hard limit. The user can change the limit up to the hard limit, but it
> will start out at the soft limit.
> What as the exact change you made to login.conf? Did you test it after
> logging out and logging back in? How were you logging in?
> Obviously, the panic isn't such a great thing. Did you get a crashdump?
--
Best regards
+----------==/\/\==----------+
| DanGer <danger at wilbury.sk> |
| DanGer at IRCnet ICQ261701668 |
| http://danger.homeunix.org |
+----------==\/\/==----------+
More information about the freebsd-current
mailing list