Date: Sun, 8 Nov 1998 15:52:46 -0600 (CST) From: sfarrell@farrell.org To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: kern/8607: maxprocsperuid and sybase segfault Message-ID: <199811082152.PAA07323@couatl.uchicago.edu>
next in thread | raw e-mail | index | archive | help
>Number: 8607 >Category: kern >Synopsis: maxprocsperuid setting causes sybase/linux segfaul >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Nov 8 14:20:00 PST 1998 >Last-Modified: >Originator: stephen farrell >Organization: >Release: FreeBSD 3.0.0-RELEASE i386 >Environment: Running Sybase/Linux under FreeBSD current. I don't believe the problem encountered is as a result of emulation. >Description: Here is my posting to emulators mailing list: This is a follow-up to my last post on the subject of problems with sybase/linux running under emulation in FreeBSD 3.0R. Here's what I've found out: The problem is triggered when maxusers is set from default 32 to 64 (sorry, no other data points). I've narrowed down the various variables that maxusers affect, and maxprocsperuid appears to be the culprit. Interestingly, even if the kernel is built with maxusers 64 (the broken value), then using sysctl to change maxprocsperuid will fix sybase's problem (I think you just need to frob it a bit--it doesn't matter what you set it to (521 is a known working value)). It might also be interesting to note that when sysctl is used to change maxprocsperuid, the value of that variable doesn't change in the kernel (at least as it's referenced in kernel_resource.c). I should point out that it appears to be a general kernel problem and not an emulation problem, as there are no references to maxusers and friends in the linux emulator. More information can be found about this by searching for sybase and freebsd (and possibly "farrell") at dejanews. Also note this URL: http://people.healthquiz.com/~sfarrell/traces/ for some ktrace output. >How-To-Repeat: Set maxusers to 64 and try to run sybase ASE on FreeBSD and see it die. Change maxprocesperuid to 521 with systctl and see it work. >Fix: No fix is know to me. Playing with sysctl and changing the maxprocesperuid does seem to be a work-around. >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811082152.PAA07323>