Allan Schrum wrote:
>
> Hi Matthias,
>
> The problem is when rsync is not actively connected to a client. When
> started as a service, an instance of rsync is running listening for
> connections. When the connection occurs, the transfer takes place.
> Afterwards, the original instance remains sti
>>In the event log the following message was found:
>
>>rsyncd: PID 1800: rsync error: error in file IO (code 11) at
>>/home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/clientserver.c(985)
>>[receiver=3.0.4].
>
> I downloaded the source, rebuilt and I am running under the debugger. The
> line indi
Allan Schrum wrote:
>>In the event log the following message was found:
>
>>rsyncd: PID 1800: rsync error: error in file IO (code 11) at
>>/home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/clientserver.c(985)
>>[receiver=3.0.4].
>
> I downloaded the source, rebuilt and I am running under the de
>In the event log the following message was found:
>rsyncd: PID 1800: rsync error: error in file IO (code 11) at
>/home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/clientserver.c(985)
>[receiver=3.0.4].
I downloaded the source, rebuilt and I am running under the debugger. The line
indicated a
I have RSync installed as a service on a Windows XP laptop. The previous
version (2.x?) did not exhibit the problems I am having now. The service stops.
It typically stops during shutdown but sometimes while it is operating during a
typical rsync operation. By "stops" I mean that it fails unexpe
5 matches
Mail list logo