[Csync2] Permission denied when syncing a new file

[Giampaolo Tomassoni]

From: csync2-bounces at lists.linbit.com
> 
> On 25-jan-2007, at 21:30, Giampaolo Tomassoni wrote:
> 
> > From: csync2-bounces at lists.linbit.com
> >>
> >> Hi list,
> >>
> >> What I couldn't find in the paper.pdf is if it's necessary to keep /
> >> etc/csync2.cfg in sync on all the machines in a group?
> >>
> >> When I add a file to my /etc/csync2.cfg on host1 and try to sync it
> >> to host2 with csync -xv, I get a permission denied error. The file
> >> doesn't exist yet on host2, and isn't defined in host2's /etc/
> >> csync2.cfg either.
> >> Adding /etc/csync2.cfg to the group and syncing again fixes this, but
> >> I'm not sure if this is the right way to do it.
> >
> > Hi user, :)
> >
> > you did right.
> >
> > Also note that, when the content of /etc/csync2.cfg changes as the  
> > result of an update, csync2 doesn't re-reads it during the updating  
> > session. This means that the update will proced with a "stale"  
> > config on the receiving side and problems may easily occur, because  
> > the sending side works with a different configuration with respect  
> > to the receiving one.
> >
> > Personally, when I change /etc/csync2.cfg in my "master" system,  
> > I'm used to issue a csync2 -c /etc/csync2.cfg followed by a csync2 - 
> > c /etc/csync2.cfg -x /etc/csync2.cfg as soon as possible and  
> > shurely *before* any other kind of csync2's update.
> >
> >
> 
> Ah, that explains what I saw, and why csync2 -x worked the second time.
> The first time the other side reads the config file and the second  
> time it allow me to sync the file I want.

Right.

Please note I posted the wrong commands I execute after a change in /etc/csync2.cfg.

The actually are:

	csync2 -c /etc/csync2.cfg && csync2 -x /etc/csync2.cfg

Cheers,

	Giampaolo

> >> Thanks for your response,
> >
> > You welcome,
> >
> > Giampaolo
> >
> >>
> >>
> >> Ruben Kerkhof
> >
> 
> 
> Maybe the paper.pdf should explain that the file lists in the config  
> file have to be the same on both your hosts. That might help other  
> users like me ;-)
> If you start with the example in the paper, it's never going to work.

It doesn't need to be the same in the overall. It is the content of a group section which have to be semantically the same among all the nodes belonging to the group.


> Syncing you /etc/csync2.cfg could be a security risk though, but if  
> the alternative is to manually edit the csync2.cfg on every host...

When you need to use server groups extensively, you probably will have much troubles in synching /etc/csync2.cfg: each node may have its own, unique content there. So, in that case you may probably need to manually edit it in each node...


> Kind regards,
> 
> Ruben
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Csync2 mailing list
> Csync2 at lists.linbit.com
> http://lists.linbit.com/mailman/listinfo/csync2