Usage for -ethKeystorePath
option is confusing
#2691
Labels
status: community working on it
in progress
-ethKeystorePath
option is confusing
#2691
Describe the bug
The name and cli help for this option is unclear and misleading.
To Reproduce
Steps to reproduce the behavior:
From the name
ethKeystorePath
, it looks like I should provide a dir path like:But, from the help msg, it looks like I should provide a file path, like:
This is too lengthy, I believe most users would rather not to provide it.
If I provide
/root/.lpData/keystore
, the actually dir code will look into will be/root/.lpData/
, which is unexpcted.To get this right, I must provide the path with trailing
/
:/root/.lpData/keystore/
.If I provide the lengthy key file path, code will look into the parent dir, the actual key file name is ignored.
If you have multiple keys in that dir, you will need to specify it again, with
-ethAcctAddr
. Also unexpected.related source code:
go-livepeer/cmd/livepeer/starter/starter.go
Lines 525 to 530 in 7be4c3b
If the path exists, either it's dir or file, the path is split, which is not reasonable.
Expected behavior
This option should be a path to a
keystore
dir, no matter it has trailing/
or not.The text was updated successfully, but these errors were encountered: