similar to: rsync log issues

I'm trying to get over an exasperating problem with rsync 2.5.7, but I'm not making any headway. The nut of the problem is that the rsync daemon seemingly ignores the "syslog facility" configuration when running in standalone daemon mode, as opposed to being started with inetd. So, for example, if I have my configuration file with [global] pid file = /etc/rsync/rsyncd.pid

There are two security advisories for people who run a writable rsync daemon. One affects only those with "use chroot = no" (which is not a very safe combination in general), and one affects a daemon that has daemon-excluded files that are being hidden in a module's hierarchy. Included are simple config-change suggestions that should help you to avoid the security issues. These

There are two security advisories for people who run a writable rsync daemon. One affects only those with "use chroot = no" (which is not a very safe combination in general), and one affects a daemon that has daemon-excluded files that are being hidden in a module's hierarchy. Included are simple config-change suggestions that should help you to avoid the security issues. These

hello, It's the first time I post some thing in this forum. I am using rsync over Netware 6.5 to syncing 20 Novell servers. My wan conection is 2 Mb and I run rsync at night when traffic is very low. I use the following parameters: rsincstp.ncf sys:rsync/rsyncdn Rsync172.17.X.Y:873 rsyncstr.ncf sys:rsync/rsyncst sys:rsync/rsync --progress --address=172.17.X.Y

https://bugzilla.samba.org/show_bug.cgi?id=8198 Summary: rsync does not set TZ variable after chroot(), which confuses logging timestamps Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at

Hello there! We are trying to get rsync to work in our servers but so far we did not succeeded. Our scenario is a 3 machines where one directory must be replicated through all the clusters, no matter where the file was saved. I have a few basic questions regarding that: 1st Do I need a daemon on all instances or just one of them? Files saved on any of them must be mirrored 2nd We gave a try with

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

Hi there list :) I use backuppc to take backup of a bunch of hosts, but I ran into problems with the last one I set up, I can't find anything that is different on this one...but it won't work... So any hints would be greatly appreciated, here are the files ryncd.conf: log file=/var/log/rsyncd pid file=/var/run/rsyncd.pid [all] comment = All disk path = / use

https://bugzilla.samba.org/show_bug.cgi?id=1900 Summary: rsync --daemon hangs with --numeric-ids Product: rsync Version: 2.6.2 Platform: All OS/Version: FreeBSD Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: peter-samba@dataloss.nl

First, yes, I have read the piece on chroot.... Trying to get an AIX (5.3) to run rsync 2.6.2 as a daemon I have tried every possibly usage to stop chroot, used no and false, as on the web it has showed up as either. Also dropped flag --numeric-ids when running.... Here is my test config--- # Simple test config file log file = /tmp/rsync.log [test] use chroot = no path = /tmp/rsync_test/

I am attempting to utilize the exclude from option in my rsync configuration file (rather than maintain lists on users machines) but it does not appear to be working. One example, I placed *.mp3 in the file to keep them from syncing mp3 files to the server and jamming up space. But rsync just seems to ignore this and syncs the files anyway without any errors to the syslog. All of my

I haven't gotten it to work successfully, I'm still struggling with the same setgroups error that you are. However, I can tell you what I have tried. So far I have rsync configured to run in --daemon mode using the command: sudo rsync --daemon I can prompt it for a list of modules, but when I go to copy a module, I get the error @ERROR: setgroups failed. I can copy locally, from one HD to

Greetings, Has anyone successfully compiled rsync 2.5.5 under Mac OS X (not Server), and actually have it work fully? I'm in a position where I'm trying to setup an automated nightly remote backup between and Cobalt Raq4 (running a variant of Redhat Linux) and a Mac running OS X 10.1.5 with the latest development tools installed. As has been pointed out previously on the list, one has

I'm running rsync 2.5.1 on solaris 7 in server mode and getting the above message when entering the following command: rsync -vraz --delete hostname::test ./ this is my rsyncd.conf use chroot = no max connections = 25 syslog facility = local 3 read only = false log file = /var/log/rsyncd.log pid file = /var/log/rsyncd.pid lock file = /var/log/rsyncd.lock [test] path = /export/home/mrl315

As indicated in the documentation, --log-file is supposed to override the "log file" directive in daemon mode. I'm seeing some odd behavior regarding this... it appears that while startup and connect information is written to the command-line log, the transfer information is still written to the rsyncd.conf log file. All tests are done with rsync 3.0.5, and have been tested

The subject says it all :-) Apparently in pre-3.0.0 versions '%P' would log the actual path as specified in the module entry in rsyncd.conf, but now it's apparently relative to the chroot... Paul Slootman

SUMMARY There is a path-sanitizing bug that affects daemon mode in all recent rsync versions (including 2.6.2) but only if chroot is disabled. It does NOT affect the normal send/receive filenames that specify what files should be transferred (this is because these names happen to get sanitized twice, and thus the second call removes any lingering leading slash(es) that the first call left

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's my understanding that as of 3.0 rsync supports OS X ACLs and extended attributes, and that it should be possible to backup a tree from an OS X system that contains files and folders with ACLs and extended attributes to a Linux host filesystem that has both "user_xattrs" and "acl" enabled on the destination file system.

Hi all: I tried to start a rsync daemon under my user name (not an administrator) on debian linux box(linux kernel 2.4.27), and failed. The command I used is > rsync -v -v --daemon --config=rsyncd.conf This command returns without any error although the daemon does not get started. The rsyncd.conf I used is as follows. Do I miss anything in the configuration file? Any help is appreciated.

Just upgraded from rsync 2.6.2 protocol version 28 to 2.6.3 protocol version 28. Linux kernel upgraded from 2.6.5-1 to 2.6.9-11. From the client side, I issued... rsync -av web::app_web /app > /dev/null From the server side, the config shows... [app_web] comment = Moving webs Inside & Outside path = /app auth users = root secrets file = /etc/rsyncd.secrets read only = true