1.\" Copyright (c) 1980, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. Neither the name of the University nor the names of its contributors 13.\" may be used to endorse or promote products derived from this software 14.\" without specific prior written permission. 15.\" 16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 19.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 26.\" SUCH DAMAGE. 27.\" 28.\" @(#)lseek.2 8.3 (Berkeley) 4/19/94 29.\" $FreeBSD$ 30.\" 31.Dd July 13, 2020 32.Dt LSEEK 2 33.Os 34.Sh NAME 35.Nm lseek 36.Nd reposition read/write file offset 37.Sh LIBRARY 38.Lb libc 39.Sh SYNOPSIS 40.In unistd.h 41.Ft off_t 42.Fn lseek "int fildes" "off_t offset" "int whence" 43.Sh DESCRIPTION 44The 45.Fn lseek 46system call repositions the offset of the file descriptor 47.Fa fildes 48to the 49argument 50.Fa offset 51according to the directive 52.Fa whence . 53The argument 54.Fa fildes 55must be an open 56file descriptor. 57The 58.Fn lseek 59system call 60repositions the file position pointer associated with the file 61descriptor 62.Fa fildes 63as follows: 64.Bl -item -offset indent 65.It 66If 67.Fa whence 68is 69.Dv SEEK_SET , 70the offset is set to 71.Fa offset 72bytes. 73.It 74If 75.Fa whence 76is 77.Dv SEEK_CUR , 78the offset is set to its current location plus 79.Fa offset 80bytes. 81.It 82If 83.Fa whence 84is 85.Dv SEEK_END , 86the offset is set to the size of the 87file plus 88.Fa offset 89bytes. 90.It 91If 92.Fa whence 93is 94.Dv SEEK_HOLE , 95the offset is set to the start of the next hole greater than or equal 96to the supplied 97.Fa offset . 98The definition of a hole is provided below. 99.It 100If 101.Fa whence 102is 103.Dv SEEK_DATA , 104the offset is set to the start of the next non-hole file region greater 105than or equal to the supplied 106.Fa offset . 107.El 108.Pp 109The 110.Fn lseek 111system call allows the file offset to be set beyond the end 112of the existing end-of-file of the file. 113If data is later written 114at this point, subsequent reads of the data in the gap return 115bytes of zeros (until data is actually written into the gap). 116However, the 117.Fn lseek 118system call does not, by itself, extend the size of a file. 119.Pp 120A 121.Qq hole 122is defined as a contiguous range of bytes in a file, all having the value of 123zero, but not all zeros in a file are guaranteed to be represented as holes 124returned with 125.Dv SEEK_HOLE . 126File systems are allowed to expose ranges of zeros with 127.Dv SEEK_HOLE , 128but not required to. 129Applications can use 130.Dv SEEK_HOLE 131to optimise their behavior for ranges of zeros, but must not depend on it to 132find all such ranges in a file. 133Each file is presented as having a zero-size virtual hole at the very 134end of the file. 135The existence of a hole at the end of every data region allows for easy 136programming and also provides compatibility to the original implementation 137in Solaris. 138It also causes the current file size (i.e., end-of-file offset) to be returned 139to indicate that there are no more holes past the supplied 140.Fa offset . 141Applications should use 142.Fn fpathconf _PC_MIN_HOLE_SIZE 143or 144.Fn pathconf _PC_MIN_HOLE_SIZE 145to determine if a file system supports 146.Dv SEEK_HOLE . 147See 148.Xr pathconf 2 . 149.Pp 150For file systems that do not supply information about holes, the file will be 151represented as one entire data region. 152.Sh RETURN VALUES 153Upon successful completion, 154.Fn lseek 155returns the resulting offset location as measured in bytes from the 156beginning of the file. 157Otherwise, 158a value of -1 is returned and 159.Va errno 160is set to indicate 161the error. 162.Sh ERRORS 163The 164.Fn lseek 165system call 166will fail and the file position pointer will remain unchanged if: 167.Bl -tag -width Er 168.It Bq Er EBADF 169The 170.Fa fildes 171argument 172is not an open file descriptor. 173.It Bq Er EINVAL 174The 175.Fa whence 176argument 177is not a proper value 178or the resulting file offset would 179be negative for a non-character special file. 180.It Bq Er ENXIO 181For 182.Dv SEEK_DATA , 183there are no more data regions past the supplied offset. 184Due to existence of the hole at the end of the file, for 185.Dv SEEK_HOLE 186this error is only returned when the 187.Fa offset 188already points to the end-of-file position. 189.It Bq Er EOVERFLOW 190The resulting file offset would be a value which cannot be represented 191correctly in an object of type 192.Fa off_t . 193.It Bq Er ESPIPE 194The 195.Fa fildes 196argument 197is associated with a pipe, socket, or FIFO. 198.El 199.Sh SEE ALSO 200.Xr dup 2 , 201.Xr open 2 , 202.Xr pathconf 2 203.Sh STANDARDS 204The 205.Fn lseek 206system call is expected to conform to 207.St -p1003.1-2008 . 208.Pp 209The 210.Dv SEEK_HOLE 211and 212.Dv SEEK_DATA 213directives, along with the 214.Er ENXIO 215error, are extensions to that specification. 216.Sh HISTORY 217The 218.Fn lseek 219function appeared in 220.At v7 . 221.Sh BUGS 222If the 223.Fn lseek 224system call is operating on a device which is incapable of seeking, 225it will request the seek operation and return successfully, 226even though no seek was performed. 227Because the 228.Ar offset 229argument will be stored unconditionally in the file descriptor of that device, 230there is no way to confirm if the seek operation succeeded or not 231(e.g. using the 232.Fn ftell 233function). 234Device types which are known to be incapable of seeking include 235tape drives. 236.Pp 237The 238.Fn lseek 239system call will not detect whether media are present in changeable 240media devices such as DVD or Blu-ray devices. 241A requested seek operation will therefore return sucessfully when no 242medium is present. 243.Pp 244This document's use of 245.Fa whence 246is incorrect English, but is maintained for historical reasons. 247