Open System Services System Calls Reference Manual (G06.28+, H06.05+)

System Functions (k - m) lstat(2)
Guardian st_mode
Example in /G File Type File Type Permissions
___________________________________________________________________
N/A Directory r-xr-xr-x
/G
vol Disk volume Directory rwxrwxrwx
vol/subvol Subvolume Directory rwxrwxrwx
vol/subvol/fileid Disk file Regular file See following text
vol/#123 Temporary disk file Regular file See following text
ztnt Subtype 30 process Directory --x--x--x
ztnt/#pty0001 Subtype 30 process
with qualifier
Character special rw-rw-rw-
vol1/zyq00001 Subvolume Directory ---------
A Guardian file classified as a directory is always owned by the super ID.
Guardian permissions are mapped as follows:
• Guardian network or any user permission is mapped to OSS other permission.
• Guardian community or group user permission is mapped to OSS group permission.
• Guardian user or owner permission is mapped to OSS owner permission.
• Guardian super ID permission is mapped to OSS super ID permission.
• Guardian read permission is mapped to OSS read permission.
• Guardian write permission is mapped to OSS write permission.
• Guardian execute permission is mapped to OSS execute permission.
• Guardian purge permission is ignored.
Users are not allowed read access to Guardian processes.
OSS file permissions are divided into three groups (owner, group, and other) of three permission
bits each (read, write, and execute). The OSS permission bits do not distinguish between remote
and local users as Guardian security does; local and remote users are treated alike.
Use on Remote Objects
The content of the st_dev field of the stat structure is unique for each node in /E because each
node is a separate fileset. Values for directories within /E are the same as described for objects
on the local HP NonStop node.
The S_ISEXPANDOBJECT macro can indicate whether an object in the /E directory is on a
remote HP NonStop node when the st_dev field is passed to the macro. The value of the macro
is TRUE if the object is on a remote HP NonStop node and FALSE otherwise.
Use From the Guardian Environment
A Guardian process can use thee lstat() function when you use the #define
_XOPEN_SOURCE_EXTENDED 1 feature test macro or an equivalent compiler command
option to compile the process.
The lstat() function belongs to 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. You cannot close these
file numbers by calling the Guardian FILE_CLOSE_ procedure.
527186-007 Hewlett-Packard Company 4−35