-
Notifications
You must be signed in to change notification settings - Fork 15
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
Just getting 255s #316
Comments
I've got a manually compiled fusedav v2.0.51+1031 on Arch+Rpi (arm architecture) as the AUR was saying that ARM is not supported. When running Here's the matching strace:
Maybe other reporters could also run strace so we can see if there's anything in common ? I was not able to understand what is going on there. |
and here the output of fusedav -V:
|
I found that it is bailing out because there is no config file defined, here: https://github.com/pantheon-systems/fusedav/blob/v2.0.51%2B1031/src/fusedav_config.c#L210 but for some reason none of the error messages are output in the terminal. Aha, it seems one needs to create a config file: https://github.com/pantheon-systems/fusedav/blob/v2.0.51%2B1031/src/fusedav_config.c#L144 |
it works now! so to fix the issue, this is what I did:
At this point there is still no output but the return code is 0. |
Hi there,
Arch User here. I was shopping around for a WebDAV file system layer that could do direct IO and found this project. Unfortunately after forking and building based on the AUR blueprint I now have the executables but all fusedav does is return 255. I also ran with -d but still, no output. Any ideas?
Thanks.
The text was updated successfully, but these errors were encountered: