tools/mesh-cfgclient: fix binaries and config name in README
PATCH 1/1 tools/mesh-cfgclient: fix binaries and config name in README
This patch fixes the mesh-cfgclient README file:
- The configuration directory is meshcfg not mesh-cfgcli
- The home directory is looked up using $HOME not using /home/$USER
- The binary is called mesh-cfgclient, not mesh-config
- The -c option takes a config file path, not the directory where the config file is stored.
--- tools/mesh/README | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
tools/mesh/README +3 -3
@@ -25,11 +25,11 @@ that contains information about the current state of the configured mesh network. The default directory for mesh-cfgclient configuration file is -/home/<username>/.config/mesh-cfgcli +$HOME/.config/meshcfg -To specify a custom storage directory, run mesh-config tool as: +To specify a custom file, run mesh-cfgclient tool as: - meshctl -c <config_dir_name> + mesh-cfgclient -c <config_file_name> If a configuration file is not found, it is assumed that a mesh network does not exist. In this case, the tool may be used to generate a new mesh
Signature · 1 line
2.24.0.rc1
Gix, Brian
AppliedApplied
Quoted 30 lines · Aurelien Jarno
This patch fixes the mesh-cfgclient README file:
- The configuration directory is meshcfg not mesh-cfgcli
- The home directory is looked up using $HOME not using/home/$USER
- The binary is called mesh-cfgclient, not mesh-config
- The -c option takes a config file path, not the directory where the config file is stored.--- tools/mesh/README | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)tools/mesh/README +3
-3@@ -25,11 +25,11 @@ that contains information about the current state of the configured mesh network. The default directory for mesh-cfgclient configuration file is -/home/<username>/.config/mesh-cfgcli +$HOME/.config/meshcfg -To specify a custom storage directory, run mesh-config tool as: +To specify a custom file, run mesh-cfgclient tool as: - meshctl -c <config_dir_name> + mesh-cfgclient -c <config_file_name> If a configuration file is not found, it is assumed that a mesh network does not exist. In this case, the tool may be used to generate a new mesh