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

SSHFS instances orphaned once SSHFS-Win-Manager exits #1

Closed
billziss-gh opened this issue Mar 22, 2020 · 1 comment
Closed

SSHFS instances orphaned once SSHFS-Win-Manager exits #1

billziss-gh opened this issue Mar 22, 2020 · 1 comment

Comments

@billziss-gh
Copy link

Steps to reproduce

  1. Add new SSHFS connection.
  2. Click on "Connect" icon to connect to server.
  3. Click on "Folder" icon to open Explorer and verify that connection is alive.
  4. Quit SSHFS-Win-Manager and verify that file system is still running.
  5. Restart SSHFS-Win-Manager.
  6. Observe that SSHFS-Win-Manager does not detect that file system is already running.
  7. It is impossible to reconnect the connection, because the drive is already taken.

Expected behavior

I would expect that upon restarting SSHFS-Win-Manager it would detect the running instance of the file system.


Re: winfsp/sshfs-win#158

@evsar3
Copy link
Owner

evsar3 commented Mar 22, 2020

Actually it should kill all children instance when the Manager is closed.
I think you didn't noticed that when closing the main window of the Manager it actually still running in the System Tray.
The porblem here seems to be allow only one instance of the manager running. Because I think you opened a new instance of it and it don't detected the processes runing

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

No branches or pull requests

2 participants