?icro MEGAS
2014-Nov-08 18:03 UTC
[Samba] Re: Re: Re: DC2 denies access whe
Hello Rowland, Louis and Min, sorry for late reply, I was really busy in the past days. As Min already wrote, I have made the same experience unfortunately. With Rowland's suggested settings it didn't solve the problem. I'm on another issue at the moment and didn't find time to check the rsync/unison process on my own, but I'll promise I'll dive into it as soon as I can. The problem really is related in the "--delete..." parameter which is exactly doing what the manual of rsync describes perfectly. I have no idea how to fix it at the moment, but if you have more clues I'd appreciate your opinion. Nice weekend, Mirco.>> On 08/11/14 16:50, Min Wai Chan wrote:>> Yep... >> >> Just like the original issue report by Megas. >> But with your suggested changes... Which is odd...>> Dear Louis and Rowland, >> >> I've try to do as suggested >> >> /root/.unison/default.prf >> remove >> perms=0 >> add >> owner=true >> group=true >> >> But still the problem on folder removed still happen... >> >> Strange...the culprit is related to the switch "--delete-after" but the most important thing is that unison seems to be misconfigured. Normally unison should sync in both directions, but actually is syncing only from dc1-->dc2. Any thoughts how to fix it? I never worked with unison before :( Mirco.
Rowland Penny
2014-Nov-08 18:27 UTC
[Samba] Re: Re: Re: DC2 denies access whe
On 08/11/14 18:03, ?icro MEGAS wrote:> Hello Rowland, Louis and Min, > > sorry for late reply, I was really busy in the past days. As Min already wrote, I have made the same experience unfortunately. With Rowland's suggested settings it didn't solve the problem. I'm on another issue at the moment and didn't find time to check the rsync/unison process on my own, but I'll promise I'll dive into it as soon as I can. The problem really is related in the "--delete..." parameter which is exactly doing what the manual of rsync describes perfectly. I have no idea how to fix it at the moment, but if you have more clues I'd appreciate your opinion. > > Nice weekend, > Mirco. >The problem is that rsync is one way, what I think happens is that rsyncs what is in 'sysvol' on DC1 to DC2 and the '--delete-after' removes anything on DC2 that is not on DC1, then unison syncs back to DC1 from DC2, but as there is no difference, there is nothing to sync. In my tests, removing the option from the sync command, stops the difference being deleted from DC2 and then unison sync's the difference to DC1. Rowland>>> On 08/11/14 16:50, Min Wai Chan wrote: >>> Yep... >>> >>> Just like the original issue report by Megas. >>> But with your suggested changes... Which is odd... >>> Dear Louis and Rowland, >>> >>> I've try to do as suggested >>> >>> /root/.unison/default.prf >>> remove >>> perms=0 >>> add >>> owner=true >>> group=true >>> >>> But still the problem on folder removed still happen... >>> >>> Strange... > the culprit is related to the switch "--delete-after" but the most important thing is that unison seems to be misconfigured. Normally unison should sync in both directions, but actually is syncing only from dc1-->dc2. > > Any thoughts how to fix it? I never worked with unison before :( > > Mirco.
Possibly Parallel Threads
- DC2 denies access when saving through the Gro
- DC2 denies access when saving through the Group Policy M
- DC2 denies access when saving through the Group Policy Management Console
- domain users "primary group" does not take effect in UNIX attributes (NIS)
- Bidirectional Rsync/Unison based SysVol replication workaround