Re: Reading for area during rsync

2006-01-31 Thread Matt McCutchen
On Tue, 2006-01-31 at 09:52 -0800, Wayne Davison wrote: > On Mon, Jan 30, 2006 at 11:36:31PM +, Jamie Lokier wrote: > > But this won't work if the change that occurred on the sending side > > after the transfer started happens within the same second, and the > > mtimes have only one second reso

RSYNC + iNotify

2006-01-31 Thread Ryan Kather
I'm looking for a way to continually monitor at least one but possibly multiple directories (and/or individual files). I would like RSYNC to immediately synchronize the changes to said directory(ies) after they occur. I believe the best approach for this would be to utilize iNotify enabled ker

RE: cwrsync server 2.0.4 / winxp / ownership problems?

2006-01-31 Thread Tevfik Karagülle
It is possible to instruct cygwin not to reflect permission changes to windows' file system. This can be done by specifying CYGWIN=nontsec. In this case, all permission related changes ordered by rsync will be discarded. Rsync daemon implemented by cwrsync server uses cygwin=notnsec by default.

Re: cwrsync server 2.0.4 / winxp / ownership problems?

2006-01-31 Thread Wayne Davison
On Tue, Jan 31, 2006 at 01:13:47PM -0500, Erik Jacobs wrote: > I didn't think that CHMod would have any effect in windows?? I assumed that the cygwin library would map the internal mode change into an appropriate external change on the filesystem. However, since I try to avoid MS Windows whenever

Re: Reading for area during rsync

2006-01-31 Thread Wayne Davison
On Mon, Jan 30, 2006 at 11:36:31PM +, Jamie Lokier wrote: > But this won't work if the change that occurred on the sending side > after the transfer started happens within the same second, and the > mtimes have only one second resolution, will it? If the file was changed twice in the same seco

DO NOT REPLY [Bug 3465] --files-from does not --delete

2006-01-31 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3465 --- Comment #3 from [EMAIL PROTECTED] 2006-01-31 11:13 MST --- (In reply to comment #2) > Another work around might be to allow a --max-size of zero combined with a > --delete. The recommended way to ask rsync to only delete files is to

RE: cwrsync server 2.0.4 / winxp / ownership problems?

2006-01-31 Thread Erik Jacobs
>The version of rsync in CVS has an option named --chmod that lets you >request permission changes for the copied files, so using that as the I didn't think that CHMod would have any effect in windows?? Are you referring to the rsync in CVS for cwrsync? -Erik -- To unsubscribe or change options

Re: cwrsync server 2.0.4 / winxp / ownership problems?

2006-01-31 Thread Wayne Davison
On Mon, Jan 30, 2006 at 04:25:01PM -0500, Erik Jacobs wrote: > Whenever I run rsync to send files to another machine, the read-only > flag gets set. The version of rsync in CVS has an option named --chmod that lets you request permission changes for the copied files, so using that as the client ve

DO NOT REPLY [Bug 3461] rsync is not atomic when temp-dir is on different device

2006-01-31 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3461 [EMAIL PROTECTED] changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

DO NOT REPLY [Bug 3444] Deal with case-insensitive file-systems better (perhaps by adding an option)

2006-01-31 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3444 --- Comment #4 from [EMAIL PROTECTED] 2006-01-31 10:34 MST --- (In reply to comment #3) > Do you mean that the ignore-case.diff patch that is found in the patches > directory of the 2.6.6 source distribution does not work ? That's right

DO NOT REPLY [Bug 3465] --files-from does not --delete

2006-01-31 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3465 --- Comment #2 from [EMAIL PROTECTED] 2006-01-31 09:13 MST --- Another work around might be to allow a --max-size of zero combined with a --delete. --maxsize of zero is not supported in rsync. While it wouldn't completely solve the origi

DO NOT REPLY [Bug 3444] Deal with case-insensitive file-systems better (perhaps by adding an option)

2006-01-31 Thread bugzilla-daemon
https://bugzilla.samba.org/show_bug.cgi?id=3444 --- Comment #3 from [EMAIL PROTECTED] 2006-01-31 08:16 MST --- > Note that the patch that came > with 2.6.6 builds, but is ineffective. The version in CVS should be OK. Do you mean that the ignore-case.diff patch that is found in the pa

RE: cwrsync server 2.0.4 / winxp / ownership problems?

2006-01-31 Thread Erik Jacobs
Hey, So I ran this command: C:\Program Files\cwRsyncServer\bin>xcacls c:\cv7 /T /E /G Administrators:F But it doesn't seem to have fixed my problem. It processed all the files/folders. I right clicked /stuff and made sure read-only was unchecked. I then went to my laptop (WinXP): "\Program F

RE: cwrsync server 2.0.4 / winxp / ownership problems?

2006-01-31 Thread Erik Jacobs
Tevfik, Thanks for the pointer. I may move this over to cwRsync just to keep a good record of it in multiple places. I don't care about porting the permissions over from/to *nix -- I have a cron that resets the perms on the folder structure on the *nix machines (QNX 6.3 if you're interested). T

RE: cwrsync server 2.0.4 / winxp / ownership problems?

2006-01-31 Thread Erik Jacobs
Sorry, I just looked at xcacls. /T = recursive /E = edit ACL (don't replace) /G Administrators:F = Full control for all administrators Thanks again! -Original Message- From: Tevfik Karagülle [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 5:35 PM To: 'Erik Jacobs' Cc: rsync@l

Re: Reading for area during rsync

2006-01-31 Thread Jamie Lokier
Matt McCutchen wrote: > > But this won't work if the change that occurred on the sending side > > after the transfer started happens within the same second, and the > > mtimes have only one second resolution, will it? > > > > That's quite likely, if the file is reasonably small and the first > > r

rsync using ssh get stuck

2006-01-31 Thread Mark, Oren
Hi,   We started working with rsync to sync data between remote sites. We started seeing many stuck rsync processes. Usually it happens in the ssh stage while the ssh issues a “select” syscall on fd #4 while it is long gone.   Here is an example:   [EMAIL PROTECTED]:/root# ps -efww