In chasing down 6271923, it appears that the culprit is a new and seemingly arbitrary limit on the number of contracts that a process can create. The default would seem to be 10000.
Most normal use isn't likely to run into this situation - the problem was found when doing benchmark'ing and I just can't imagine any system supporting 9,000+ concurrent and active users... If such a scenario did exist, I'd imagine there'd be a bit of tweaking of system paramters to ensure that it was properly tuned, so I'm tempted to say "here's a workaround for your benchmarking" and leave the bug at that... The temptation is to add gob of code in inetd to set projects.max-contracts to a bigger number (lets say 100,000) or remove it but that feels ... "wrong". What I'd prefer is to be able to say is that the correct way to enable the system for this type of workload is to use projadd to create a specific inetd project and then set a project attribute in the SMF profile for inetd that points to the project. SMF would then be responsible for picking up the settings for the project in /etc/projects and applying that to the corresponding service. I've seen the question of "is it possible to link projects to SMF services" raised before, but I can't see this on the radar through the SMF pages at: www.opensolaris.org/os/community/smf Even with that, I'd not be inclinued to change the way the system ships but it would provide a proper path for someone to set the system for the expected load/task. Comments? Darren
