search for: lochart

...htly tar for the server but we are using CwRsync on the client. Does this patch have to be applied on the client side as well? The two errors above were coupled with 4 successful runs from the same machines. Each machine had 1 failure and 4 out of 6 rsync transfers worked. Thanks again, Douglas Lochart Cape Computing Corp -- What profits a man if he gains the whole world yet loses his soul? -------------- next part -------------- HTML attachment scrubbed and removed

...we go along without having to restart the rsync daemon or inetd service. We want this so that we can add new client machines without interfering with other clients use of the server. Is what we are trying to do workable? If so how should we run our rsync server. Thanks so much in advance Doug Lochart -- What profits a man if he gains the whole world yet loses his soul?

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

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

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

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

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 bytes total size 0 2006/03/12 22:38:26 [11631] rsync to dlochart from cygnus-x1 (127.0.0.1) 2006/03/12 22:38:26 [11631] deleting rsync-test/jj.kk 2006/03/12 22:38:26 [11631...

I have looked through the archives for this error and found some instance of it but no solutions. I have an idea for a workaround but I would like to get some clarification. 1) Unix has as a limit 256 for the length of a file name. Does this limit also apply to a fully qualified path? 2) The path we are sending over is 261 in length, I assumed that since none of the dir names or file names

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

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

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