On Sun, 15 Apr 2012, Paul Slootman wrote:
> On Wed 17 Dec 2008, Peter Palfrader wrote:
> >
> > So far my analysis suggests that stuff breaks with this checkpoint setup
> > here if all of the following conditions are met:
> > - client is 2.6.9
> > - server is 3.0.2
> > - the share name is longe
On Wed 17 Dec 2008, Peter Palfrader wrote:
>
> So far my analysis suggests that stuff breaks with this checkpoint setup
> here if all of the following conditions are met:
> - client is 2.6.9
> - server is 3.0.2
> - the share name is longer than 14 chars.
>
> If any of those conditions is not m
On Wed, 17 Dec 2008, Peter Palfrader wrote:
> otoh it works with etch clients from hosts that aren't on my university
> network. So maybe let's blame it on a broken PIX or something for now.
>
> I'll let you kow if I learn anything new.
So far my analysis suggests that stuff breaks with this ch
On Wed, 17 Dec 2008, Peter Palfrader wrote:
> On Wed, 17 Dec 2008, Peter Palfrader wrote:
>
> > On Tue, 16 Dec 2008, Paul Slootman wrote:
> >
> > > I'm still interested in seeing tcpdumps and perhaps strace's from the
> > > 3.0.3 rsync version though.
> > > What do your rsync invocations (in xin
On Wed, 17 Dec 2008, Peter Palfrader wrote:
> On Tue, 16 Dec 2008, Paul Slootman wrote:
>
> > I'm still interested in seeing tcpdumps and perhaps strace's from the
> > 3.0.3 rsync version though.
> > What do your rsync invocations (in xinetd config, I mean) and
> > rsyncd.conf's look like?
>
> O
On Tue, 16 Dec 2008, Paul Slootman wrote:
> I'm still interested in seeing tcpdumps and perhaps strace's from the
> 3.0.3 rsync version though.
> What do your rsync invocations (in xinetd config, I mean) and
> rsyncd.conf's look like?
Ok, different host - no ip based vhosts stuff around to interf
On Tue, 16 Dec 2008, Paul Slootman wrote:
> > > There isn't some inetd-type thing that wraps accesses to the rsync
> > > daemon, that may be screwing things up?
> >
> > Well, it is running out of xinetd, but that doesn't change between 2.6.9
> > and 3.0.3.
>
> Yes, but it may interact in some wa
On Tue 16 Dec 2008, Peter Palfrader wrote:
> On Tue, 16 Dec 2008, Paul Slootman wrote:
>
> > > per request of mirroradm I had installed rsync 3.0.3-2~bpo40+1 on
> > > kassia.debian.org.
> > >
> > > This resulted in stable rsync clients (2.6.9-2etch2) no longer being
> > > able to access rsync sha
On Tue, 16 Dec 2008, Paul Slootman wrote:
> > per request of mirroradm I had installed rsync 3.0.3-2~bpo40+1 on
> > kassia.debian.org.
> >
> > This resulted in stable rsync clients (2.6.9-2etch2) no longer being
> > able to access rsync shares:
> Perhaps having tcpdumps from both ends will help
On Thu 11 Dec 2008, Peter Palfrader wrote:
> Package: rsync
> Version: 3.0.3-2~bpo40+1
> Severity: important
>
> Hi,
>
> per request of mirroradm I had installed rsync 3.0.3-2~bpo40+1 on
> kassia.debian.org.
>
> This resulted in stable rsync clients (2.6.9-2etch2) no longer being
> able to acce
Package: rsync
Version: 3.0.3-2~bpo40+1
Severity: important
Hi,
per request of mirroradm I had installed rsync 3.0.3-2~bpo40+1 on
kassia.debian.org.
This resulted in stable rsync clients (2.6.9-2etch2) no longer being
able to access rsync shares:
| [EMAIL PROTECTED]:~$ rsync -vvv kassia.debian.
11 matches
Mail list logo
