| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Fixes: #208.
|
| | |
|
| |
|
|
| |
Fixes: #81.
|
| |
|
|
|
|
|
| |
We now only list options that are potentially useful for an
end-user (and unlikely to accidentally break a file system). The full
list of FUSE options has been moved to the documentation of the
fuse_new() and fuse_session_new() functions.
|
| |
|
|
|
|
| |
Instead of using command line options to modify struct fuse_conn_info
before and after calling the init() handler, we now give the file system
explicit control over this.
|
| |
|
|
|
|
| |
This option really affects the behavior of the session loop, not the
low-level interface. Therefore, it does not belong in the fuse_session
object.
|
| |
|
|
|
|
|
| |
The fix in commit cf4159156b was incomplete. While some false positives
are caused by sleep() in the file system taking longer than expected,
there was also a race condition where the file system would run before
the contents are initialized properly.
|
| | |
|
| |
|
|
|
| |
I think this is the reason for a sporadic test failure, where
fuse_lowlevel_notify_store() fails.
|
|
|
This should make it more obvious at first glance what the different
examples do.
|
Nikolaus Rath