mikeov
commented
7 years ago Here is the [documentation] fix. With all QFS tools, including qfsshell, the configuration file is intended mainly to set authentication parameters, which are typically the same in the cases when more than one file system is used.
https://github.com/quantcast/qfs/commit/840099ab9fb13fe1f0be09dd61fa520c2b832a6e
Please see my ticket here: https://quantcast.atlassian.net/projects/QFS/issues/QFS-347?filter=allopenissues
Below is my test result: `
case 1: only -f argument, use metaServer info from QfsClient.prp file
$ qfsshell -f /home/dean/work/qfsclient/QfsClient.prp QfsShell> ls dean dumpster lisa QfsShell> quit
case 2: both -f and -s arguments, use -f first, the metaServer info from QfsClient.prp file works
$ qfsshell -s xyz -f /home/dean/work/qfsclient/QfsClient.prp QfsShell> ls dean dumpster lisa QfsShell> exit
case 3: only -s argument, still works
$ qfsshell -s 192.168.72.19 QfsShell> ls dean dumpster lisa QfsShell> exit
case 4: neither -f nor -s argumen exists, print help info
$ qfsshell Usage: qfsshell either -f or -s can be used, if both exist, -f will be used {-s } [-p (default 20000)]
[-q [cmd]]
{-f }
[-l (DEBUG|INFO|NOTICE|WARN|ERROR|FATAL)]
Starts an interactive client shell to QFS.
-q: switches to execution in quiet mode.
cmd: command to execute, only in quiet mode.
`