Open System Services System Calls Reference Manual (G06.29+, H06.08+, J06.03+)

System Functions (r) rmdir(2)
Accessing Files in Restricted-Access Filesets
When accessing a file in a restricted-access fileset, the super ID (255,255 in the Guardian
environment, 65535 in the OSS environment) is restricted by the same file permissions and
owner privileges as any other user ID: It has no special privileges unless the executable file
started by the super ID has the PRIVSETID file privilege. In this case, the process started by the
super ID can switch to another ID and then access files in restricted-access filesets as that ID.
Executable files that have the PRIVSOARFOPEN privilege and that are started by a member of
the Safeguard SECURITY-OSS-ADMINISTRATOR (SOA) group have the appropriate privilege
to use this function on any file in a restricted-access fileset. However, Network File System
(NFS) clients are not granted SOA group privileges, even if these clients are accessing the sys-
tem with a user ID that is a member of the SOA security group.
For more information about restricted-access filesets and file privileges, see the Open System Ser-
vices Management and Operations Guide.
Use From the Guardian Environment
The rmdir() function is one of a set of functions that have the following effects when the first of
them is called from the Guardian environment:
• Two Guardian file system file numbers (not necessarily the next two available) are allo-
cated for the root directory and the current working directory. These file numbers cannot
be closed by calling the Guardian FILE_CLOSE_ procedure.
• The current working directory is assigned from the VOLUME attribute of the Guardian
environment =_DEFAULTS DEFINE.
• The use of static memory by the process increases slightly.
These effects occur only when the first of the set of functions is called. The effects are not cumu-
lative.
NOTES
On systems running H06.24 or later H-series RVUs or J06.13 or later J-series RVUs, you can use
this function with 32-bit or 64-bit OSS applications.
RETURN VALUES
Upon successful completion, the rmdir() function returns the value 0 (zero). If the rmdir()
function fails, the value -1 is returned and errno is set to indicate the error.
ERRORS
If any of the following conditions occurs, the rmdir() function sets errno to the corresponding
value:
[EACCES] One of the following conditions exists:
• Search permission is denied on a component of the directory pathname
specified by the path parameter.
• Write permission is denied on the parent directory of the directory to be
removed.
• The S_ISVTX flag is set on the directory containing the directory
referred to by the path parameter. However, the calling process is not
any of the following:
— The parent directory owner
527186-023 Hewlett-Packard Company 6−53