Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

if first invocation is cancelled before unlocking key, second invocation fails, requires unmount #9

Closed
dradetsky opened this issue Mar 9, 2016 · 2 comments
Assignees
Labels

Comments

@dradetsky
Copy link

Suppose I run sshfs having not yet ssh-added my key. I am then prompted to enter the password for my key. I want to enter my password only once, so I C-c the sshfs process, run ssh-add, then re-run sshfs. I assume that because I haven't given sshfs my unlocked key, nothing has happened, so the result will be that the second sshfs invocation mounts the filesystem.

The actual result is that the filesystem is somehow half-mounted. I don't yet fully understand what has happened, but the upshot is that it will not mount until I run fusermount -uz $MOUNTPOINT (The -z may not be required).

I don't see any reason why beginning the mount before acquiring the key or password or whatever is desirable.

@dradetsky
Copy link
Author

In case this has already been fixed upstream:

% sshfs -V
SSHFS version 2.5
FUSE library version: 2.9.4
fusermount version: 2.9.4
using FUSE kernel interface version 7.19

@Nikratio Nikratio added the bug label Mar 9, 2016
@Nikratio
Copy link
Contributor

Nikratio commented Mar 9, 2016

Fully agree, patches are welcome :-).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants