Hello, I try to backup files from a NAS to our backup-server using rsync. The NAS itself is not able to run rsync. Therefore I installed rsyncd (cwrsync 2.1.1) on a windowsserver which has access to the NAS. I configured the rsyncd like this: [nspPR53_so2] path = /172.21.87.9/nspPR53_so/material/doc read only = true transfer logging = yes When connecting with the client I get the error message: rsync rsync://172.21.87.14/nspPR53_so2 @ERROR: chdir failed rsync error: error starting client-server protocol (code 5) at main.c(1383) [receiver=2.6.9] Any ideas what I'm making wrong? Thanks, Stefan Multimedia Solutions AG Stefan Kalb | Database Publishing Dorfstrasse 29, P.O. Box | CH-8037 Zurich | Switzerland Phone: +41 44 446 83 30 | Direct: +41 44 446 83 33 | Fax: +41 44 446 83 38 mailto:sk@mmsag.ch | Homepage: http://www.mmsag.ch The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. -------------- next part -------------- HTML attachment scrubbed and removed
On Mon, 2008-03-17 at 15:57 +0100, Kalb Stefan wrote:> I try to backup files from a NAS to our backup-server using rsync. > The NAS itself is not able to run rsync. > Therefore I installed rsyncd (cwrsync 2.1.1) on a windowsserver which > has access to the NAS. > I configured the rsyncd like this: > > [nspPR53_so2] > path = /172.21.87.9/nspPR53_so/material/doc > read only = true > transfer logging = yes > > When connecting with the client I get the error message: > rsync rsync://172.21.87.14/nspPR53_so2 > @ERROR: chdir failed > rsync error: error starting client-server protocol (code 5) at > main.c(1383) [receiver=2.6.9] > > Any ideas what I'm making wrong?The module path needs to be of a form recognized by Cygwin as UNC. You could try a double slash at the beginning, but the most reliable technique is generally to map a network drive, say N:, and then refer to that drive: /cygdrive/n/?nspPR53_so/material/doc . ?Matt
Stefan, Please keep this on the list (CC rsync@lists.samba.org ). On Mon, 2008-03-17 at 17:33 +0100, Kalb Stefan wrote:> I corrected the path to: > > [nspPR53_so2] > path = //172.21.87.9/nspPR53_so/material/doc > read only = true > transfer logging = yes > > But no success. > Error message remains the same. > > Is there a possibility to get some more information on error by setting another loglevel?Not really. Rsync running under Cygwin is failing to chdir into the module, which suggests that Cygwin does not recognize the path. Getting a module path that Cygwin likes may take some experimentation, so I recommend that you install a full Cygwin environment: run http://cygwin.com/setup.exe and then delete the cygwin1.dll that cwRsync installed to avoid incompatibilities. Example 3.11 at: http://cygwin.com/cygwin-ug-net/using-utils.html#mount suggests that you can use the Cygwin "mount" command to make the share accessible at an ordinary-looking path of your choice and then use that path. This way, you won't run out of drive letters.> Unfortunately I am not able to map the drive to a drive letter because there are plenty of shares (more than letters available)Matt
Is it just me or a lot of people on this mailing list got into a bad habit of also carbon copying to the poster as well? I subscribe to this mailing list. Why send me a duplicate copy? I get more than enough email thank you... Personally I like mailing list correspondence kept to the list. Cheers. :-)) -- Stuart Halliday -----Original Message----- From: Matt McCutchen <matt@mattmccutchen.net> To: Stuart Halliday <StuartH@ecs-tech.com> Cc: rsync@lists.samba.org Date: Wed, 19 Mar 2008 12:41:33 -0400 Subject: Re: AW: rsync Windows UNC> On Wed, 2008-03-19 at 16:37 +0000, Stuart Halliday wrote: > > Probably easier to just do: > > > > net use Z: \\sharename\ > > > > Run rsync script (with a path of /cygdrive/z/) > > > > net use z: /DELETE > > > > Certainly quicker... ;-) > > The problem is that Stefan is operating a daemon with too many shares > for them all to have drive letters all the time. It might be possible > to map and unmap network drives dynamically using "pre-xfer exec" and > "post-xfer exec", but it would take a lot of care to make that work > correctly with multiple concurrent connections. > > Matt > > -- > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: > http://www.catb.org/~esr/faqs/smart-questions.htmlThis email is the property of ECS Technology Ltd. This company is registered in Scotland with company number 212513. VAT registered GB 761 7456 12 http://www.ecs-tech.com/