I thought the binary I down loaded was built with Cygwin but when I try
your suggestion for the path names, RSync complains.
Any chance I could get your binary?
On Wed, Jul 04, 2001 at 03:35:00PM +1000, Martin Pool wrote:
On 28 Jun 2001, Kevin Faust [EMAIL PROTECTED] wrote:
I am running rsync on lots of Win2K machines. It was built from the
rsync 2.4.6 sources using Cygwin.
One issue, the rsyncd.conf file requires a use chroot=false
On Thu, Jul 05, 2001 at 12:38:00AM -0500, Phil Howard wrote:
Wayne Davison wrote:
We certainly do need to be careful here, since the interaction between
the various read and write functions can be pretty complex. However, I
think that the data flow of my move-files patch stress-tests
On Thu, Jul 05, 2001 at 12:48:06PM -0500, Dave Dykstra wrote:
If you really want it to stay in the foreground, edit become_daemon in
socket.c.
It would be nice to have this available as an option so rsyncd can be run
under djb's daemontools.
--
Jos Backus _/ _/_/_/
Has anyone seen this message before? If so, can you tell me what it means?
Rsync returned: c:\program files\agenda\rsync.exe: *** shared region is
corrupted. inited 27
0 [main] ? 0 lock_pinfo_for_update: rc 0, pinfo_mutex 0x,
Win32 error 6
BEGIN:VCARD
VERSION:2.1
Dave Dykstra wrote:
You shouldn't have to have it be in the foreground in order for strace -f
You're right, I was not aware of that option. And I thought I
knew my way around strace.
Here's what strace shows me:
[pid 14576] open(/tmp/rsyncd.lock, O_RDWR|O_CREAT|0x8000, 0600) = 4
[pid 14576]
We do a bunch of distribution to remote machines (under Windows NT) using
compare-dest to make use of existing files on those machines when possible.
Up until now, the comparison directory has always been at least one level
down in the directory hierarchy, but we've just started doing full
