2004-11-03 13:51:07 +00:00
|
|
|
.\" Copyright (c) 1983, 1991 The Regents of the University of California.
|
|
|
|
.\" All rights reserved.
|
|
|
|
.\"
|
|
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
|
|
.\" modification, are permitted provided that the following conditions
|
|
|
|
.\" are met:
|
|
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
|
|
.\" 3. All advertising materials mentioning features or use of this software
|
|
|
|
.\" must display the following acknowledgement:
|
|
|
|
.\" This product includes software developed by the University of
|
|
|
|
.\" California, Berkeley and its contributors.
|
|
|
|
.\" 4. Neither the name of the University nor the names of its contributors
|
|
|
|
.\" may be used to endorse or promote products derived from this software
|
|
|
|
.\" without specific prior written permission.
|
|
|
|
.\"
|
|
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
|
|
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
.\" SUCH DAMAGE.
|
|
|
|
.\"
|
|
|
|
.\" @(#)truncate.2 6.9 (Berkeley) 3/10/91
|
|
|
|
.\"
|
|
|
|
.\" Modified 1993-07-24 by Rik Faith <faith@cs.unc.edu>
|
|
|
|
.\" Modified 1996-10-22 by Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
.\" Modified 1998-12-21 by Andries Brouwer <aeb@cwi.nl>
|
2007-09-20 06:52:22 +00:00
|
|
|
.\" Modified 2002-01-07 by Michael Kerrisk <mtk.manpages@gmail.com>
|
2004-11-03 13:51:07 +00:00
|
|
|
.\" Modified 2002-04-06 by Andries Brouwer <aeb@cwi.nl>
|
2007-09-20 06:52:22 +00:00
|
|
|
.\" Modified 2004-06-23 by Michael Kerrisk <mtk.manpages@gmail.com>
|
2004-11-03 13:51:07 +00:00
|
|
|
.\"
|
2007-07-08 12:11:40 +00:00
|
|
|
.TH TRUNCATE 2 2007-07-26 "Linux" "Linux Programmer's Manual"
|
2004-11-03 13:51:07 +00:00
|
|
|
.SH NAME
|
|
|
|
truncate, ftruncate \- truncate a file to a specified length
|
|
|
|
.SH SYNOPSIS
|
|
|
|
.B #include <unistd.h>
|
|
|
|
.br
|
|
|
|
.B #include <sys/types.h>
|
|
|
|
.sp
|
|
|
|
.BI "int truncate(const char *" path ", off_t " length );
|
|
|
|
.br
|
|
|
|
.BI "int ftruncate(int " fd ", off_t " length );
|
2007-07-08 12:11:40 +00:00
|
|
|
.sp
|
|
|
|
.in -4n
|
|
|
|
Feature Test Macro Requirements for glibc (see
|
|
|
|
.BR feature_test_macros (7)):
|
|
|
|
.in
|
|
|
|
.ad l
|
|
|
|
.sp
|
|
|
|
.BR getdtablesize ():
|
|
|
|
_BSD_SOURCE || _XOPEN_SOURCE\ >=\ 500 || _POSIX_C_SOURCE\ >=\ 200112L
|
|
|
|
.ad b
|
2004-11-03 13:51:07 +00:00
|
|
|
.SH DESCRIPTION
|
|
|
|
The
|
2005-07-19 07:15:17 +00:00
|
|
|
.BR truncate ()
|
2004-11-03 13:51:07 +00:00
|
|
|
and
|
2005-07-19 07:15:17 +00:00
|
|
|
.BR ftruncate ()
|
2004-11-03 13:51:07 +00:00
|
|
|
functions cause the regular file named by
|
|
|
|
.I path
|
|
|
|
or referenced by
|
|
|
|
.I fd
|
|
|
|
to be truncated to a size of precisely
|
|
|
|
.I length
|
|
|
|
bytes.
|
|
|
|
.LP
|
2007-04-12 22:42:49 +00:00
|
|
|
If the file previously was larger than this size, the extra data is lost.
|
2004-11-03 13:51:07 +00:00
|
|
|
If the file previously was shorter, it is extended, and
|
2006-01-13 02:09:44 +00:00
|
|
|
the extended part reads as null bytes ('\\0').
|
2004-11-03 13:51:07 +00:00
|
|
|
.LP
|
2005-07-18 17:10:25 +00:00
|
|
|
The file offset is not changed.
|
2004-11-03 13:51:07 +00:00
|
|
|
.LP
|
2007-04-12 22:42:49 +00:00
|
|
|
If the size changed, then the st_ctime and st_mtime fields
|
2005-07-19 07:15:17 +00:00
|
|
|
(respectively, time of last status change and
|
|
|
|
time of last modification; see
|
|
|
|
.BR stat (2))
|
2007-04-12 22:42:49 +00:00
|
|
|
for the file are updated,
|
2005-07-19 07:15:17 +00:00
|
|
|
and the set-user-ID and set-group-ID permission bits may be cleared.
|
2004-11-03 13:51:07 +00:00
|
|
|
.LP
|
|
|
|
With
|
2005-07-19 07:15:17 +00:00
|
|
|
.BR ftruncate (),
|
2004-11-03 13:51:07 +00:00
|
|
|
the file must be open for writing; with
|
2005-07-19 07:15:17 +00:00
|
|
|
.BR truncate (),
|
2004-11-03 13:51:07 +00:00
|
|
|
the file must be writable.
|
|
|
|
.SH "RETURN VALUE"
|
2007-04-12 22:42:49 +00:00
|
|
|
On success, zero is returned.
|
|
|
|
On error, \-1 is returned, and
|
2004-11-03 13:51:07 +00:00
|
|
|
.I errno
|
|
|
|
is set appropriately.
|
|
|
|
.SH ERRORS
|
|
|
|
For
|
2005-10-19 06:54:38 +00:00
|
|
|
.BR truncate ():
|
2004-11-03 13:51:07 +00:00
|
|
|
.TP
|
|
|
|
.B EACCES
|
|
|
|
Search permission is denied for a component of the path prefix,
|
|
|
|
or the named file is not writable by the user.
|
|
|
|
(See also
|
2007-05-26 12:41:39 +00:00
|
|
|
.BR path_resolution (7).)
|
2004-11-03 13:51:07 +00:00
|
|
|
.TP
|
|
|
|
.B EFAULT
|
|
|
|
.I Path
|
|
|
|
points outside the process's allocated address space.
|
|
|
|
.TP
|
|
|
|
.B EFBIG
|
|
|
|
The argument
|
|
|
|
.I length
|
|
|
|
is larger than the maximum file size. (XSI)
|
|
|
|
.TP
|
|
|
|
.B EINTR
|
|
|
|
A signal was caught during execution.
|
|
|
|
.TP
|
|
|
|
.B EINVAL
|
|
|
|
The argument
|
|
|
|
.I length
|
|
|
|
is negative or larger than the maximum file size.
|
|
|
|
.TP
|
|
|
|
.B EIO
|
|
|
|
An I/O error occurred updating the inode.
|
|
|
|
.TP
|
|
|
|
.B EISDIR
|
|
|
|
The named file is a directory.
|
|
|
|
.TP
|
|
|
|
.B ELOOP
|
|
|
|
Too many symbolic links were encountered in translating the pathname.
|
|
|
|
.TP
|
|
|
|
.B ENAMETOOLONG
|
|
|
|
A component of a pathname exceeded 255 characters,
|
2006-02-12 22:19:08 +00:00
|
|
|
or an entire pathname exceeded 1023 characters.
|
2004-11-03 13:51:07 +00:00
|
|
|
.TP
|
|
|
|
.B ENOENT
|
|
|
|
The named file does not exist.
|
|
|
|
.TP
|
|
|
|
.B ENOTDIR
|
|
|
|
A component of the path prefix is not a directory.
|
|
|
|
.TP
|
2006-05-09 05:28:41 +00:00
|
|
|
.B EPERM
|
|
|
|
.\" This happens for at leas MSDOS and VFAT fil systems
|
|
|
|
.\" on kernel 2.6.13
|
|
|
|
The underlying file system does not support extending
|
|
|
|
a file beyond its current size.
|
|
|
|
.TP
|
2004-11-03 13:51:07 +00:00
|
|
|
.B EROFS
|
|
|
|
The named file resides on a read-only file system.
|
|
|
|
.TP
|
|
|
|
.B ETXTBSY
|
|
|
|
The file is a pure procedure (shared text) file that is being executed.
|
|
|
|
.PP
|
|
|
|
For
|
2005-07-19 07:15:17 +00:00
|
|
|
.BR ftruncate ()
|
2004-11-03 13:51:07 +00:00
|
|
|
the same errors apply, but instead of things that can be wrong with
|
|
|
|
.IR path ,
|
|
|
|
we now have things that can be wrong with
|
|
|
|
.IR fd :
|
|
|
|
.TP
|
|
|
|
.B EBADF
|
|
|
|
The
|
|
|
|
.I fd
|
|
|
|
is not a valid descriptor.
|
|
|
|
.TP
|
|
|
|
.BR EBADF " or " EINVAL
|
|
|
|
The
|
|
|
|
.I fd
|
|
|
|
is not open for writing.
|
|
|
|
.TP
|
|
|
|
.B EINVAL
|
|
|
|
The
|
|
|
|
.I fd
|
|
|
|
does not reference a regular file.
|
|
|
|
.SH "CONFORMING TO"
|
2006-08-03 13:57:17 +00:00
|
|
|
4.4BSD, SVr4, POSIX.1-2001 (these calls first appeared in 4.2BSD).
|
|
|
|
.\" POSIX.1-1996 has
|
|
|
|
.\" .BR ftruncate ().
|
|
|
|
.\" POSIX.1-2001 also has
|
|
|
|
.\" .BR truncate (),
|
|
|
|
.\" as an XSI extension.
|
|
|
|
.\" .LP
|
|
|
|
.\" SVr4 documents additional
|
|
|
|
.\" .BR truncate ()
|
|
|
|
.\" error conditions EMFILE, EMULTIHP, ENFILE, ENOLINK. SVr4 documents for
|
|
|
|
.\" .BR ftruncate ()
|
|
|
|
.\" an additional EAGAIN error condition.
|
2004-11-03 13:51:07 +00:00
|
|
|
.SH NOTES
|
|
|
|
The above description is for XSI-compliant systems.
|
|
|
|
For non-XSI-compliant systems, the POSIX standard allows
|
2007-06-08 09:56:56 +00:00
|
|
|
two behaviors for
|
2005-07-19 07:15:17 +00:00
|
|
|
.BR ftruncate ()
|
2004-11-03 13:51:07 +00:00
|
|
|
when
|
|
|
|
.I length
|
|
|
|
exceeds the file length
|
|
|
|
(note that
|
2005-07-19 07:15:17 +00:00
|
|
|
.BR truncate ()
|
2004-11-03 13:51:07 +00:00
|
|
|
is not specified at all in such an environment):
|
|
|
|
either returning an error, or extending the file.
|
2007-04-12 22:42:49 +00:00
|
|
|
Like most Unix implementations, Linux follows the XSI requirement
|
|
|
|
when dealing with native file systems.
|
2006-05-09 05:28:41 +00:00
|
|
|
However, some non-native file systems do not permit
|
|
|
|
.BR truncate ()
|
2007-04-12 22:42:49 +00:00
|
|
|
and
|
2006-05-09 05:28:41 +00:00
|
|
|
.BR ftruncate ()
|
|
|
|
to be used to extend a file beyond its current length:
|
|
|
|
a notable example on Linux is VFAT.
|
2004-11-03 13:51:07 +00:00
|
|
|
.\" At the very least: OSF/1, Solaris 7, and FreeBSD conform, mtk, Jan 2002
|
|
|
|
.SH "SEE ALSO"
|
|
|
|
.BR open (2),
|
2007-05-26 12:41:39 +00:00
|
|
|
.BR stat (2),
|
|
|
|
.BR path_resolution (7)
|