Displaying 20 results from an estimated 11000 matches similar to: "how about auth users without a password?"
2004 May 05
5
rsync and Perl programming
Hi everybody -
I'm trying to write a Perl wrapper for some rsync tasks that need doing.
Problem is, there's some sort of odd interaction going on between Perl
and the daemon mode communication for the rsync client, and I'm at my
wit's end in trying to figure it out.
Here's the Perl script:
#####################################################
2004 Jul 15
3
Rsync not preserving owner/group
For some reason when using -owner -group my files end up being nobody:nobody
on the destination..?
This is Solaris 9.
Jeremy S. Loukinas
2003 Dec 24
2
Getting Started (Trying)
I have configured my rcyncd.conf file and it is stored in /etc.
Whne I type in the command rsync --daemon, nothing happens.
Whats wrong? I type in netstat to see if I can see port 873 being
used but there is nothing. Here is my conf file
log file = /var/log/rsyncd.log
[home]
path = /vmfs/Storage
comment = My Home Area
list = yes
read only = no
I am new to linux and rsync. Using
2006 Apr 01
3
issues with password-file
I have rsync daemon running on a fedora core 4 box that I am trying to use
as a backup server for my web sites. I dont have shell access on my web
host so will need to run a cron job to do the backups, which is what I want
to do anyway.
For testing purposes however I am using a php script using the "system()"
function so I am getting some feedback.
In my rsyncd.conf file I have the
2004 Mar 16
2
Rsync 2.6.0 compile problem
I am trying to compile rsync-2.6.0 on BSD/OS 5.0
patched to current level. gcc version 2.95.3
I ran configure: ./configure --with-rsh=rsh
This is the only error message given by configure:
checking sys/sysctl.h usability... no
checking sys/sysctl.h presence... yes
configure: WARNING: sys/sysctl.h: present but cannot be compiled
configure: WARNING: sys/sysctl.h: check for missing prerequisite
2004 Apr 22
1
Problem with ownership of non-root files at destination
I'm using rsync to mirror my Sharp SL-5500 Linux PDA
home directory to my Linux desktop over a
TCP/IP-on-USB link.
I'm running the following command as root on the 5500:
/home/QtPalmtop/bin/rsync -av /home/zaurus \
192.168.129.1::zaurus
I'm running the rsync server out of xinetd. I have
verified with 'ps' that the server, when it starts, is
running as root. The files are
2004 Mar 25
3
Root access over ssh?
Is it possible to configure rsync in server mode, to gain access to root
protected files, without the user having to log in as root through ssh?
I'd prefer to login as a regular user through ssh and access an rysnc
server on the host that's running as root. As far as I can tell,
however, that's not possible...am I wrong?
2004 Apr 16
2
RSync on Windows 2003
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
2004 Mar 11
1
rsync + ssh: fails from cron
Hi,
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 ssh remote.work.machine:publicats $HOME/work
>From cron, however, I am prompted for a password, though.
I have seen
2003 Sep 08
1
continuing broken pipe problems
Hello all -
I am running rsync 2.5.6 on two FreeBSD 5.0 machines. I have experimented
with running rsync using ssh, with command lines like the following:
rsync -rv --progress jimbo@192.68.100.10:/usr/share/smbshare
/usr/home/jimbo
And also with running rsync as a daemon on the master server, and syncing to
it from the other machine like so:
rsync -rv --progress 192.168.100.10::test
2003 Oct 09
4
howto enable ssh on connect to rsync daemon
Hi,
I'm trying to setup automatic sync of files over SSH from node2 to node1.
node2 is the "server" and node1 is the "client".
I have setup rsync like this on the nodes which runs AIX (4.3.3 and 5.1):
1. Installed rsync from Linux Toolbox (rsync-2.5.4-1.aix4.3.ppc.rpm) on both nodes.
2. Added following to both nodes /etc/services file:
rsync 873/tcp
3. Added
2003 Aug 21
3
authentication error
I have setup a Rysnc server in Mandrake 9.1
When I add a auth user into my Rsync.conf and rsync.secrets,
it do not work, everytime it shows
[root@html]# rsync chris@mandrake82::XXXXX/.html/. /
Password:
@ERROR: auth failed on module XXXXX
rsync: connection unexpectedly closed (89 bytes read so far)
rsync error: error in rsync protocol data stream (code 12) at io.c(165)
This is my rsync's
2015 Apr 09
3
rsync error: error allocating core memory buffers
Hi,
I've configured 'backuppc' to transfer files via rsyncd, with enabled
checksums. Whith one of the shares I get the error (in syslog):
---------------------------------------------------------------------
robbe rsyncd[2183]: ERROR: out of memory in receive_sums [sender]
robbe rsyncd[2183]: rsync error: error allocating core memory buffers
(code 22) at util2.c(106)
2007 Jul 12
1
rsyncd.conf missing option akin to --one-file-system
It seems to me that rsyncd.conf does not provide an option akin to rsync's
--one-file-system command line argument. If that is true, it seems like a
bug of ommission, as I now face a use case where I need it.
Is there maybe some technical reason for the ommission?
Thanks,
--
Lester Hightower
2008 Aug 05
1
rsync problem after ssh upgrade
Hello.
In my setup I collected logs from many hosts using ssh + rsync. It
worked fine untill I upgraded OpenSSH from version 5.0p1 to 5.1p1 on those
hosts running Slackware Linux. After upgrade nothing works as before. When
I try to get logs connection breaks with the following message in syslog
on the server side:
Aug 4 15:34:44 srvhost sshd[8130]: Accepted publickey for user from
2009 Mar 30
1
is it possible to continue rsync after network interruption?
I rsync a remote destination which has a daily network interruption of round
about 5 minutes.
Is it possible to configure rsync to wait in such a case this 5 minutes and
continue the rsync as soon as the network connection is established again?
I use rsyncd with perl::rsync (backuppc) through a ssh tunnel.
Thanks
Matthias
--
Don't Panic
2003 Dec 30
5
Question about file ownership on destination
Hello
Regarding ownership on the destination:
rsync's man page indicates that when synchronizing files to a remote host,
-o implies the --numeric-ids option, which makes perfect sense aince the
named users/groups may not exist on the destination host. The problem I
have is that the files created on the destination still appear to be owned
by the local user (server1) on the rsync
2008 Mar 10
2
The server is configured to refuse --iconv
I've just tried upgrading to cwrsync 2.1.0 (Rsync version 3.0.0 protocol
version 30) between 2 Windows XP Pro sp2 machine across the Internet.
I used:
SET CYGWIN=nontsec
SET HOME=c:\cwrsync\bin
C:\cwrsync\bin\rsync -za -u -P --delete --recursive /cygdrive/c/test2/
stuart@test.address.co.uk::test/
When I run the above batch script on the remote machine I get this odd output.
2001 Oct 23
1
Connection Timeout
This is my first post so first of all I will say hello to everyone.
I have rsync configured and working properly on my local network however
when I try to connect from a remote host (one located in a different state)
the connection times out. I was wondering if there was another way to set
the timeout besides in the rsyncd.conf file?
As I said the connection works fine on the internal lan, but
2014 Dec 03
4
Aw: Re: encrypted rsyncd - why was it never implemented?
from a security perspective this is bad. think of a backup provider who wants to make rsyncd modules available to the end users so they can push backups to the server. do you think that such server is secure if all users are allowed to open up an ssh shell to secure their rsync transfer ?
ok, you can restrict the ssh connection, but you open up a hole and you need to think twice to make it secure