[Samba] sysvolcheck and sysvolreset errors

Jonathan Hunter jmhunter1 at gmail.com
Tue May 26 14:43:05 UTC 2020

On Wed, 20 May 2020 at 14:48, Roy Eastwood via samba
<samba at lists.samba.org> wrote:
> Yes, I get the similar output but it's not what sysvolcheck is expecting.       Well I suppose sysvolcheck isn't happy with the
> permissions, but as GPOs are able to be edited, changed and are applied to both computers and users then I assume this can be
> ignored.   I got the acl settings from Louis' script, but does the WiKi stipulate what they should be?   If so setting them to what
> sysvolcheck expects - will that make this error go away?   Is it a bug in sysvolcheck?

For what it's worth, I've found sysvolcheck to be quite opaque and not
always giving results that are understandable to me. Similarly to your
experience, my setup is now working but sysvolcheck still complains..
I'm at the point where I daren't run sysvolcheck for fear that it
might change my GPO permissions *away* from the working values I
currently have.

I did try and improve things a few years back, but found so many
layers in the stack (just from memory - Python code, python libraries,
C code, VFS code, and probably more) that enhancing the error
reporting (for example to show *which file* an error related to) just
required more tuits than I had available then. It's one of those
"itch" things - I spent quite a few weeks on and off, trying to use
this itch of mine to improve the error reporting, but ultimately gave
up and I now avoid sysvolcheck.. sorry..



"If we knew what it was we were doing, it would not be called
research, would it?"
      - Albert Einstein

More information about the samba mailing list