Skip to main content

Client Setting Files

The Kinds and Reading Order of the Setting Files#

HCP tools provides the following configuration files on the client.

command namefile name
hcphcp.conf
hsynchsync.conf
hrmhrm.conf
hcp-lshcp-ls.conf
hmkdirhmkdir.conf
hpwdhpwd.conf
hmvhmv.conf
hlnhln.conf
hchmodhchmod.conf
hchownhchown.conf

Each command load the following configuration files in the order. 'hcp.conf' is an example representation to describe the order.

  1. /etc/hcp/hcp.conf (Linux), C:\ProgramData\Clealink\HCP Tools\hcp.conf (Windows)
  2. \<user home directory>/.hcp/hcp.conf (Linux), \<user home directory>_hcp\hcp.conf (Windows)
  3. \<the path configured in the config-file options>

When the file doesn’t exist, it is skipped. When the configuration file wasn’t read successfully, file read error occurs and the operation stops.

You need a privilege to edit /etc/hcp/hcp.conf in the first file of No.1.

If you change configurations in ordinary users, please use the second file of \<user home directory>/.hcp/hcp.conf or the third file of \<the path configured in the config-file options>.

Including Setting Files#

On each configuration file, You can load an external configuration file, noted as 'common configuration file' below, to share the configuration across any client configuration files. This results in preventing you from writing a configuration to each configuration file respectively and saving time to change your configuration.

  1. Create a common configuration file to describe configurations to share across client configuration files. For example, the file name is 'hcp-common.conf' here.

  2. Add an including statement to hcp.conf.

    [root@localhost ~]# vi hcp.conf Include /etc/hcp/hcp-common.conf // Specifying a common configuration file in an absolute path or relative one.

  3. Add the including statements to other client configuration files of hsync.conf, hrm.conf, hcp-ls.conf, hmkdir.conf, hpwd.conf, hmv.conf, hln.conf, hchmod.conf, hchown.conf in the same manner.

And you can write this including statement in any place on the configuration files. Loaded configurations from the statement overwrites configurations loaded before. You cannot make nesting the including statement.

When you specify the common configuration file in a relative path, HCP tools searchs for it in relative from client configuration files to include it.