failed to mount (hardcoded fusermount path?)
vtolstov opened this issue · comments
circuit -a 37.139.40.30:11022 -m /home/vtolstov/circuit/
CIRCUIT 2014 gocircuit.org
2014/04/25 16:18:54 created lock /tmp/circuit-R4c4bd0e1559f4f35-P6208/.lock
circuit://37.139.40.30:11022/6208/R4c4bd0e1559f4f35
2014/04/25 16:18:54 X7aac3208da7a7a82
2014/04/25 16:18:54 fuse mounting /home/vtolstov/circuit/ (fusermount: "", fork/exec /bin/fusermount: no such file or directory)
vtolstov@selfip ~ $ which fusermount
/usr/bin/fusermount
yes. it was. don't worry about this bug though.
i am getting rid of the file system interface in favor
of a tool-based one. fuse shouldn't be needed any more.
On 25 April 2014 08:18, Vasiliy Tolstov notifications@github.com wrote:
circuit -a 37.139.40.30:11022 -m /home/vtolstov/circuit/
CIRCUIT 2014 gocircuit.org
2014/04/25 16:18:54 created lock /tmp/circuit-R4c4bd0e1559f4f35-P6208/.lock
circuit://37.139.40.30:11022/6208/R4c4bd0e1559f4f35
2014/04/25 http://37.139.40.30:11022/6208/R4c4bd0e1559f4f352014/04/25 16:18:54 X7aac3208da7a7a82
2014/04/25 16:18:54 fuse mounting /home/vtolstov/circuit/ (fusermount: "", fork/exec /bin/fusermount: no such file or directory)
vtolstov@selfip ~ $ circuit -a 37.139.40.30:11022 -m /home/vtolstov/circuit/^C
vtolstov@selfip ~ $ which fusermount
/usr/bin/fusermount—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4
.
Thanks