From 7e0f021a9aec35fd8e6725e87e3313b101d26f5e Mon Sep 17 00:00:00 2001 From: Tobias Klauser Date: Sun, 27 Jan 2008 11:37:44 +0100 Subject: Initial import (2.0.2-6) --- reference/C/MAN/unlink.htm | 168 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 168 insertions(+) create mode 100644 reference/C/MAN/unlink.htm (limited to 'reference/C/MAN/unlink.htm') diff --git a/reference/C/MAN/unlink.htm b/reference/C/MAN/unlink.htm new file mode 100644 index 0000000..79ab69d --- /dev/null +++ b/reference/C/MAN/unlink.htm @@ -0,0 +1,168 @@ +unlink + +
+
+
+
+
+

UNLINK(2) Linux Programmer's Manual UNLINK(2) +

+ +

NAME +

unlink - delete a name and possibly the file it refers to + +

SYNOPSIS +

#include <unistd.h> + + int unlink(const char *pathname); + +

DESCRIPTION +

unlink 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 it. + +

RETURN VALUE +

On success, zero is returned. On error, -1 is returned, + and errno is set appropriately. + +

ERRORS +

EFAULT pathname points outside your accessible address + space. + + EACCES Write access to the directory containing pathname + is not allowed for the process's effective uid, or + one of the directories in pathname did not allow + search (execute) permission. + + EPERM The directory containing pathname has the sticky- + bit (S_ISVTX) set and the process's effective uid + is neither the uid of the file to be deleted nor + that of the directory containing it. + + ENAMETOOLONG + pathname was too long. + + ENOENT A directory component in pathname does not exist + or is a dangling symbolic link. + + ENOTDIR A component used as a directory in pathname is + not, in fact, a directory. + + EISDIR pathname refers to a directory. + + + + +

Linux 24 July 1993 1 +

+ + + + +

UNLINK(2) Linux Programmer's Manual UNLINK(2) +

+ + ENOMEM Insufficient kernel memory was available. + + EROFS pathname refers to a file on a read-only filesys- + tem. + +

CONFORMING TO +

SVID, AT&T, POSIX, X/OPEN, BSD 4.3 + +

BUGS +

Infelicities in the protocol underlying NFS can cause the + unexpected disappearance of files which are still being + used. + +
+
+

SEE ALSO +

+link, +rename, +open, +rmdir, +mknod, +remove, +rm, +

+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

Linux 24 July 1993 2 +

+ +
+

+


+

+

+ + + + +
+Top + +Master Index + +Keywords + +Functions +
+
+

+


+ +This manual page was brought to you by mjl_man V-2.0 -- cgit v1.2.3-54-g00ecf ame='ignorews' onchange='this.form.submit();'>mode:
Diffstat (limited to 'sound/soc/codecs/wm8997.c')