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
VFS errors #312
Comments
Indeed, it looks like The safest way to resolve this is to compile the VFS on your server, to ensure it will have all the necessary libraries available. |
Samba 4.17+ can either bundle, or not, I'll leave this open for now. |
Note to future-self: to disable bundling, add this in
|
Yesterday with the previous Greyhole version, I was unable to build myself VFS, as underlined in my previous issue. But it seems that with the new package version it works fine (I've sent a big batch of data in one share this afternoon for testing it). I get the one-man-project issue, and building by hand the VFS module is fine, if there are no building errors. I think this could also be triggered by dpkg when installing the package, but I don't know how. In any case, for me this issue is solved, until the next significative Samba update ;). Thank you for your help ! |
Bugfix: deb-specific modules, starting at 4.17 : using non-bundled (i.e. shared) libraries (for ldb, tdb, tevent & talloc) - Ref: #312
I think I found a proper solution. |
Here is the requested output :
|
OK, thanks. |
…samba4.so (on Debian 12 at least) - Ref: #312
OK, seems fixed.
|
Thank you, I'll test it when possible :) |
Hi,
Following my issue yesterday, I've updated Greyhole with the latest version. Now when I try to use my shares, they won't open and I have this samba error :
Any idea of how to fix this ? I'm on Debian 12.
The text was updated successfully, but these errors were encountered: