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 uid = root In /var/log/rsync.log, I get two records recorded for the single issue or rsync from the client side. The problem is the timestamp are using localtime and Greenwich time. While running on the older version of the kernel, both timestamps were using localtime. Jul 13 16:44:59 web rsyncd[26323]: rsync on app_web from root@webA.arb.ca.gov (xxx.xxx.xxx.xxx) Jul 13 23:45:11 web rsyncd[26323]: wrote 4335227 bytes read 295 bytes total size 31683130932 Is there a way to get both timestamps, stamping "localtime"? Thanks
On Wed, Jul 13, 2005 at 05:01:55PM -0700, Steve Magee wrote:> The problem is the timestamp are using localtime and Greenwich time.This has come up: http://lists.samba.org/archive/rsync/2005-January/011353.html ... several times before: https://bugzilla.samba.org/show_bug.cgi?id=2607 Unfortunately, I have not heard of anyone discovering exactly what the problem is, though it appears to be outside of rsync's control. One way to work around the problem may be to set "use chroot = off" in your rsyncd.conf file. Does your system use syslogd (the daemon for syslog() calls)? If not, try enabling that. This all works fine on my Debian Sarge/Etch systems (which use libc6-2.6.2.ds1, just in case that's pertinent). ..wayne..