Date: 03 Nov 1998 18:32:11 -0600 From: stephen farrell <stephen@farrell.org> To: freebsd emulation list <emulation@FreeBSD.ORG> Subject: Sybase/FreeBSD update Message-ID: <87yapsz4ac.fsf@couatl.uchicago.edu>
next in thread | raw e-mail | index | archive | help
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. Please feel free to contact me for more information, but I don't expect to have a 3.0 box to play with again in the near future (weeks or couple of months). (Yes, I'm punting and using linux for this application... No, I'm not happy about it, but there are many reasons, not least of which is the license. I have put in my word to sybase to get a native port). -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87yapsz4ac.fsf>