search for: remote_run_after_cmd

...On the other hand, the page https://wiki.samba.org/index.php/Sysvolreset claims that one should never run sysvolreset or even sysvolcheck (!?) in such a scenario. So what is the correct advice? I would assume that I do not need to reset the permissions all the time, so I could safely omit the REMOTE_RUN_AFTER_CMD in the osync config? Best regards, Jakob

Hi, In reading this list I see a lot of talk about samba-tool ntacl sysvolreset actually breaking things. Given the above How do I properly configure a 2nd AD DC or setup sysvol replication? For instance If I were to follow https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory In the Built-in Groups GID Mappings section the last thing it says to do is run samba-tool

...the page https://wiki.samba.org/index.php/Sysvolreset > claims that one should never run sysvolreset or even sysvolcheck (!?) in > such a scenario. > So what is the correct advice? I would assume that I do not need to > reset the permissions all the time, so I could safely omit the > REMOTE_RUN_AFTER_CMD in the osync config? > > Best regards, Jakob > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba