similar to: long file name (91) error

Hi all, we are just beginning to dive into rsync. I have limited experience with just playing around with the examples and reading all the docs that I can. I just read an interesting post from a developer that mentions cwrsync is a minimalistic rsync and thus things like permissions are not transfered, the post was from 2004. Here are my questions Windows (cw)Rsync Client --> Linux Rsync

We were trying to introduce a better client side log format so that we could get timestamps and module names etc. In the rsync documentation it looks like you can use --log-format for the client ... there is even a sentence saying that this format would not interfere with the rsybc daemons format. We are using cwrsync and when we try and add --log-format="%o %h [%a] %m (%u) %f %l" The

Yes this is another connection reset issue but all I am asking is some pointers on how I can possibly determine what and why this is happening. Its easy to say its a network issue but the bosses and clients want to know how to fix this said "network issue." I have read the rsync issues list. Some of what is suggested we might try HOWEVER we cannot duplicate the errors that occur and

All, I have a CentOS 4 system I need to update OpenSSH on. Most of my experience has been on slackware and I am new to using yum and packages. I ran yum and it tells me that my current installed version is 3.9 patch level 1. It also said that there are no updates for it. I did a google for it but every link I saw that seemed to point to info about an rpm for 4.3 came up not found. Is there a

What I mean is if I have several clients performing backups at the same time what is the level of atomicity? I ask because of this ... take a look at the following lines from the log file: This is from one client operating. 2006/03/12 22:38:26 [11627] rsync to dlochart/backups/Sunday from cygnus-x1 (127.0.0.1) 2006/03/12 22:38:26 [11627] ./ 2006/03/12 22:38:26 [11627] wrote 28 bytes read 147

Can anyone shed some light on this error we are getting or know of a way to find out more info? Thanks in advance for any help ... we are puzzled. Our server is Linux, rsync version 2.6.7 running in daemon mode Our clients are windows; using cwrsync version 2.6.7 Our method of transport is opening an SSH tunnel then doing rsync through it. We have tested this internally and it has worked very

I am trying to automate ssh-keygen creating keys without a passphrase. How can I run a script that calls ssh-keygen so that it does NOT require a passphrase? When I was testing on the command line I created a file that contained 2 line feeds and piped it into stdin. I got a message mentioning that ssh-askpass could not be found and it completed. I did not try the keys but I would like to be

Greetings all. Due to security concerns we are switching our backup processes from "SSH tunnel to rsync daemon" to "Running rsync over ssh in --server mode". In daemon mode we had a nice conglomerate log file of all of the backups that ran. Now that I am tweaking the scripts to run over --server mode I see that by default there is no remote logging. From what I have read on

We are strategizing a set of backup servers and I have been trying to deduce wha the maximum size of each RAID 5 array should be to match the OS we are using. We are currently running CentOS 4.3 64 bit. We have planned a 2 TB RAID 5 array for testing but we will need to set up several larger ones for production. I have poked around and I see people mention limits like 2TB max file size and 32TB

I saw in the rsync.d documentation that there is a perl script to parse the default log format for tranferred files. Is there a utility out there that will handle the server/client log files even if you chaneg the format around? thanks Doug -- What profits a man if he gains the whole world yet loses his soul? -------------- next part -------------- HTML attachment scrubbed and removed

I wanted to start a new thread for this aspect instead of continuing my previous in case others have similar questions. I am running an rsync command that will have the --server option appended automagically by rsync. However I do notice that other default options go along with it. This is what i am seeing: rsync --server -vlogDtpr --log-format=%o Is there a way to keep these from appearing

Hello, I'm desperately trying to have a RSync server work on a Windows 2003 Standard Server. All the documentation available I have found applies to Windows NT/2000/XP I don't know whether 2003 works differently from the previous Windows. I have installed the cwrsync package. The RSyncServer Service is running fine under a user account named cwrsync. A successful Telnet on the port 873

I'm having prolems with cwRsync on server 2003. I'm getting pretty much identical results to this from the archive: http://lists.samba.org/archive/rsync/2004-April/009187.html, and as far as I can see the only suggestion there was to check permissions. I have one further complication too- I'm trying to sync a remote server on to a vmware virtual disk that I've mounted using the

I installed the newly released version of cwRsync today on a few Windows machines and have noticed a new problem that I have not seen mentioned anywhere. When syncing to an NT machine used for backups, my rsync client exited at the end of the transfer with the following message to standard error: multiplexing overflow 1:296 [sender] rsync error: error in rsync protocol data stream (code 12)

Good day, I have been doing some tests with rsync on windows (client) to backup to a linux server. I started out with cwrsync, but ran into the dreaded "File name too long (91)" error. Apparently due to an issue with the cygwin portion of it. So I was then testing with a newer version of cygwin (1.7 beta) as the long file name issue was resolved. In testing that with some

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi: First let me say that rsync/cwrsync is amazing ! And sorry ! if I'm bothering you with this question... I need to sync my work files from the WinXP Pro machine to our Solaris one... so far so fine.. My problem is when I specify the path on the rsyncd.conf (cwrsync) I have tried many combinations from:

I believe this post I found is related to a problem I'm having with long files names...I would like to use cwRsync, does my problem suggest this is still happening and has not been addressed? http://lists.samba.org/archive/rsync/2005-April/012117.html However, I have long file name issues using rsync 2.6.6 from a BSD server to the default Cygwin rsync 2.6.6. Should I (and how do I) apply

I'm using cwRsync which incorporates rsync-2.6.7 with Cygwin. I've got it set up as a server and it works for local directories but when I try to set up a module with path /cygdrive/m/dirname it tells me that it can't chdir to that path, error 2, no such file or directory. I copied Cygwin mount and ls to the machine and mount reports that /cygdrive/m is indeed there, and ls can

Hi, Some explanations regarding cwRsync: cwRync installers (both client and server) are now available as a paid download bundle. Installer sources, however, are still available as free upon contact. Please keep in mind that installer sources are not enough to build cwRsync installers: You need to build up a complete Cygwin environment, compile/copy binaries in the package. It may be time

Hi folks, It may be a very basic question for many people here but I have been struggling with Windows commandline. My CentOS machines are running perfectly fine. Question: I have installed cwRsync server on one of Windows 2003 and cwRsync client on the other Windows 2003. What command should I run to connect to the cwRsync server from the client? and how can I make sure that cwRsync is even