Tried this on a couple of systems with & without root, & checked permissions. Same basic outcome, regardless of the actual content of the --path argument.
$ safenode-manager add --owner ptvirgo --user pvirgo --home-network --auto-restart --count 1
╔═══════════════════════════╗
║ Add Safenode Services ║
╚═══════════════════════════╝
1 service(s) to be added
Retrieving latest version for safenode...
Using cached safenode version 0.108.4...
Download completed: /home/pvirgo/.local/share/safe/node/downloads/safenode
Services Added:
✓ safenode2
- Safenode path: /home/pvirgo/.local/share/safe/node/safenode2/safenode
- Data path: /home/pvirgo/.local/share/safe/node/safenode2
- Log path: /home/pvirgo/.local/share/safe/node/safenode2/logs
- RPC port: 127.0.0.1:46521
[!] Note: newly added services have not been started
$ safenode-manager add --owner ptvirgo --user pvirgo --home-network --auto-restart --path $HOME/.local/share/safe/node/ --count 1
╔═══════════════════════════╗
║ Add Safenode Services ║
╚═══════════════════════════╝
1 service(s) to be added
Error:
0: Permission denied (os error 13)
Location:
sn_node_manager/src/helpers.rs:279
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⋮ 3 frames hidden ⋮
4: sn_node_manager::helpers::get_bin_version::h7e353d616485dc1e
at <unknown source file>:<unknown line>
5: safenode_manager::main::{{closure}}::hbe9ec6ba588431b5
at <unknown source file>:<unknown line>
6: tokio::runtime::scheduler::current_thread::Context::enter::h5107ded5dc1ec1a3
at <unknown source file>:<unknown line>
7: tokio::runtime::context::set_scheduler::hf1156e93a88fcde8
at <unknown source file>:<unknown line>
8: tokio::runtime::scheduler::current_thread::CoreGuard::block_on::hca57c916e09b8e0f
at <unknown source file>:<unknown line>
9: tokio::runtime::context::runtime::enter_runtime::he328d9b7a7d746b4
at <unknown source file>:<unknown line>
10: tokio::runtime::runtime::Runtime::block_on::h2f671f700169ac81
at <unknown source file>:<unknown line>
11: safenode_manager::main::h5f6da247175de7b5
at <unknown source file>:<unknown line>
12: std::sys_common::backtrace::__rust_begin_short_backtrace::h68e3924a149fcbf0
at <unknown source file>:<unknown line>
13: std::rt::lang_start::{{closure}}::hacbef5f6658bef64
at <unknown source file>:<unknown line>
14: std::rt::lang_start_internal::h14632ddfb850e80e
at <unknown source file>:<unknown line>
15: main<unknown>
at <unknown source file>:<unknown line>
Tried this on a couple of systems with & without root, & checked permissions. Same basic outcome, regardless of the actual content of the --path argument.