You can delete a file with
Deletion actually deletes a file name. If this is the file's only name, then the file is deleted as well. If the file has other remaining names (see Hard Links), it remains accessible under those names.
unlinkfunction deletes the file name filename. If this is a file's sole name, the file itself is also deleted. (Actually, if any process has the file open when this happens, deletion is postponed until all processes have closed the file.)
This function returns
0on successful completion, and
-1on error. In addition to the usual file name errors (see File Name Errors), the following
errnoerror conditions are defined for this function:
- Write permission is denied for the directory from which the file is to be removed, or the directory has the sticky bit set and you do not own the file.
- This error indicates that the file is being used by the system in such a way that it can't be unlinked. For example, you might see this error if the file name specifies the root directory or a mount point for a file system.
- The file name to be deleted doesn't exist.
- On some systems
unlinkcannot be used to delete the name of a directory, or at least can only be used this way by a privileged user. To avoid such problems, use
rmdirto delete directories. (On GNU/Linux and GNU/Hurd systems
unlinkcan never delete the name of a directory.)
- The directory containing the file name to be deleted is on a read-only file system and can't be modified.
In most other respects,
unlink. There are two additional
errnoerror conditions defined for
- The directory to be deleted is not empty.
These two error codes are synonymous; some systems use one, and some use the other. GNU/Linux and GNU/Hurd systems always use