Section: Linux Programmer's Manual (2)
Return to Main Contents
unlink - delete a name and possibly the file it refers to
int unlink(const char *pathname);
deletes a name from the filesystem. If that name was the
last link to a file and no processes have the file open the file is
deleted and the space it was using is made available for reuse.
If the name was the last link to a file but any processes still have
the file open the file will remain in existence until the last file
descriptor referring to it is closed.
If the name referred to a symbolic link the link is removed.
If the name referred to a socket, fifo or device the name for it is
removed but processes which have the object open may continue to use
On success, zero is returned. On error, -1 is returned, and
is set appropriately.
Write access to the directory containing
is not allowed for the process's effective UID, or one of the
did not allow search permission.
- EBUSY (not on Linux)
cannot be unlinked because it is being used by the system
or another process and the implementation considers this an error.
points outside your accessible address space.
An I/O error occurred.
refers to a directory.
(This is the non-POSIX value returned by Linux since 2.1.132.)
Too many symbolic links were encountered in translating
pathname was too long.
A component in
does not exist or is a dangling symbolic link, or
Insufficient kernel memory was available.
A component used as a directory in
is not, in fact, a directory.
The system does not allow unlinking of directories,
or unlinking of directories requires privileges that the
current process doesn't have.
(This is the POSIX prescribed error return;
as noted above, Linux returns
for this case.)
- EPERM (Linux only)
The filesystem does not allow unlinking of files.
- EPERM or EACCES
The directory containing
has the sticky bit
set and the process's effective UID is neither the UID of the file to
be deleted nor that of the directory containing it, and
the process is not privileged (Linux: does not have the
refers to a file on a read-only filesystem.
SVr4, 4.3BSD, POSIX.1-2001.
Infelicities in the protocol underlying NFS can cause the unexpected
disappearance of files which are still being used.
- RETURN VALUE
- CONFORMING TO
- SEE ALSO
linux.jgfs.net manual pages