LinuxReviws.org --get your your Linux knowledge
> Linux Reviews > Manual Pages (man) >

unlink

call the unlink function to remove the specified file


  1. unlink.1.man
  2. unlink.2.man


1. unlink.1.man

Manpage of UNLINK

UNLINK

Section: User Commands (1)
Updated: October 2011
Index Return to Main Contents
 

NAME

unlink - call the unlink function to remove the specified file  

SYNOPSIS

unlink FILE
unlink OPTION  

DESCRIPTION

Call the unlink function to remove the specified FILE.

--help
display this help and exit
--version
output version information and exit
 

AUTHOR

Written by Michael Stone.  

REPORTING BUGS

Report unlink bugs to bug-coreutils@gnu.org
GNU coreutils home page: <http://www.gnu.org/software/coreutils/>
General help using GNU software: <http://www.gnu.org/gethelp/>
Report unlink translation bugs to <http://translationproject.org/team/>  

COPYRIGHT

Copyright © 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl>.
This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.  

SEE ALSO

unlink(2)

The full documentation for unlink is maintained as a Texinfo manual. If the info and unlink programs are properly installed at your site, the command

info coreutils aqunlink invocationaq

should give you access to the complete manual.


 

Index

NAME
SYNOPSIS
DESCRIPTION
AUTHOR
REPORTING BUGS
COPYRIGHT
SEE ALSO

This document was created by man2html using the manual pages.
Time: 17:32:54 GMT, October 23, 2013

2. unlink.2.man

Manpage of UNLINK

UNLINK

Section: Linux Programmer's Manual (2)
Updated: 2004-06-23
Index Return to Main Contents
 

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 file system. 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

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 permission. (See also path_resolution(7).)
EBUSY (not on Linux)
The file pathname cannot be unlinked because it is being used by the system or another process and the implementation considers this an error.
EFAULT
pathname points outside your accessible address space.
EIO
An I/O error occurred.
EISDIR
pathname refers to a directory. (This is the non-POSIX value returned by Linux since 2.1.132.)
ELOOP
Too many symbolic links were encountered in translating pathname.
ENAMETOOLONG
pathname was too long.
ENOENT
A component in pathname does not exist or is a dangling symbolic link, or pathname is empty.
ENOMEM
Insufficient kernel memory was available.
ENOTDIR
A component used as a directory in pathname is not, in fact, a directory.
EPERM
The system does not allow unlinking of directories, or unlinking of directories requires privileges that the calling process doesn't have. (This is the POSIX prescribed error return; as noted above, Linux returns EISDIR for this case.)
EPERM (Linux only)
The file system does not allow unlinking of files.
EPERM or EACCES
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, and the process is not privileged (Linux: does not have the CAP_FOWNER capability).
EROFS
pathname refers to a file on a read-only file system.
 

CONFORMING TO

SVr4, 4.3BSD, POSIX.1-2001.  

BUGS

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

SEE ALSO

rm(1), chmod(2), link(2), mknod(2), open(2), rename(2), rmdir(2), unlinkat(2), mkfifo(3), remove(3), path_resolution(7), symlink(7)  

COLOPHON

This page is part of release 3.32 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/.


 

Index

NAME
SYNOPSIS
DESCRIPTION
RETURN VALUE
ERRORS
CONFORMING TO
BUGS
SEE ALSO
COLOPHON

This document was created by man2html using the manual pages.
Time: 17:32:54 GMT, October 23, 2013

ENGLISH - ENGLISH - ENGLISH - ENGLISH - ja - nl - ENGLISH

Meet new people