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,
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 the prompt
> > (nothing identified) on the next line.
>
> That's wr
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 the prompt
> (nothing identified) on the next line.
That's wrong, at the very least it should show things like shared libs.
Were
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: failed to connect to mydesktop: Connection refused (111)
> > rs
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: failed to connect to mydesktop: Connection refused (111)
> rsync error: error in socket IO (code 10 at clientserver.c(99)
>
> I
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
6 matches
Mail list logo
