This has nothing to with the fusepy Python interface, but only with the underlying C-implementation of (lib)FUSE. The default fuse command line help gives you:

-d   -o debug  enable debug output (implies -f)
-f             foreground operation
-s             disable multi-threaded operation

So if you are using the debug mode, fuse will automatically also operate in foreground mode.

When running in background mode (so no -f or -d), fuse will use a fork-call to create a child process, which will continue to run in the background (even when you close your current shell) while fuse terminates the original process (see the implementation here). This makes sense for production use, as you usually want your mount to survive when you close the terminal window. You can still find the running process by using e.g. (h)top or ps.

During development, you usually don't want your process to fork to background, so the -f option is automatically enabled when you pass -d, to make debugging easier.

Anyways, if you take a closer look at the stacktrace, you'll find that your program terminates due to a ServerSelectionTimeoutError: No servers found yet raised by pymongo. So that has nothing to do with fusepy, but is probably entirely in your code. I guess this is either due to a timing issue/race condition or could be due to some socket or thread being created before the init() method was called. You shouldn't create such objects before you are calling the python FUSE function, which in turn calls the C-function fuse_main, which might lead to a fork. Better create them in the init() callback, which will always be after the fork.

fusepy doesn't work when in background mode #132

Description

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions