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
On Dec 5, 2007 9:59 PM, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-12-04 at 15:59 -0500, Doug Lochart wrote:
> > Greetings all. Due to security concerns we are switching our backup
> > processes from "SSH tunnel to rsync daemon" to "Running rsync
On Dec 6, 2007 12:52 AM, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-12-05 at 23:21 -0500, Doug Lochart wrote:
> > Now I am having another issue and that is passing a log format in the
> > rsync-path. I can see it is coming over but for some reason a defauly
&
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
Nevermind. I figured it out after some trial and error. Basically I have
my forced ssh command script intercepting the rsync call and setting the
parameters myself.
Thanks all of for your help. I still may have more questions but so far it
is looking good!
Doug
On Dec 7, 2007 2:29 PM, Doug
Matt,
Questions for you based on your earlier response
>
> Anyway, it's easy do a secure rsync daemon setup with ssh connections
> and authentication. Make a separate daemon configuration file for each
> user listing only the modules he/she is allowed to access. Then set
> each user's forced co
More often than not it is a permissions issue. The private-key that
you use must have permissions set to 600. Try separat8ng the problem
by just using ssh (no rsync). try this:
ssh -vvv -i your-private-key -l your-username 192.168.x.x (or whatever
the host is)
Look at the verbose output and se
We have hit the same problem and what we found out was that Vista
changed something and either rsync or cygwin can't determine the
permissions and so nothing (or null) is sent across and this seems to
cause the directory to be created this way. We have only seen this on
Vista and have since backed
You are correct and I am out of the loop. Evidently the client
developer used this approach to solve our Vista problem but I either
forgot or was not informed. Probably the former =)
On Jan 30, 2008 1:45 PM, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-01-30 at 13:09 -0
That is what we did albeit a little differently and then I wrote a
Perl script to parse it and give me what I want.
On Feb 6, 2008 3:54 PM, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> On Wed, 2008-02-06 at 21:34 +0100, Mojca Miklavec wrote:
> > we're running an rsync on a server and would like to
My experience working with a Windows client with a Windows Server has not
been all that great. In most cases it is not the client itself it is just
the typical pain that you experience when trying to run an open source
product on Windows. Our biggest issues with using the windows client and
serve
Not trying to sound harsh or anything but this issue has been discussed at
length in the list over the past 3 years. PLEASE search through the
archives. When searching try searching on the word ROBOCOPY as that is an
often suggested means of handling windows ACL's.
2009/6/25 dir_teh
> hi Srini
ch in advance
Doug Lochart
--
What profits a man if he gains the whole world yet loses his soul?
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
On 3/1/06, Peter <[EMAIL PROTECTED]> wrote:
>
> --- Doug Lochart <[EMAIL PROTECTED]> wrote:
>
> > Windows (cw)Rsync Client --> Linux Rsync server
> >
> > 1) Should we abandon cwrsync for cygwin + rsync?
> > Have the
> > disparities between
Thank you for your insight. It has been very beneficial!On 3/2/06, Tevfik Karagülle <[EMAIL PROTECTED]> wrote:
> 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> interest
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?
thanksDoug-- What profits a man if he gains the whole world yet loses h
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
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 pat
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.7Our method of transport is opening a
ey are set properly
i.e 100BaseT, 1000BaseT.Any other ideas?If I did not mention this before, it is not consistent and we have not been able to reproduce it at will.thanksDoug
On 5/10/06, Wayne Davison <[EMAIL PROTECTED]> wrote:
On Wed, May 10, 2006 at 02:35:47PM +0000, Doug Lochart wrote:> C
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
We were trying to introduce a better client side log format so that we could get timestamps and module names etc. In the rsync documentationit 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.
22 matches
Mail list logo
