On 02/09/11 10:48, Roland Mainz wrote:
On Wed, Feb 9, 2011 at 4:34 PM, Glenn Fowler<g...@research.att.com> wrote: the test does not exercise the original problem it doesn't even use lseek(), which is central to the problem
I know. I already acknowledged that Solaris needs to address the lseek(fd, 0, SEEK_CUR) problem, at least as a corner case. I was going beyond the original problem to the larger issue of atomicity among read(), write() and lseek() as specified in both the latest and the previous versions of the POSIX standard.
the problem can be solved by making lseek(fd, 0, SEEK_CUR) a readonly query no need for locks or semaphores in or out of the kernel
Yes, but this is just an edge-condition solution. The larger problem remains, at least on the systems tested so far. Roger _______________________________________________ ksh93-integration-discuss mailing list ksh93-integration-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss
