Open System Services System Calls Reference Manual (G06.25+, H06.03+)

System Functions (k - m) lstat(2)
The st_ctime and st_atime fields for Guardian regular disk files (except for EDIT files) are
updated by OSS function calls, not by Guardian procedure calls.
The time fields for /G, /G/vol, and /G/vol/subvol always contain the current time.
When the path parameter points to the name of a Guardian process that is not a process of sub-
type 30, the lstat() function call fails. The value -1 is returned and errno is set to [ENOENT].
The lstat() function always returns access modes of "d---------" when the
path parameter points
to a Guardian subvolume that has a reserved name beginning with "ZYQ". The other
access
modes reported for files in /G vary according to the file type.
The following table shows the mapping between Guardian files and their corresponding file types
described in the st_mode field.
Table 4−1. Guardian File Type Mappings
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:
• A Guardian network or any user permission is mapped to an OSS other permission.
• A Guardian community or group user permission is mapped to an OSS group permission.
• A Guardian user or owner permission is mapped to an OSS owner permission.
• A Guardian super ID permission is an 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). Note that the OSS permission bits do not distinguish
between remote and local users as Guardian security does; local and remote users are treated
alike.
527186-003 Hewlett-Packard Company 4−19