17 februari 2010 23:17
Aan: 'rsync at lists.samba.org'
Onderwerp: RE: Rsync / ssh high cpu load
Hi again,
Still working on this one. When I rsync/ssh a big file to my server over the
local network (100Mbit/s) with the --bwlimit=1000 I only have a small CPU
load. SSH takes about 10% and rs
ericht-
Van: Jan Alphenaar [mailto:jan.alphen...@dotcolour.com]
Verzonden: woensdag 17 februari 2010 23:17
Aan: 'rsync@lists.samba.org'
Onderwerp: RE: Rsync / ssh high cpu load
Hi again,
Still working on this one. When I rsync/ssh a big file to my server over the
local network (100Mbi
...@dotcolour.com]
Verzonden: woensdag 17 februari 2010 12:17
Aan: 'rsync@lists.samba.org'
Onderwerp: RE: Rsync / ssh high cpu load
Hi,
In an attempt to narrow this down a bit I installed a RedHat machine with
openssh-5.3p1 and rsync-3.0.7 and did the same test as below.
Transferring dat
Hi,
On Thu, 18 Feb 2010, Henri Shustak wrote:
Although there is a small version difference in the rsync versions, I would
say that this is caused by the cygwin layer.
When using rsync over SSH you may find that the CPU load is substantial
depending upon multiple factors including but not lim
> Although there is a small version difference in the rsync versions, I would
> say that this is caused by the cygwin layer.
When using rsync over SSH you may find that the CPU load is substantial
depending upon multiple factors including but not limited to your processor,
disks and network.
Ho
Hi,
In an attempt to narrow this down a bit I installed a RedHat machine with
openssh-5.3p1 and rsync-3.0.7 and did the same test as below.
Transferring data, both up and downstream, are not giving me any CPU load.
Although there is a small version difference in the rsync versions, I would
say t
On Thu, 16 Jul 2009 08:47:17 -0700, Laurent Luce wrote:
> I am looking into redundancy now. Does anyone use a similar setup and
> has redundancy. I am looking for some advices.
I'm not clear to what redundancy you're referring. Files common to
multiple clients? Files unchanged from copy to cop
Title: RE : Rsync + SSH on a different port + restricted access
Thanks, it worked nice !
Best regards
Johan
Message d'origine
De: Julian Pace Ross [mailto:[EMAIL PROTECTED]]
Date: lun. 04/09/2006 10:14
À: BOYE Johan
Cc: rsync@lists.samba.org
Objet : Re: Rsync + S
I found that adding the following at the beginning of the key on recv. side works perfectly for me with any rsync command on the sending side.
from="10.1.1.1",command="/home/remoteuser/cron/validate-rsync" ssh-dss B3Nza
C1kc3MAAAEBAKYJenaYvMG3nHwWxK... etc...then create the file "validate-rsync
have 'almost' the same version of OpenSSH/SSL and
> RSYNC on both computers...
>
> Good luck
>
> Johan
>
> > -Message d'origine-
> > De : [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] De la
> > part de Shachar Shemesh
> >
de Shachar Shemesh
> Envoyé : jeudi 6 avril 2006 13:52
> À : khabot
> Cc : rsync@lists.samba.org
> Objet : Re: rsync, ssh and DSA key
>
> khabot wrote:
>
> >Thanks for your response
> >I have done this, but I execute
> >
> >
>
khabot wrote:
>Thanks for your response
>I have done this, but I execute
>
>
>>>rsync -avz -e ssh [EMAIL PROTECTED]:/var/mail/ /var/mail
>>>
>>>
>It still askin me for the root password in 10.78.0.117 and for the
>passphrase i, 10.78.0.107
>thank you to help
>
>
Your problem probably has
Thanks for your response
I have done this, but I execute
> > rsync -avz -e ssh [EMAIL PROTECTED]:/var/mail/ /var/mail
It still askin me for the root password in 10.78.0.117 and for the
passphrase i, 10.78.0.107
thank you to help
On Wed, 2006-04-05 at 20:23, Bob Hutchinson wrote:
> On Wednesday 05
On Wednesday 05 Apr 2006 16:41, khabot wrote:
> hi all
> I have generated the key in the source server(10.78.0.107)
> ssh-keygen -t dsa -C "[EMAIL PROTECTED]"
> I have added this key to authorized_keys2 of the destination
> server(10.78.0.117)
> cat id_dsa.pub >> /root/.ssh/authorized_keys2
check
On Sun, Mar 06, 2005 at 10:45:01AM -0600, michael mendoza wrote:
> [EMAIL PROTECTED] desc]# du -sh
> 52K .
>
> machine:/home/mike/Desktop/desc# du -sh
> 24K .
>
> I don't understeint that, why? in the source is 52 k
> and in the destination is 24k
John mentioned the various things that
Hi, i don't write so much englisk, look at this>
~in the same line
#rsync -avz --stats -e ssh desc ~
[EMAIL PROTECTED]:/home/mike/Desktop/
Password:
building file list ... done
desc/
desc/prueba/
desc/prueba/a
desc/prueba/b
desc/prueba/p/
desc/prueba/p/c
desc/prueba1.tar
Number of files: 7
Numb
(Email attachment quoted for the benefit of the mail archive...)
On Thu, 3 Mar 2005, michael mendoza <[EMAIL PROTECTED]> wrote:
>
> Hi, thank again.
>
> I used rsync today to copy 400 MB from a pc to other
> pc with rsync -avz -e ssh SourceDir
> [EMAIL PROTECTED]:/dirDest/
>
> but in the source
Nota: Se adjuntó el mensaje reenviado.
_
Do You Yahoo!?
Información de Estados Unidos y América Latina, en Yahoo! Noticias.
Visítanos en http://noticias.espanol.yahoo.com--- Begin Message ---
Hi, thank again.
I used rsync today to copy 400
On Mon, Feb 28, 2005 at 10:51:32PM -0600, michael mendoza wrote:
> rsync -avzpogl -e ssh archivoOrigen [EMAIL PROTECTED]:/dir2/
> but when a see in the new server, the data dont have the same permiss
> of owner, group than the old server.
The problem is that rsync need to be running as root in ord
On Thu, Oct 07, 2004 at 11:18:03AM -0600, Ryan Sommers wrote:
> After sending the first mail I was able to get it to work by adding
> '-e ssh' to the command line and changing '[EMAIL PROTECTED]:/path/to/stuff' to
> '[EMAIL PROTECTED]::module'.
Yes, that is the other choice if you want to restrict
Wayne Davison said:
> On Thu, Oct 07, 2004 at 10:20:34AM -0600, Ryan Sommers wrote:
>> Edited authorized_keys on M adding 'command="sudo /usr/local/bin/rsync
>> --server --daemon ."'
>
> You can't start an rsync daemon and then attempt to do a non-daemon
> transfer. Get rid of the "command" settin
On Thu, Oct 07, 2004 at 10:20:34AM -0600, Ryan Sommers wrote:
> Edited authorized_keys on M adding 'command="sudo /usr/local/bin/rsync
> --server --daemon ."'
You can't start an rsync daemon and then attempt to do a non-daemon
transfer. Get rid of the "command" setting above and tell rsync to
run
Yessos, very cool.
It works even with
rsync -auv -e "ssh [EMAIL PROTECTED] ssh" src_folder host_C:sdt_dir
Sometimes solutions can be very simple...
Unfortunartely all open positions for email postmasters are just filled
in. I did my best to convince my boss, you were better, but it didn't
work.:)
Haai Andrzej,
The problem is solved. When I double checked the ssh-b file I realized
I had to change the linux commands to cygwin commands.
>From that moment all commands (like date, hostname...) worked on the
C-host
So with the key authentification and the following ssh-b script:
#!/bin/bas
Stefaan Lhermitte wrote:
Indeed, I want to:
* to start rsync session A->C
* cannot establish ssh session A->C (firewall)
* but can establish ssh session A->B and B->C
I think I understand the ssh hop. If I'm correct. I make a script file
ssh-b that I subsequently invoke in the rsync command (./ssh
Indeed, I want to:
* to start rsync session A->C
* cannot establish ssh session A->C (firewall)
* but can establish ssh session A->B and B->C
I think I understand the ssh hop. If I'm correct. I make a script file
ssh-b that I subsequently invoke in the rsync command (./ssh-b).
Unfortunately I sti
On Wed 08 Sep 2004, Stefaan Lhermitte wrote:
> I tried to connect the tunnel with another port number. When I use port
> number 22 instead of 873 I can telnet to C from B.
> When I telnet I get "SSH-1.99-OpenSSH_3.9p1."
Yes, because you are connecting via the tunnel to the ssh server on C
> Su
Stefaan Lhermitte wrote:
I tried to connect the tunnel with another port number. When I use
port number 22 instead of 873 I can telnet to C from B.
When I telnet I get "SSH-1.99-OpenSSH_3.9p1."
Subsequently I ran: ssh -v -L 22:C-computer:22 [EMAIL PROTECTED]
When I run now the rsync command:
r
I tried to connect the tunnel with another port number. When I use port
number 22 instead of 873 I can telnet to C from B.
When I telnet I get "SSH-1.99-OpenSSH_3.9p1."
Subsequently I ran: ssh -v -L 22:C-computer:22 [EMAIL PROTECTED]
When I run now the rsync command:
rsync -v /cygdrive/d/fol
Nope, I cannot telnet port 873. I tried "telnet C-computer" and "telnet
C-computer 873" but command give the error:
Connection refused.
On the other hand, the SSH command from B-computer to C-computer works
does give connection without any problems.
Thanx in advance,
Stef
Andrzej Filip wrot
Stefaan Lhermitte wrote:
I'm trying to rsync my labtop pc (let's assume A-computer) with my
desktop pc (let's assume C-computer) through our firewall.
In between there is one computer (let's assume B-computer) that has an
open port, so I theoretically could connect via a tunnel.
I checked the SSH
On Mon, Jun 21, 2004 at 01:56:29PM -0600, Tim Conway wrote:
> I've known of people running a rsyncd binding on localhost and
> tunneling, when they were afraid of getting sniffed. I assume this is
> just an automation of that process?
No, it uses ssh to run its own daemon process. It's just so t
Well, whaddya know? I've known of people running a rsyncd binding on
localhost and tunneling, when they were afraid of getting sniffed. I
assume this is just an automation of that process? I guess it's time to
reload my mental copy of the man pages.
Tim Conway
Unix System Administration
Cont
According to the manpage and other docs, it also
possible to use ssh to connect to a daemon using
"::". However, you must use the --rsh="ssh ..."
option instead of the -e.
"o for copying from the local machine to a
remote machine using a remote shell program as the
transport, using rs
That's an ssh problem, not rsync.
try "ssh xx.yy.zz".
That said, ssh is irrelevant to what you're trying to do.
you are going to a module on an rsync daemon, not a directory through a
remote shell transport connection.
:: is an rsync-protocol TCP connection to port 873, not an ssh-protocol
TCP co
Thank you for your reply -- it is very helpful and makes things
clearer to me. I will try the other approach that you have
suggested, i.e., making the cron jobs part of the same process
group.
Thanks again,
Itay
On Thu, 11 Mar 2004, Larry Brasfield wrote:
> Itay Furman wrote
Itay Furman wrote:
> Hi,
Greetings.
> My ssh set up, on both 'work' and 'home' machines uses the
> private-public key authentication (key uses non-empty
> passphrase). So from the 'home' shell prompt the following
> works without prompting to password or passphrase:
>
> rsync -avz --delete -e
On Wed, Feb 04, 2004 at 03:26:19PM +, Paul Simpson wrote:
> [EMAIL PROTECTED] root]# rsync --rsh="ssh -lpaul" clinton::
> [EMAIL PROTECTED]'s password:
> rsync: server sent "" rather than greeting
It's probably your ssh setup outputting something. Try this:
#!/bin/sh
out=`ssh -lpaul clinton
On Thu, 4 Dec 2003, Michael <[EMAIL PROTECTED]> wrote:
> I know that with ssh I can issue the -i command to use a different identity.
> Is there anyway to use the -i command with rsync and ssh? Thank you.
>
> Michael
In addition to what Martin suggested, you can also include the -i option
and it
On 4 Dec 2003, Michael <[EMAIL PROTECTED]> wrote:
> I know that with ssh I can issue the -i command to use a different identity.
> Is there anyway to use the -i command with rsync and ssh? Thank
> you.
Use the IdentityFile and Host keywords in your ssh_config:
Host suzy-alt-key
HostName suz
ch1.5-1
zlib 1.1.4-1
Use -h to see help about each section
Thanks,
--
Mike Oswell
-Original Message-
From: Lapo Luchini [mailto:[EMAIL PROTECTED]
Sent: May 31, 2003 12:29 AM
To: Oswell, Michael
Cc: '[EMAIL PROTECTED]'; CygWin
Subject: Re: Rsync / SSH
> >Cygwin is installed on both systems and works perfectly. OpenSSH is
> >installed and running, and the rsync user we created is able to ssh using
> >password-less keys between the 2 systems. When I run rsync, it correctly
> >pulls the data down that I want. The problem is that there are NO
> >
On Sat, May 31, 2003 at 09:48:47AM +0200, Lapo Luchini wrote:
> Actually it seems to me the opposite: it has perms also without -p...
> maybe it is the default?
Without -p new files get perms of source as modified by
umask.
--
jw schultz wrote:
Hey cygwiners have you no comment?
I think this is a cygwin limitation. Perms are probably
not supported. With -p it will use whatever perms stat
returned (apparently ). I'm not sure why you are
getting a 0200 mode.
I asked Micheal Oswell for more details because perms ar
Oswell, Michael wrote:
[sorry for the full quote, but I'm CCing the cygwin mailing list too]
I am attempting to use rsync to "mirror" data between several windows 2000
and windows XP systems. I am a UNIX person by nature, so decided the
easiest way to go about doing this would be to use Cygwin wit
On Thu, May 29, 2003 at 10:02:02AM -0700, Oswell, Michael wrote:
> I am attempting to use rsync to "mirror" data between several windows 2000
> and windows XP systems. I am a UNIX person by nature, so decided the
> easiest way to go about doing this would be to use Cygwin with cron and ssh
> runni
Guess I was rushing a bit too much. I did get the source command in right
in one of my tests, but not another. For some reason, it still fails when
I put it in root cron, but it does now work with the system crontab
(where the user is set as root). I think I'll just accept that oddity and
use the
Thank's, that's exactly what I'm looking for! -- I think.
I've gotten it installed in root (.bashrc and .bash_profile), and I've got
it working so that whenever I open a new Xterm, I can ssh to the remote
without getting a passphrase request, but . . . the cron script still
hangs. From reading
by: [EMAIL PROTECTED]
06/24/2002 01:31 PM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
(bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:Re: Rsync ssh script execution fails under cron?
Classification:
After that warm response, I decided to try for anothe
On Mon, Jun 24, 2002 at 03:31:58PM -0400, Jeff Hill wrote:
>
> My intent was to avoid the security issues of logging into a remote server
> as root without a password or passphrase. At this stage, I'm willing to
> fall back to trying ssh keys without a passphrase. Again, easy enough to
> imple
After that warm response, I decided to try for another day to get a script
working, to no avail.
Yes, a blank line and a "set -x" might be required (but certainly not
always required for all cron scripts). It made no difference here, so far.
As for the commands you didn't recognize (log_user,
On Mon, Apr 29, 2002 at 06:53:54PM -0400, Administrator wrote:
> I am trying to use rsync over ssh to a specific port and am having no luck. Any
>help would be greatly apprecaited.
>
> This is what I have:
>
> rsync --delete -rlogptvz -e ssh /tmp [EMAIL PROTECTED]:/home/safe/backup/
>
> If so
On Mon, Apr 29, 2002 at 06:53:54PM -0400, Administrator wrote:
> If someone could show me how to tell rsync to use a specific ssh port I would really
>appreciate it.
One solution would be to create an ssh wrapper script, like this:
#!/bin/sh
exec ssh -p "$@"
and refer to it instea
I'm new to this mailing list so a short intro: My name is Drew Streib,
and I work for VA Linux/SourceForge.net as, among other things, the
ftp.sourceforge.net mirrors and distribution guy.
On Mon, Mar 26, 2001 at 10:47:36AM -0600, Dave Dykstra wrote:
> I understand, but I don't think those consid
On Wed, Mar 21, 2001 at 05:16:13PM +, L. Cranswick wrote:
>
> > On Tue, Mar 20, 2001 at 09:06:03PM -0800, Lachlan Cranswick wrote:
> > > Not sure if this was answered in the recent flurry of postings but
> > > what is the status on putting a cut-down version of ssh inside
> > > rsync to allow
> On Tue, Mar 20, 2001 at 09:06:03PM -0800, Lachlan Cranswick wrote:
> > Not sure if this was answered in the recent flurry of postings but
> > what is the status on putting a cut-down version of ssh inside
> > rsync to allow an "easy" encryption option?
>
> I don't recall anybody suggesting tha
On Tue, Mar 20, 2001 at 09:06:03PM -0800, Lachlan Cranswick wrote:
> Not sure if this was answered in the recent flurry of postings but
> what is the status on putting a cut-down version of ssh inside
> rsync to allow an "easy" encryption option?
I don't recall anybody suggesting that exactly. I
Well, here is how I enabled passwordless login on from my debian 2.2 box
to itself to test MPICH stuff:
First, be sure ~/.ssh/authorized_keys files is not group writable, and
contains the identity which is to be allowed to perform passwordless
logins.
In case there is something atypical in my s
58 matches
Mail list logo
