similar to: Rsync module quota

> The benefit of rsync over ssh secured by rrsync is that it is more > like what rsync users are already used to. i don`t like rsync over ssh in an environemt with users you can?t trust. from a security perspective, i think such setup is broken by design. it`s a little bit like giving a foreigner the key to your front door and then hope that the door in the corridor to your room will be

I'm using a server (named foo) there uses qmail MTA. I.e, I've in /home directory : drwx------ user1 bar 4096 Oct 6 00:00 user1 and, under this folder, some files with 700 rights. When I'll request from another machine with a rsync client machine, just I receive the folders of user1, but empty... My rsyncd.conf in //foo/etc : [foo_home] comment = rsync on //foo

hello, I have this error while using --password-file= option. Any idea. Fran?ois tamtam:/etc# rsync --password-file=/etc/rsyncd.secrets backupcvs@cvs::cvs/ @ERROR: auth failed on module cvs rsync error: partial transfer (code 23) at io.c(143) . All seems OK tamtam:/etc# ls -ltr /etc/rsyncd.secrets -rw------- 1 root root 23 May 7 18:12 /etc/rsyncd.secrets

I set up ssh without authentication on both servers and I have tested it fine. When I do this: #/usr/local/bin/rsync --rsh /usr/local/bin/ssh --rsync-path /usr/local/bin/rsync remote_server::test /home/test rsync: unable to open configuration file "rsyncd.conf": No such file or directory rsync error: syntax or usage error (code 1) at clientserver.c(502) rsync: connection unexpectedly

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

Can anyone shed any light on what I should expect from rsync when the --link-dest option is invoked when the destination is a remote rsync module? i.e. rsync --archive --delete --link-dest=../dst_1/ /src/ user@host::xyz/dst_0 I almost expected to get a whole lot of hard links in dst_1 to unchanged files in dst_0... if I skip rsyncd on the server side (i.e. make the target

With the following server config: log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [offsite] path = /media/external/ comment = Offsite backup read only = no hosts allow = 192.168.2.0/24 auth users = backup secrets file = /etc/rsyncd.scrt uid = 0 gid = 0 I tried the following for --link-dest and they all tried to transfer all

I cannot figure out where I am going wrong with my excluded files syntax! rsync backups up those folders I'm trying to exclude. rsync -av --exclude-from=/etc/rsync_excluded.conf --delete root@polaris::polhome /pol_home_bkup cat /etc/rsync_excluded.conf - /home/agokhale - /home/anand - /home/asalazar etc. These are all top level folders with the same names. On the rsync server

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As far as a backup provider goes I wouldn't expect them to use rsync over SSL unless that were built into rsync in the future (and has been around long enough that most users would have it). I would expect them to either use rsync over ssh secured by rrsync or rsyncd over ssh with them managing the rsyncd.conf file. Either way the server side

hi I'm using rsync version 2.5.6. When i try to connect from a remote computer for example with, rsync -e ssh root@192.168.0.5:: it connects and tells me what paths are available. But when i want to connect with a normal user rsync -e ssh user@192.168.0.5:: it tells me following error message: rsync: unable to open configuration file "rsyncd.conf": No such file or directory rsync

Clean copy. I even used the -W flag to see if it made a difference but, nope. I'm testing this same test on some of my other servers too. See if there's any common-ground I can find. On another servers (MS SQL Server) with faster disks I tried a similar test just now. There's only the C drive on this server but I used my same test file from the other server and used rsync (3.1.0)

Hi. I am new to this newsgroup. I have a setup where I am rsyncing between a Windows and a Linux box. I have Rsync Server set up on each machine but so far have only been able to get Rsync Server on Linux working. I can Rsync from the Windows machine to the Linux, but not the other way around. When I try to Rsync from the Linux box to the Windows, here is the error I receive: rsync: failed to set

I have an rsync daemon running on a Windows box. It has a module called "temp" that allows users to write to a specific directory. My rsync.conf looks like: use chroot = false strict modes = false max connections = 3 hosts allow = 192.168.1.7 lock file = rsyncd.lock log file = rsyncd.log pid file = rsyncd.pid timeout = 600 refuse options = h I c a delete [temp] comment = WSS

I think you would implement it as a new type of filter rule. similar to 'P' (preserve) but with a timestamp or delta-time to define what counts as 'recent' as well as the pattern to match for this rule to apply (which could just be a wildcard matching anything by default, but could also use the full pattern-matching capabilities if required). Have a look at: the

A: do you have a "hosts allow" or "hosts deny" in rsyncd.conf? B: what version are you using? It seems i've seen messages about rsyncd in some versions refusing to allow unresolvable names in. C: Are you able to access the rsyncd, and just wonder about the log entries, or are you unable to get in? If it's just a log complaint, I wouldn't worry about it. Most

I have it up and working. for me at least. http://crypotworksapps.blogspot.com/2011/04/windows-and-linux-backups-made-dirt.html On Tue, Apr 19, 2011 at 11:00 AM, <rsync-request at lists.samba.org> wrote: > Send rsync mailing list submissions to > ? ? ? ?rsync at lists.samba.org > > To subscribe or unsubscribe via the World Wide Web, visit > ? ? ?

On Wed, Dec 3, 2014 at 9:40 AM, Tomasz Chmielewski <mangoo at wpkg.org> wrote: > rsync in daemon mode is very powerful, yet it comes with one big > disadvantage: data is sent in plain. > > The workarounds are not really satisfying: > > > - use VPN - one needs to set up an extra service, not always possible > > - use stunnel - as above > > - use SSH - is not

I've run across a situation where I have a directory of .gz files. I do want to rsync this directory. I've tried without the --compress (because they are already compressed) but the files never get rsynced. Interactively, I get the following error: :rsync error: some files could not be transferred (code 23) at main.c(1045) In the /etc/rsyncd.log, for each of the files, I get:

I have a similar problem with rsync, though it's not consistent. sometimes, things just don't come over, and sometimes, things just don't get deleted. Repeated runs usually correct it. If it's the case of a directory being replaced with a non-directory, you'll have to add "--force" to get it to happen. Hope it helps. Tim Conway tim.conway@philips.com

Hello, I just posted this a few days back and my email got totally messed up so I don't know for sure if there was any reply yet to this. If there was I would be glad if someone just could forward that to me. Thank you in advance, Stephan Hello, I downloaded that win version of rsync and I have a small question: How can I do one of the following: 1.) Add multiple syncronisation