Date: Sun, 2 Jun 2002 15:59:56 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc: DJGPP workers <djgpp-workers AT delorie DOT com>
Subject: Re: open(), fopen() don't check for llseek() failure
In-Reply-To: <3CFA02AD.64252B5E@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1020602155924.14325B@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Sun, 2 Jun 2002, Richard Dawe wrote:

> When open and fopen are called to open & append to a file, they don't check
> that llseek() is successful. I think they should fail, if the seek was
> unsuccessful. Should this be fixed?

When do we expect llseek to fail?

What happens with devices open in append mode?