31 Mar
2006
31 Mar
'06
18:46
On Fri, 2006-03-31 at 08:00 -0500, Jerry Feldman wrote:
I agree pretty much with your statement. The OP was opening a file for writing, then performing a fork where both the parent and child were writing to the file simultaneously. I took the program that the OP submitted and ran it on SuSE 10 (32-bit), and ran it on RHEL 4 (64-bit IA64). Both had the same successful result without the overwriting that the OP experienced. (In both cases, 2.6 kernel).
Are you implying that the file location pointer is shared across a dup() call in these systems?