lseek - move the read/write file offset
off_t lseek(int fildes, off_t offset, int whence);
The lseek() function shall set the file offset for the open file description associated with the file descriptor fildes, as follows:
If whence is SEEK_SET, the file offset shall be set to offset bytes.
If whence is SEEK_CUR, the file offset shall be set to its current location plus offset.
If whence is SEEK_END, the file offset shall be set to the size of the file plus offset.
The symbolic constants SEEK_SET, SEEK_CUR, and SEEK_END are defined in <unistd.h>.
The behavior of lseek() on devices which are incapable of seeking is implementation-defined. The value of the file offset associated with such a device is undefined.
The lseek() function shall allow the file offset to be set beyond the end of the existing data in the file. If data is later written at this point, subsequent reads of data in the gap shall return bytes with the value 0 until data is actually written into the gap.
The lseek() function shall not, by itself, extend the size of a file.
[SHM] If fildes refers to a shared memory object, the result of the lseek() function is unspecified.
[TYM] If fildes refers to a typed memory object, the result of the lseek() function is unspecified.
Upon successful completion, the resulting offset, as measured in bytes from the beginning of the file, shall be returned. Otherwise, (off_t)-1 shall be returned, errno shall be set to indicate the error, and the file offset shall remain unchanged.
The lseek() function shall fail if:
- The fildes argument is not an open file descriptor.
- The whence argument is not a proper value, or the resulting file offset would be negative for a regular file, block special file, or directory.
- The resulting file offset would be a value which cannot be represented correctly in an object of type off_t.
- The fildes argument is associated with a pipe, FIFO, or socket.
The ISO C standard includes the functions fgetpos() and fsetpos(), which work on very large files by use of a special positioning type.
Although lseek() may position the file offset beyond the end of the file, this function does not itself extend the size of the file. While the only function in POSIX.1-2008 that may directly extend the size of the file is write(), truncate(), and ftruncate(), several functions originally derived from the ISO C standard, such as fwrite(), fprintf(), and so on, may do so (by causing calls on write()).
An invalid file offset that would cause [EINVAL] to be returned may be both implementation-defined and device-dependent (for example, memory may have few invalid values). A negative file offset may be valid for some devices in some implementations.
The POSIX.1-1990 standard did not specifically prohibit lseek() from returning a negative offset. Therefore, an application was required to clear errno prior to the call and check errno upon return to determine whether a return value of ( off_t)-1 is a negative offset or an indication of an error condition. The standard developers did not wish to require this action on the part of a conforming application, and chose to require that errno be set to [EINVAL] when the resulting file offset would be negative for a regular file, block special file, or directory.
XBD <sys/types.h> , <unistd.h>
First released in Issue 1. Derived from Issue 1 of the SVID.
The DESCRIPTION is updated for alignment with the POSIX Realtime Extension.
Large File Summit extensions are added.
In the SYNOPSIS, the optional include of the <sys/types.h> header is removed.
The following new requirements on POSIX implementations derive from alignment with the Single UNIX Specification:
The requirement to include <sys/types.h> has been removed. Although <sys/types.h> was required for conforming implementations of previous POSIX specifications, it was not required for UNIX applications.
The [EOVERFLOW] error condition is added. This change is to support large files.
An additional [ESPIPE] error condition is added for sockets.
The DESCRIPTION is updated for alignment with IEEE Std 1003.1j-2000 by specifying that lseek() results are unspecified for typed memory objects.
return to top of page