Possible read()/readline() bug?

[Joshua Kugler]

Mike Kent wrote:

> To followup on this:
> 
> Terry: Yes, I did in fact miss the 'buffer' parameter to open.
> Setting the buffer parameter to 0 did in fact fix the test code that I
> gave above, but oddly, did not fix my actual production code; it
> continues to get the data as first read, rather than what is currently
> on the disk.  I'm still investigating why.

What OS is your test code one? What OS is your production code on?  As
mentioned read{line} will mirror the OS's underlying stdio.

j