site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jan 8, 2008, at 10:38 AM, Scott D. Davilla wrote: Don't use buffered I/O. http://www.opengroup.org/onlinepubs/007908799/xsh/setvbuf.html Or use a shared mmap(). Cheers, M _______________________________________________ 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 too am seeing a similar problem. In my case, We have one producer thread that does an fopen for write only, and several consumer threads that do fopen for read only. The consumer threads are only able to read the number of bytes in the file that existed when the fopen was called. They never see any additional data from the producer thread. These files can be very large, they are position (x,y) with electron and x-ray events streamed in realtime from networked hardware. This is a real problem with our existing code as it's design depends on the above ability. We just moved from CFM to Mach-O (yea, yea, I know). Works fine with CW and CFM (and Borland, we are cross-platform). Any suggestions for a solution? This email sent to site_archiver@lists.apple.com