X-Git-Url: http://git.osdn.net/view?a=blobdiff_plain;f=original%2Fman2%2Fclose.2;fp=original%2Fman2%2Fclose.2;h=0000000000000000000000000000000000000000;hb=2460a0b8024ceb8570acdbc9208713d79458efcb;hp=e6802547760ee39addeca30bd2eb24fd0a1c9be6;hpb=83f9e5d087c3464d5131604d3c9893479e6228eb;p=linuxjm%2FLDP_man-pages.git diff --git a/original/man2/close.2 b/original/man2/close.2 deleted file mode 100644 index e6802547..00000000 --- a/original/man2/close.2 +++ /dev/null @@ -1,146 +0,0 @@ -.\" This manpage is Copyright (C) 1992 Drew Eckhardt; -.\" and Copyright (C) 1993 Michael Haardt, Ian Jackson. -.\" -.\" %%%LICENSE_START(VERBATIM) -.\" Permission is granted to make and distribute verbatim copies of this -.\" manual provided the copyright notice and this permission notice are -.\" preserved on all copies. -.\" -.\" Permission is granted to copy and distribute modified versions of this -.\" manual under the conditions for verbatim copying, provided that the -.\" entire resulting derived work is distributed under the terms of a -.\" permission notice identical to this one. -.\" -.\" Since the Linux kernel and libraries are constantly changing, this -.\" manual page may be incorrect or out-of-date. The author(s) assume no -.\" responsibility for errors or omissions, or for damages resulting from -.\" the use of the information contained herein. The author(s) may not -.\" have taken the same level of care in the production of this manual, -.\" which is licensed free of charge, as they might when working -.\" professionally. -.\" -.\" Formatted or processed versions of this manual, if unaccompanied by -.\" the source, must acknowledge the copyright and authors of this work. -.\" %%%LICENSE_END -.\" -.\" Modified Wed Jul 21 22:40:25 1993 by Rik Faith -.\" Modified Sat Feb 18 15:27:48 1995 by Michael Haardt -.\" Modified Sun Apr 14 11:40:50 1996 by Andries Brouwer : -.\" corrected description of effect on locks (thanks to -.\" Tigran Aivazian ). -.\" Modified Fri Jan 31 16:21:46 1997 by Eric S. Raymond -.\" Modified 2000-07-22 by Nicolás Lichtmaier -.\" added note about close(2) not guaranteeing that data is safe on close. -.\" -.TH CLOSE 2 2013-12-30 "Linux" "Linux Programmer's Manual" -.SH NAME -close \- close a file descriptor -.SH SYNOPSIS -.nf -.B #include -.sp -.BI "int close(int " fd ); -.fi -.SH DESCRIPTION -.BR close () -closes a file descriptor, so that it no longer refers to any file and -may be reused. -Any record locks (see -.BR fcntl (2)) -held on the file it was associated with, -and owned by the process, are removed (regardless of the file -descriptor that was used to obtain the lock). -.PP -If -.I fd -is the last file descriptor referring to the underlying -open file description (see -.BR open (2)), -the resources associated with the open file description are freed; -if the descriptor was the last reference to a file which has been -removed using -.BR unlink (2), -the file is deleted. -.SH RETURN VALUE -.BR close () -returns zero on success. -On error, \-1 is returned, and -.I errno -is set appropriately. -.SH ERRORS -.TP -.B EBADF -.I fd -isn't a valid open file descriptor. -.TP -.B EINTR -The -.BR close () -call was interrupted by a signal; see -.BR signal (7). -.TP -.B EIO -An I/O error occurred. -.SH CONFORMING TO -SVr4, 4.3BSD, POSIX.1-2001. -.\" SVr4 documents an additional ENOLINK error condition. -.SH NOTES -Not checking the return value of -.BR close () -is a common but nevertheless -serious programming error. -It is quite possible that errors on a -previous -.BR write (2) -operation are first reported at the final -.BR close (). -Not checking the return value when closing the file may lead to -silent loss of data. -This can especially be observed with NFS -and with disk quota. -Note that the return value should be used only for diagnostics. -In particular -.BR close () -should not be retried after an -.B EINTR -since this may cause a reused descriptor from another thread to be closed. -.PP -A successful close does not guarantee that the data has been successfully -saved to disk, as the kernel defers writes. -It is not common for a filesystem -to flush the buffers when the stream is closed. -If you need to be sure that -the data is physically stored, use -.BR fsync (2). -(It will depend on the disk hardware at this point.) -.PP -It is probably unwise to close file descriptors while -they may be in use by system calls in -other threads in the same process. -Since a file descriptor may be reused, -there are some obscure race conditions -that may cause unintended side effects. -.\" Date: Tue, 4 Sep 2007 13:57:35 +0200 -.\" From: Fredrik Noring -.\" One such race involves signals and ERESTARTSYS. If a file descriptor -.\" in use by a system call is closed and then reused by e.g. an -.\" independent open() in some unrelated thread, before the original system -.\" call has restarted after ERESTARTSYS, the original system call will -.\" later restart with the reused file descriptor. This is most likely a -.\" serious programming error. -.SH SEE ALSO -.BR fcntl (2), -.BR fsync (2), -.BR open (2), -.BR shutdown (2), -.BR unlink (2), -.BR fclose (3) -.SH COLOPHON -This page is part of release 3.79 of the Linux -.I man-pages -project. -A description of the project, -information about reporting bugs, -and the latest version of this page, -can be found at -\%http://www.kernel.org/doc/man\-pages/.