Mail Archives: cygwin/2008/12/07/16:23:30
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 still listening for connections.
> When running as a service waiting for a connection, something happens to
> it which causes it to fail and exit without cleaning up. This leaves a PID
> file which blocks all restart attempts. I then must manually clean up the
> PID file to allow the service to restart. Obviously, leaving the PID file
> should not take place which is the symptom of the true problem.
>
> Something is causing rsync to fail without cleaning up the PID file.
> Sometimes it is a reboot (most often due to that). Sometimes during a
> transfer it will fail and not cleanup properly. I have not yet figured
> this out and was hoping others saw this as well.
>
> I did notice that while debugging (with gdb) rsync that if I type Ctrl-C
> that the task stops without cleaning up. However, I'm not sure if that is
> due to how gdb works, or something else.
>
> Again, this is with rsync-3.0.4-1. This cleanup problem did not exist with
> rsync-2.6.9-2. As a temporary solution, I am back to the older rsync on
> most of my machines until we get this current problem resolved.
>
> Thanks,
>
> -Allan
Hi Allen,
I didn't understand your problem.
You didn't need this PID file. Simply remove the line
pid file = xxxx
from your rsyncd.conf
br
Matthias
--
Don't panic
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -