site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) John Francini wrote: John Francini On Jun 21, 2005, at 0:42, Tron Thomas wrote: What determines how much space is available for creating semaphores? _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/francini%40mac.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... I'm not sure if any semaphores are leaked or not. I asked the developer who works in the area that uses semaphores, and he said that most of the semaphore created by his code should exist for pretty much the life of the program. Other people may be creating semaphores that are not being deleted. I have added some logging to see if any semaphores are being deleted. So, far I haven't seen any evidence of semaphore deletion. What tools and technique can I use to determine how many semaphores are in use, and if there are any possible semaphore leaks? The semaphore space is controlled by the kern.sysv.sem* set of sysctl(8) values. The question, though, is how many semaphores is the program using, and is it "leaking" semaphores? The default value appears to be 87381 in Panther. At work we have a program running on Mac OS X that routinely calls sem_open to created named semaphores. After the program has run for a while the sem_open command will fail with the result ENOSPC and the corresponding error string "No space left on device". This email sent to francini@mac.com This email sent to site_archiver@lists.apple.com