From wd@uebemc.siemens.de Thu Jun 9 13:03:01 EDT 1994 vasco@bvl.pt (Antonio Vasconcelos) writes: >: not specify exactly how many users you can sign onto a Solaris 2.x host. The >: 'maxuser' variable is used to size various kernel tables... >Such as ??? >I'm still looking for the name of some basic parameters that I >think may be defined in /etc/system. Specially the maximum number >of child processes by user id and the maximum number of open files >(system wide and by user id). Anyone know this ones ??? Run "crash" and have a look at the output of the "var" command; there is a structure "v" in your kernel that holds all the tunable parameters. The definition is in /usr/include/sys/var.h And there is another structure "rlimits" which lists the ressour- ce limits; see the definition in /usr/include/sys/resource.h If you have more (or more detailed) questions feel free to ask [email preferred]. BTW: I do not know of a "clean" way to change these values yet. It seems to be impossible to set a field of a structure using /etc/system. All I can do so far is patching the kerning with adb. I guess this is what Sun calls "flexibility" :-( >Anyone know why Sun have choose to *hide* this info ? >I had some hope when I found something called 'Tuning Kernel >Parameters' in the AnswerBook... Ah! Vain hopes there are some info >there, but not what I need. We all have the same kind of problems... :-( Sun, are you listening??? Wolfgang Office: (+49)-89-722-41782 wd@uebemc.siemens.de Private: (+49)-89-952275 wd@denx.muc.de "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn From vasco@bvl.pt Thu Jun 9 13:03:11 EDT 1994 casper@fwi.uva.nl (Casper H.S. Dik) writes: : The maximum number of processes per user is maxuprc. Thanks, thanks, thanks... : I'm not sure there's still a hard limit on open files, : we never run into it. (Perhaps because maxusers now scales : automatically with the amount of memory you have so under : configuring a machine (booting a maxusers=4 kernel on : a file/compute server) is now more difficult. I don't think so, the info get with sysdef -i is the same for the default maxusers (how many ???) and for the maxusers=200 that I have now: (...) * Process Resource Limit Tunables (Current:Maximum) * Infinity:Infinity cpu time Infinity:Infinity file size 7ffff000:7ffff000 heap size 800000:7ffff000 stack size Infinity:Infinity core file size 40: 400 file descriptors <------------- Infinity:Infinity mapped memory (...) : >Anyone know why Sun have choose to *hide* this info ? : >I had some hope when I found something called 'Tuning Kernel : >Parameters' in the AnswerBook... Ah! Vain hopes there are some info : >there, but not what I need. : >Hell, even Unisys's docs for the SVR2 Kernel (3 pages) were more : >usefull!!! : : In Solaris 2.3 there is more info in the Tuning Kernel Parameters : section. That's the place I was talking about... Are there other places ? : I don't think Sun is really hiding info, they simply haven't gotten : around to documenting all of it. The kernel still sees many, many : changes every release and keeping the documentation in sync with that : is a daunting task. That's sloppy managnement... I hope there is only one person working on the kernel... 8-) : Some of the knobs in the kernel are not documented on purpose, : I think. Just as people start punching random button and turing : random knobs when they can't get a machine to work, they'll start : to switch on/off all kinds of stuff in the kernel giving only : half a chance. I understand that need but I dislike it, in fact I don't like any situation that can only be solved by an SE just because they have access to information that is not supplied to costumers. That's the kind of things that companies like Commodore do (did) with the Amiga. And I don't belive that 'maxuprc' is one of that knobs... -- regards, Antonio Vasconcelos @ The Lisbon $tock Exchange (BVL) require 'std/disclaimer.ph' <<< It's never as easy as you think >>> From vasco@bvl.pt Thu Jun 9 13:03:50 EDT 1994 casper@fwi.uva.nl (Casper H.S. Dik) writes: : It was never documented, perhaps because it really never worked : right in 4.1.x w/o editing param.c. (There's an #undef followed by : a #define, so putting it in the config file is of no use). Well, it works in Solaris 2.3, I tryed the canonical runaway fork program: "while(1) fork()" and that user did stop at the correct number of PIDs. Of course that I have to do a reboot to stop that processes, but the important is that a single user can't hung the system anymore. : The default value for maxuprc is all processes (-2), which is fine for : desktop machines but not for large ``mainframe'' type machines. : And multi-user student machines. (Runaway forks are very common) That's our case, we have a SC2000 and we are expected to have more than 200 users (fortunatlly they are not students 8-) -- regards, Antonio Vasconcelos @ The Lisbon $tock Exchange (BVL) require 'std/disclaimer.ph' <<< That's not a bug, that's a feature >>>