Darren Reed wrote:
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.
The limit on the number of contracts has been there as long as contracts have :)
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
Looks like Menno answered this one.
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?
I don't see a reason why you couldn't raise the limit on the number of contracts inetd creates in the shipping product. The point of the control is to prevent users from denying service (contracts are cheap to create but have a fixed namespace), not to create an employment program for system tuners. The only thing I'd look out for is to make sure that if you put inetd in a new project, that the services it starts are correctly placed into their projects and aren't simply inheriting inetd's. Dave _______________________________________________ networking-discuss mailing list [email protected]
