line??
BTW, when I'm making a connection, the 'persist' option does seem to
work, because a failed connection will keep redialing until a
successful connection occurs. It's just he 'modem handup' situation
when 'persist' fails to reconnect that is a problem.
hacker
Package: rsync
Version: 2.6.4-6
I've successfully used rsync (2.6.4-6) to transfer files over a plip
connection via a cable connecting the parallel ports of my desktop and
laptop, using kernel 2.4.27.
Now, I'm trying to use kernel 2.6.10 (and 2.6.11) and rsync won't
establish a connection.
root
On 5/25/05, Paul Slootman <[EMAIL PROTECTED]> wrote:
> On Wed 25 May 2005, hacker wrote:
> >
> > Now, I'm trying to use kernel 2.6.10 (and 2.6.11) and rsync won't
> > establish a connection.
> >
> > root #: rsync mydesktop::
> > rsync:
On 5/30/05, Paul Slootman <[EMAIL PROTECTED]> wrote:
> On Thu 26 May 2005, hacker wrote:
> > >
> > > Could you do an "lsof -p 8349", to see what rsync is listening to?
> >
> > Today, it's process 1984 and 'lsof -p 1984' returns to t
Package: rsync
Version: 2.6.4-4
Severity: grave
Justification: renders package unusable
I upgraded from 2.6.4-2 to 2.6.4-4 on my local network server and now
my client gets an error:
$ rsync mydesktop::
rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data s
Package: gtkparasite
Version: 0+git20090907-1
Severity: grave
Tags: sid
Justification: renders package unusable
The package seems to be missing the actual `gtkparasite` executable. The
program's website describes this executable, but it is not present after
installing.
-- System Information:
De
This bug is solved. Please withdraw it from your buglist.
It turns out that I was loading the parport_pc module with specific
irq and address, and the 2.6.x kernels didn't recognize it. So, now I
just 'modprobe parport_pc' and it works. It had nothing to do with
rsync!
Thanks,
7 matches
Mail list logo
