Manpage of UNLINK
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 (execute) permission.
- 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.
- EPERM (Linux only)
The filesystem does not allow unlinking of files.
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.)
refers to a directory.
(This is the non-POSIX value returned by Linux since 2.1.132.)
- 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.
pathname was too long.
A component in
does not exist or is a dangling symbolic link, or
A component used as a directory in
is not, in fact, a directory.
Insufficient kernel memory was available.
refers to a file on a read-only filesystem.
Too many symbolic links were encountered in translating
An I/O error occurred.
SVr4, SVID, POSIX, X/OPEN, 4.3BSD. SVr4 documents additional error
conditions EINTR, EMULTIHOP, ETXTBSY, ENOLINK.
Infelicities in the protocol underlying NFS can cause the unexpected
disappearance of files which are still being used.
- RETURN VALUE
- CONFORMING TO
- SEE ALSO