-
-
Notifications
You must be signed in to change notification settings - Fork 557
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
Make the fuse daemon process a parent of the payload process rather than a sibling #1287
Comments
Hello @remleduff. Yes, that would be much better. Do you know how to do this in code? A pull request on https://github.com/AppImage/type2-runtime would be highly appreciated. cc @TheAssassin |
I'll look into this, I'm interested at least. My thought is to basically switch the code after the fork call, and make the child start the payload, and the parent be the fuse daemon. |
I'd have to have a look myself first to provide any feedback. Feel free to send a PR. I'll have a look. |
Currently running an appimage creates two processes:
My users get confused by this, as they think they should be able to go to "task manager" and kill the process that they just ran. However, this just kills the fuse process, and the application keeps running to some extent. It crashes eventually when the application attempts to read something that wasn't already cached.
To me, it would be clearer in the process list if the fuse daemon process was a true parent of the payload process. Since the child in this case can't work without the parent, it would also be nice if killing the "parent" also killed the "child."
It's perfectly possible I'm misunderstanding something here though.
Thanks for a great software distribution system!
The text was updated successfully, but these errors were encountered: