On 02/27/2012 08:10 AM, Pádraig Brady wrote: > I'm also thinking I should warn once when > the new lseek fails, but only after the fall back > write() succeeds.
I wouldn't bother. Either diagnostic should suffice, and warning about the lseek would slow the app down a bit and make it more complicated.
