Path: utzoo!mnetor!uunet!husc6!mit-eddie!uw-beaver!cornell!rochester!udel!burdvax!sdcrdcf!trwrb!desint!geoff
From: geoff@desint.UUCP (Geoff Kuenning)
Newsgroups: comp.bugs.sys5
Subject: Re: Possible "lseek()" bug
Message-ID: <1655@desint.UUCP>
Date: 16 Dec 87 08:18:56 GMT
References: <716@hsi.UUCP> <36212@sun.uucp> <978@sauron.Columbia.NCR.COM>
Reply-To: geoff@desint.UUCP (Geoff Kuenning)
Organization: Interrupt Technology Corp., Manhattan Beach, CA
Lines: 17
Keywords: lseek

In article <978@sauron.Columbia.NCR.COM> campbell@sauron.Columbia.NCR.COM (Mark Campbell) writes:

> It seems that the V.3.1 "lseek()" does not return a negative value when
> asserted with a negative offset.  There is some talk in the manual concerning
> this behavior with remote file systems; however, this problem appears when
> accessed local file descriptors too.
> 
> Is there something I'm missing?

That's what it's supposed to do.  From the manual page for lseek(2):

    RETURN VALUE
	Upon successful completion, a non-negative integer indicating
	the file pointer value is returned.  Otherwise, a value of -1
	is returned and errno is set to indicate the error.
-- 
	Geoff Kuenning   geoff@ITcorp.com   {uunet,trwrb}!desint!geoff