site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com On Feb 5, 2009, at 3:48 PM, Rand Childs wrote: Jamie -- Jamison Hope The PTR Group www.theptrgroup.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... Personally I ran up against the kernel limit of the maximum number of SYS V message queues while porting and testing a Unix application I was working on. As far as I could tell there was no easy way to increase the number of message queues without serious modification to the Darwin code. Instead I wrote a message queue library replacement, implementing the minimum features that I needed using semaphores and shared memory. AIX, Solaris and other vendors Unix implementations, and Linux can be configured to run the application without recompiling the kernel and without writing a message queue library to replace the one provided with the operating system. OS X was the odd man out. I ran into that same issue in a (somewhat legacy) distributed IPC mechanism that used a combination of sockets and message queues to allow a process to send messages to other processes without caring whether the receivers were running on the same machine or other computers on the network. But due to time constraints I didn't try to work around it; we just couldn't use our Macs as flexibly as we could the Sun and Linux boxes: they could only communicate with one other machine rather than all of them. This didn't exactly endear Mac OS X to the Linux and Solaris guys. This email sent to site_archiver@lists.apple.com