I got rsyncd v2.6.6 protocol version 29 running on Suse Enterprise Server 10. Here's what my /etc/rsyncd.conf looks like - max connections = 0 log format = %a %h %o %f %l %b log file = /var/log/rsync/rsync.log [nibbler] path = /backup/nibbler comment = nibbler read only = no use chroot = no timeout = 3600 transfer logging = yes [remote] path = /backup/remote/ comment = remote read only = no use chroot = no timeout = 3600 transfer logging = yes All I am trying to do is get an email notification on how many bytes have been transfered from which server each night. I tried - [remote] path = /backup/remote/ comment = remote read only = no use chroot = no timeout = 3600 transfer logging = yes log file = remote.log with the hope to cat/awk/cut/grep each log to get something emailed out. But it doesn't generate any log. Is there any easy way I could get rsync results emailed out for each individual server from rsyncd daemon? Thanks.
On Thu, Oct 26, 2006 at 02:12:47AM -0700, atstake atstake wrote:> [remote] > path = /backup/remote/ > comment = remote > read only = no > use chroot = no > timeout = 3600 > transfer logging = yes > log file = remote.logThe "log file" directive is not a per-module setting in anything prior to 2.6.9, so you'll need to either wait for that to be released or try out the latest "nightly" tar file (which is extremely close to what will be released). ..wayne..
Maybe Matching Threads
- Rsync doesn't log properly when in standalone daemon mode
- Rsync-daemon security advisories for writable daemons
- Rsync-daemon security advisories for writable daemons
- rsync error
- [Bug 8198] New: rsync does not set TZ variable after chroot(), which confuses logging timestamps