Penguin

Differences between current version and revision by previous author of rmdir(2).

Other diffs: Previous Major Revision, Previous Revision, or view the Annotated Edit History

Newer page: version 3 Last edited on Monday, June 6, 2005 12:25:14 pm by PerryLorier
Older page: version 1 Last edited on Tuesday, June 4, 2002 12:23:45 am by perry Revert
@@ -1,136 +1,36 @@
-RMDIR  
-!!!RMDIR  
-NAME  
-SYNOPSIS  
-DESCRIPTION  
-RETURN VALUE  
-ERRORS  
-CONFORMING TO  
-BUGS  
-SEE ALSO  
-----  
 !!NAME 
+rmdir - delete a directory  
  
-  
-rmdir - delete a directory  
 !!SYNOPSIS 
+ __#include <unistd.h>__  
  
+ __int rmdir(const char *__''pathname''__);__  
  
-__#include __  
-  
-  
-__int rmdir(const char  
-*__''pathname''__);__  
 !!DESCRIPTION 
+rmdir(2) deletes a directory, which must be empty.  
  
-  
-__rmdir__ deletes a directory, which must be  
-empty.  
 !!RETURN VALUE 
+On success, zero is returned. On error, -1 is returned, and ''errno'' is set appropriately.  
  
-  
-On success, zero is returned. On error, -1 is returned, and  
-''errno'' is set appropriately.  
 !!ERRORS 
+;[EPERM]: The filesystem containing ''pathname'' does not support the removal of directories.  
+;[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.  
+;[EFAULT]: ''pathname'' points outside your accessible address space.  
+;[EACCES]: Write access to the directory containing ''pathname'' was not allowed for the process's effective uid, or one of the directories in ''pathname'' did not allow search (execute) permission.  
+;[ENAMETOOLONG]: ''pathname'' was too long.  
+;[ENOENT]: A directory component in ''pathname'' does not exist or is a dangling symbolic link.  
+;[ENOTDIR]: ''pathname'', or a component used as a directory in ''pathname'', is not, in fact, a directory.  
+;[ENOTEMPTY]: ''pathname'' contains entries other than __.__ and __..__ .  
+;[EBUSY]: ''pathname'' is the current working directory or root directory of some process. Linux lets you remove the current working directory of a process, it will keep the directory around until the process exits. Linux will however complain if you try and remove a mountpoint that is in use.  
+;[ENOMEM]: Insufficient kernel memory was available.  
+;[EROFS]: ''pathname'' refers to a file on a read-only filesystem.  
+;[ELOOP]: Too many symbolic links were encountered in resolving ''pathname''.  
  
-  
-__EPERM__  
-  
-  
-The filesystem containing ''pathname'' does not support  
-the removal of directories.  
-  
-  
-__EFAULT__  
-  
-  
-''pathname'' points outside your accessible address  
-space.  
-  
-  
-__EACCES__  
-  
-  
-Write access to the directory containing ''pathname'' was  
-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__  
-  
-  
-''pathname'', or a component used as a directory in  
-''pathname'', is not, in fact, a directory.  
-  
-  
-__ENOTEMPTY__  
-  
-  
-''pathname'' contains entries other than __.__ and  
-__..__ .  
-  
-  
-__EBUSY__  
-  
-  
-''pathname'' is the current working directory or root  
-directory of some process.  
-  
-  
-__ENOMEM__  
-  
-  
-Insufficient kernel memory was available.  
-  
-  
-__EROFS__  
-  
-  
-''pathname'' refers to a file on a read-only  
-filesystem.  
-  
-  
-__ELOOP__  
-  
-  
-Too many symbolic links were encountered in resolving  
-''pathname''.  
 !!CONFORMING TO 
+SVr4, SVID, POSIX, BSD 4.3  
  
-  
-SVr4, SVID, POSIX, BSD 4.3  
 !!BUGS 
+Infelicities in the protocol underlying NFS can cause the unexpected disappearance of directories which are still being used.  
  
-  
-Infelicities in the protocol underlying NFS can cause the  
-unexpected disappearance of directories which are still  
-being used.  
 !!SEE ALSO 
-  
-  
- rename(2), mkdir(2), chdir(2),  
- unlink(2), rmdir(1), rm(1)  
-----  
+rename(2), mkdir(2), chdir(2), unlink(2), rmdir(1), rm(1) 
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.