File Paths
During the installation of the CANN package, related configurations and log information are generated. Table 1 lists the paths for storing these files.
{arch} indicates the CPU architecture, and ${HOME} indicates the directory of the current user.
Install and use the CANN software as instructed in this document. You are not advised to install the CANN software on a shared drive for usage through mounting. The CANN software depends on file locks of the file system, but some shared storage devices do not support file locks. As a result, tasks may fail to be started.
Path |
Path |
|---|---|
Software package installation log path |
If an installation path is specified, replace the following default installation path as required. Take the Toolkit package as an example:
If the size of the installation log file exceeds 50 MB, the file is automatically dumped to a backup file, for example, ascend_toolkit_install_bak.log, in the current path. |
Path for recording information such as the software package version, CPU architecture, and installation path after the installation |
If an installation path is specified, replace the following default installation path as required. Take the Toolkit package as an example:
|
Path for recording the installation paths of software packages |
|
Path for recording installation parameters (such as --install-for-all and --whitelist) specified during software package installation |
If an installation path is specified, replace the following default installation path as required.
|
Default installation path of the custom operator package |
If an installation path is specified, replace the following default installation path as required. Take the Toolkit package as an example:
If the custom operator package fails to be installed due to insufficient permission, modify the permission on the vendors directory through the installation user of the operator package. For details about the custom operator package, see CANN TBE and AI CPU Operator Development Guide. |