Re: --timeout not honoured

2009-12-19 Thread Wayne Davison
On Fri, Dec 18, 2009 at 4:29 AM, Fabian Cenedese wrote: > 13:18:52 write(4, > "\367\344\356\325UUM3\273*<17\7\256D\255\225x0\345^{\203"..., 4092) = 4092 > 13:18:52 time(NULL)                     = 1261138732 > 13:18:52 select(5, NULL, [4], [4], {60, 0}) = 0 (Timeout) > 13:19:52 time(NULL)        

Re: --timeout not honoured

2009-12-18 Thread Fabian Cenedese
At 14:19 16.12.2009 -0800, Wayne Davison wrote: >On Tue, Dec 15, 2009 at 11:41 PM, Fabian Cenedese ><cened...@indel.ch> wrote: >I think I know now where my confusion comes from. The reported time is not >the actual time without action but the time since the start of the r

Re: --timeout not honoured

2009-12-16 Thread Wayne Davison
On Tue, Dec 15, 2009 at 11:41 PM, Fabian Cenedese wrote: > I think I know now where my confusion comes from. The reported time is not > the actual time without action but the time since the start of the rsync > command. > It shouldn't be, since it is reporting the time elapsed since the last inp

Re: --timeout not honoured

2009-12-15 Thread Fabian Cenedese
At 10:27 15.12.2009 +0100, Fabian Cenedese wrote: >Hi > >I already wrote about this problem half a year ago but didn't get >an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html > >I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800. >But still I often have rs

--timeout not honoured

2009-12-15 Thread Fabian Cenedese
Hi I already wrote about this problem half a year ago but didn't get an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800. But still I often have rsync stall much longer than that. Some examples: 2009/12