similar to: rsync --rsh not reading .ssh/config

A while back I argued for adding a --with-rsh=CMD option to configure and got some general agreement that it would be a good thing (especially for systems that don't have rsh at all). However, the changes were never integrated into rsync. This patch adds the --with-rsh=CMD option to configure and modifies main.c to improve the blocking-IO setting code. The old code would set blocking_io to

>From what I understand, the problem is due to people's disagreement about what the "correct" behavior should be. I'm pretty sure that the following is the correct behavior from running rsh and ssh often (both fsecure and openssh). Lets say you have a stupid script that does while 1 do sleep 1 done Called foreverSleep on your remote host: rsh remotehost

On Mon, Dec 15, 2003 at 10:51:08AM -0800, Wayne Davison wrote: > On Mon, Dec 15, 2003 at 10:03:28AM -0800, jw schultz wrote: > > > The one thing i really would have liked to have seen in a version bump > > would have been changing the default remote shell to ssh instead of > > rsh/remsh. > > I can see this being both a good thing (since I think it is a better >

Hi, I have installed rsync-2.4.6 version on Linux Redhat 6.2 (Kernel-2.2.14-5.0), after installed I tried to test the rsh and run "rsh remotehost /bin/true > out .dat". But it failed the error message was "Permission denied". I checked the permission all was okay, I forgot the rsh/csh methods and replaced by RSYNC_PROXY. Finally, it failed again. I would like to know that

I'm new on rsync, and I have some question regarding file synchronization my rsyncd.conf is secrets file = /etc/rsyncd.secrets read only = yes list = yes uid = nobody gid = nobody max connections = 1 log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [test] path = /home/test auth users = test on another linux, I executed rsync --verbose --progress

https://bugzilla.samba.org/show_bug.cgi?id=1924 Summary: unable to rsync between a PC with cygwin and a unix machine using rsh Product: rsync Version: 2.6.3 Platform: x86 OS/Version: Windows 2000 Status: NEW Severity: major Priority: P3 Component: core AssignedTo:

I have a problem getting key authentication to work with one remote user (git), even though it works fine for the remote user "root". The remote file .ssh/authorized_keys is identical for both users - I cp'ed it from the root account to the git home dir. On local machine (OS X, by the way) I have: $ cd $ ls -l .ssh -rw------- 1 jussihirvi staff 668 Aug 24 16:13 id_rsa (the

Hi, This is perhaps a stupid question. I apologize in advance if it's already been covered, but I'm stumped... I'm using rsync to backup some file systems to a remote host. The transport is openssh-2.9.9p2. The problem does not occur when the transport is rsh. I'm invoking rsync as follows: rsync -RlHptgoD --numeric-ids -e "ssh" -rzx --stats .

I want to replicate between two Solaris hosts. The source is Solaris 2.6 and the target is Solaris 2.8. Using rsh, the basic program seems fine (not running in daemon mode), but I have a problem. The directory tree is about 150,000 files, with about 5 gb of data. I tar'd the directory and moved it to the other side, but when I run an rsync against that directory, it still wants to move

Hi all, I've a particular host on my network that when I run; rexec -l username -p password remotehost command it just hangs. When I do; rexec -a -l username -p password remotehost command i get; Where are you? If I do; rexec -l username -p password localhostname (not just localhost but its actual name) command it works. Any ideas would be very appreciated. - aurf

I'm migrating from C7 to C8.? I'm currently using autofs, but alas autofs has been dropped in C8 for the AMD automounter. I have some very ancient knowledge of AMD, I used it when it was first introduced many years ago on Solaris and moved to Sun's automounter when it was introduced. So now it's back to square one. I used automount2amd to convert one of my existing maps,

Hi All! I am puzzled. I am using openssh 5.3p1 on RHEL/CentOS but am seeing the same behaviour for osx and debian: ssh -R xxx:yyy:yyy:yyy remotehost Will effectively drop the first (xxx) argument and result in ssh -R 127.0.0.1:yyy:yyy:yyy remotehost ssh -R yyy:yyy:yyy remotehost I had a look at the source code where apparently all 4 values are ready and handed down to the appropriate

This is frustrating: $ export LIBVIRT_DEFAULT_URI=qemu+ssh://remotehost/session $ virsh list error: failed to connect to the hypervisor error: no valid connection error: Operation not supported: Connecting to session instance without socket path is not supported by the ssh connection driver Has there been any thought given to making this easier? It seems that having a simple helper

We try to run a reliable ssh tunnel vis systemd. This is the unit configuration file: {{{ [Unit] Description=Tunnel For %i After=network.target [Service] User=autossh ExecStart=/usr/bin/ssh -o "ExitOnForwardFailure yes" -o "ServerAliveInterval 60" -N -R 40443:installserver:40443 -R 8080:installserver:8080 ExecStartPre=-/usr/bin/ssh tunnel@%i "for pid in $$(ps -u

Unless told otherwise, rsync uses rsh to contact the remote system.=20 Another popular option is ssh. Both of these protocols use the logged-in=20 username, unless specified otherwise. What rsync really does is "rsh=20 remotehost rsync --server-and-other-undocumented-options". If you can't=20 "rsh server rsync --version", rsync won't work with rsh. Same with ssh. I

There is no /root/.ssh/authorized_keys on remote host, so I have to authenticate with password. On the remote host: # /usr/sbin/sshd -T | egrep permitroot permitrootlogin yes Attempting: $ ssh root@<remotehost> shows: Received disconnect from <remotehost> port 22:2: Too many authentication failures for root packet_write_wait: Connection to <remotehost> port 22: Broken

Hi, Been using rsync for many years but I'm stuck with this problem. I'ts a simplistic backup using rsync from a Windows 2k3 machine to a Linux box out on the 'net, using pre-shared ssh keys. In this case I'm saving, files belonging to various users, using the administrator account on the windows machine and the destination is a normal user account and its home file area.

Hi, I found that current rsync versions do something different when using --one-file-system --relative and --delete. This has all worked as expected with the old version (in our case those delivered with RHEL4 and 5) but it doesn't work correct in the 3.0.x version. I have opened a bug at RedHat because it's at least a regression for their upgrade from EL5.6 to EL5.7 which updated to

Hi, Not sure when this stopped working, because I'm sure it used to. This is the cygwin build of rsync, with the standard cygwin rsh (which is a fairly old GNU inetutils 1.3.2). ~=> rsync --rsh=rsh -vv bibble: opening connection using rsh bibble rsync --server --sender -vvr . rsh: unknown option -- server Try `rsh --help' for more information. rsync: connection unexpectedly closed

https://bugzilla.samba.org/show_bug.cgi?id=1924 wayned@samba.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From wayned@samba.org 2004-10-13 09:09