Messages in this thread | | | Date | Tue, 27 Feb 2001 11:18:39 +0100 | From | Rasmus Andersen <> | Subject | Re: rsync over ssh on 2.4.2 to 2.2.18 |
| |
On Tue, Feb 27, 2001 at 10:02:11AM +0000, Russell King wrote: > Hi, > > I'm seeing odd behaviour with rsync over ssh between two x86 machines - > one if the is an UP PIII (Katmai) running 2.4.2 (isdn-gw) and the other > is an UP Pentium 75-200 (pilt-gw) running 2.2.15pre13 with some custom > serial driver hacks (for running Amplicon cards with their ISA interrupt- > sharing scheme).
[...]
I have seen behaviour similar to this (descibed in http://marc.theaimsgroup.com/?l=linux-kernel&m=98262067309185&w=2) locally on a 2.4.X machine where the rsync completes but fails to terminate, apparently because the child does not receive the KILLUSR1 (wild speculation)? Anyways, the parent process waits in wait4 and the child loops, waiting for the signal. This is not reproducable in 2.2.X (for me).
I have found that in order to reproduce this problem I need to make rsync do a certain amount of work. Ie., rsync linux/drivers new-dir will make rsync hang, but rsync linux/drivers/[a-p]* does not. Does the same thing apply for you? stracing the rsync does make it all work if I specify that rsync should trace the child, too.
Regards, Rasmus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |