SFTP Attributes Controls and VIs
Owning Palette: Toolkit
Requires: LIBSSH2
A container class for file or directory attributes, or metadata, such as permissions and time stamps.
Class Item | Description |
---|---|
Type Definitions | Groups related files into a folder |
Utility | Groups related files into a folder |
Read User ID | Gets the POSIX-style Group Identifier (GID) for the remote SFTP filesystem entry. |
Write User ID | Sets the POSIX-style User Identifier (UID) for the remote SFTP filesystem entry. |
Read Access Time | Gets the last time the remote SFTP filesystem entry was read in seconds relative to the UNIX epoch. |
Read File Size | Gets the number of bytes for the remote SFTP filesystem entry. |
Read File Type | Gets the kind of SFTP filesystem entry for the remote SFTP filesystem entry. |
Read Flags | Gets the SFTP flags for the remote SFTP filesystem entry. |
Read Group ID | Gets the POSIX-style group ID (GID) for a remote SFTP filesystem entry. |
Write Group ID | Sets the POSIX-style filesystem entry's Group ID (GID). |
Read Modified Time | Gets the last time the remote SFTP filesystem entry was modified in seconds relative to the UNIX epoch. |
Read Permissions | Gets the POSIX-style filesystem permissions, or mode. |
Write Permissions | Sets the POSIX-style filesystem permissions, or mode. |
Create | Creates a new SFTP Attributes object that represents a libssh2lv shared library SFTP Attributes struct. This VI must be called, or executed, before using any other SFTP Attributes-related VIs. This VI allocates memory within the libssh2lv shared library that must be explicitly deallocated, or freed, at the end of the application using the Destroy VI to avoid memory leaks or running Out-of-Memory (OOM) on a resource contrained system. A SFTP Attributes object represents the metadata associated with a remote SFTP filesystem entry. |
Destroy | Deallocates, or frees, the memory allocated for the libssh2lv shared library SFTP Attributes struct represented by this SFTP Attributes object. After this is called, the object can no longer be used in the application without causing a segmentation fault, i.e. crashing LabVIEW. This VI must be called to avoid leaking memory or running Out-of-Memory (OOM) on resource-constrained systems. |