similar to: the --owner option won't work?

I am using rsync 2.5.5 running as a daemon on the destination system, which is SuSE Linux 8.0. The source system is SuSE 7.3, also with rsync 2.5.5. With the default 'use chroot = true' and not using --numeric-ids, I get the wrong user names on the destination files. I have tracked this down to getpwnam() failing to return the user name from the passwd file. It does not fail when

On Wed, 2019-12-04 at 20:18 +0100, agents at meddatainc.com wrote: > CAUTION: This email originated from outside of the University of > Limerick. Do not click on links or open attachments unless you > recognize the sender's email address and know the content is safe. > On 11/25/2019 11:14 PM, isdtor wrote: > > > > Enable and start httpd. Write a build script that builds

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

Hi there, this is my first posting to this list, so let me quickly introduce myself. I'm Alex and currently working on a new version of the rsync package for the eisfair Linux distribution?. I have some problems understanding the behaviour of the 'auth users' option in the rsyncd.conf file when running rsync in daemon mode. I set up a module and a secrets file. This is the behaviour

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

Hi all, Tripped over a documentation bug. I'm guessing the behavior I've found isn't a bug in itself as it's kind of implied by chroot (unless the /etc/passwd db is read *before* you do the chroot call), so I'm calling it a documentation bug. The Setup: System A: running rsync --daemon from xinetd, configured with a read-only share. System B: syncing a local directory

https://bugzilla.samba.org/show_bug.cgi?id=11013 Bug ID: 11013 Summary: [patch] Mention that privileges are dropped, when "use chroot" is enabled in rsyncd.conf manpage Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5

Hello, evevryone. thank you for your mails. I used rsync(rsync-2.4.6-2) for backup Server.(My Linux is RedHat7.1) I am very comfortable backup system by rsync. but, I saw this messages in use rsyncd daemon.(/var/log/messages) I don't know mean this messages. but, It is right use rsyncd. and I used rsyncd at every day. but this messages writed log at every minute(?) or every time. What

Hello, I think i may have found a bug in the "max clients" option in rsyncd.conf [we use rsync-2.5.5; All platforms I tried (Irix-6.5.14 and various linux flavours) show the behaviour explained below] The manpage says: |max connections | The "max connections" option allows you to specify | the maximum number of simultaneous connections you | will allow to

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

Hi all, When i use rsync with on the server : motd file = /etc/rsyncd.motd log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [filieres] path = /home2 comment = Repertoire de sauvegarde des filieres read only = no hosts allow = 172.18.1.246 # vador only dont compress = *.gz *.jpg *.zip *.rpm *.tgz note : the

https://bugzilla.samba.org/show_bug.cgi?id=5166 Summary: -o -g options don't work right or I've misread the man pages Product: rsync Version: 2.6.6 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=3839 Summary: The '/' in the Softlink is missing on the remote Rsyncd server ! Product: rsync Version: 2.5.7 Platform: x86 OS/Version: Windows 98 Status: NEW Severity: normal Priority: P3 Component: core AssignedTo:

For some reason when using -owner -group my files end up being nobody:nobody on the destination..? This is Solaris 9. Jeremy S. Loukinas

Hello, I am trying to run rsync under my own userid on a high-numbered port. The problem is that, when I use the --daemon option, I get an error saying that a chroot() call failed. My config file does *not* have any chroot call in it. How can I avoid a chroot() invocation when running as a normal non-root user? Thanks in advance for any advice! -- Daniel Ortmann, LSI Logic, 3425 40th Av NW,

https://bugzilla.samba.org/show_bug.cgi?id=5275 Summary: user id mapping stopped working with 3.0.0pre10 Product: rsync Version: 3.0.0 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: brian@aljex.com

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 as powerful as in daemon mode (i.e. read only access, chroot, easy way of adding/modifying users and modules etc.) Why was encrypted

Hi, I'm running rsyncd in daemon mode started via xinetd. My /etc/rsyncd.conf looks like: [cache] path = /mnt/tst_vol_aws/sat_p_cache/ comment = Cache Directory use chroot = false read only = false uid = someone gid = someone dont compress = * On the client I run: /usr/bin/rsync --delete --ignore-errors -gpzsoltD --temp-dir=/mnt/tst_vol_aws/tmp/rsync -r

rsync: connection unexpectedly closed (88 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(139) I'm getting the above error when trying to use rsync over port 873. The command I'm using is : rsync -avz root@sundog::test ./ the /etc/rsyncd.conf contains the following auth users = root uid = root gid = staff [test] path = /export/home/mrl315 Any

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