Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Allow disabling signal handler #13

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.

Sign up for GitHub

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

Jump to bottom
Open
touilleMan opened this issue Jul 4, 2018 · 2 comments
Open

Allow disabling signal handler #13

touilleMan opened this issue Jul 4, 2018 · 2 comments
Labels
enhancement

Comments

@touilleMan
Copy link
Contributor

Hi,

I'd like to use llfuse as part of an asynchronous application (typically having a main thread with the asynchronous loop, then at one point starting a new thread that will run llfuse.main)
The thing is the asynchronous framework (trio in my case) already install signal handlers (and for pretty good reasons 😄 ).

So my questions are:

  • is it possible to prevent llfuse from overwriting the signals handlers ?
  • is there a way to terminate llfuse.main from another thread (typically from the asynchronous loop) ?
@Nikratio
Copy link
Contributor

Nikratio commented Jul 4, 2018

Preventing the signals handlers from being set is not currently possible, but should be trivial to add. For terminating the main loop, currently you have to unmount the filesystem. It would be trivial to expose a function that just terminates the loop though (modeled after handle_exc() in misc.pxi).

Someone would need to write a pull request for bot features though, I am unlikely to have time for this in the near future.

@touilleMan touilleMan mentioned this issue Jul 4, 2018
Closed
@touilleMan
Copy link
Contributor Author

Thanks for the quick reply

Someone would need to write a pull request for bot features though, I am unlikely to have time for this in the near future.

I've submitted PR #14 from your advices

@touilleMan touilleMan mentioned this issue Jul 5, 2018
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Nikratio @touilleMan