An octal string containing the a POSIX-compatible file permission bitmask The bitmask should be interpreted as a series of octal digits.
ANSI (Cross Platform) char* GetFilePermissionsOctal();
int SetFilePermissionsOctal(const char* lpszFilePermissionsOctal); Unicode (Windows) LPWSTR GetFilePermissionsOctal();
INT SetFilePermissionsOctal(LPCWSTR lpszFilePermissionsOctal);
@property (nonatomic,readwrite,assign,getter=filePermissionsOctal,setter=setFilePermissionsOctal:) NSString* filePermissionsOctal; - (NSString*)filePermissionsOctal; - (void)setFilePermissionsOctal:(NSString*)newFilePermissionsOctal;
#define PID_SFTP_FILEPERMISSIONSOCTAL 22 IPWORKSSFTP_EXTERNAL void* IPWORKSSFTP_CALL IPWorksSFTP_SFTP_Get(void *lpObj, int propid, int arridx, int *lpcbVal, int64 *lpllVal); IPWORKSSFTP_EXTERNAL int IPWORKSSFTP_CALL IPWorksSFTP_SFTP_Set(void *lpObj, int propid, int arridx, const void *val, int cbVal);
An octal string containing the a POSIX-compatible file permission bitmask
The bitmask should be interpreted as a series of octal digits. For example, "100644" and "40755".
The last three octal digits are the most significant and represent, in order, the file access capabilities of the file's owner, the owner's group and other users. Each of these octal digits is, on its own, a 3-bit bitmask with the following possible values:
An octal permission digit of 7 would have all three values set and would mean that the file can be read, written and executed by that user class. For example, the octal permissions "100644" would have a value "6" for the owner, "4" for the group, and "4" for other users. This would be interpreted to mean that all users can read the file, no users can execute it and only the owner can write it. The permissions "40755" would mean that all users can read and execute the file, but only the owner can write it.
The previous octal digit is another bitmask with the following values:
|1 (001)||Sticky Bit - retain the file in memory for performance|
|2 (010)||Set GID - sets the group ID of the process to the file's group ID upon execution (only for executable files)|
|4 (100)||Set UID - sets the user ID of the process to the file's user ID upon execution (only for executable files)|
The previous two octal digits are used together as a bitmask to determine the type of file. This bitmask has the following values:
|01 (000001)||Named pipe|
|02 (000010)||Character special|
|06 (000110)||Block special|
|12 (001010)||Symbolic link|
For example, the octal file permissions "100644" would indicate a regular file and octal "40755" would indicate a directory.
This property is not available at design time.