Hi! 

I noticed that using rsyncd's chroot() functionality (which is
recommended) breaks logging if your machine is not using UTC as
system time zone.

The problem is this: rsyncd logs various stuff after chrooting
(for example the "wrote X  read Y total size Z" line.
Unfortunately, at this point /etc/localtime is inaccesible,
resulting in UTC times being used. Other log lines (most notably
the per -session "rsync on gentoo-portage from NAME (IP)" are
written *outside* the chroot(), resulting in localized times.

At first I thought this might be fixed by using syslog logging,
but as the syslog call is used (i.e. not syslog-over-UDP) , the
problem remains.

So I thought, I'd deactivate chroot()ing in order to narrow down
the problem. And bing: using use chroot=false "fixes" the
timestamps. 

Loging with broken timestamps is damn near unusable, so what
should we do about it? I've written to the rsync maintainers (via
their mailing list) but got no feedback whatsoever :-(

Greets,
Tobias

PS: Seemingly, older rsyncds don't have this problem. I'm using
v2.6.3

--
gentoo-mirrors@g.o mailing list