Re: Bad time logging - rsync 3.1.1 as daemon on Mac OS 10.9

2014-08-19 Thread Francis . Montagnac
Hi. Try perhaps to copy /etc/localtime in the chroot, for example with: cd / rsync -LaR etc/localtime PATH_TO_THE_CHROOT/ Francis -- Please use reply-all for most replies to avoid omitting the mailing list. To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync

Re: Bad time logging - rsync 3.1.1 as daemon on Mac OS 10.9

2014-08-19 Thread Kevin Korb
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nothing in your example involves the rsync daemon or a chroot. Anyways, what happend when you did that and what did you expect to happen instead? On 08/19/2014 02:07 AM, francis.montag...@inria.fr wrote: Hi. Try perhaps to copy /etc/localtime in

Re: Bad time logging - rsync 3.1.1 as daemon on Mac OS 10.9

2014-08-19 Thread Francis . Montagnac
On Tue, 19 Aug 2014 02:29:35 -0400 Kevin Korb wrote: Nothing in your example involves the rsync daemon or a chroot. Except the PATH_TO_THE_CHROOT/ Anyways, what happend when you did that and what did you expect to happen instead? I suspect that the rsync daemon is calling localtime(3) in the

Bad time logging - rsync 3.1.1 as daemon on Mac OS 10.9

2014-08-18 Thread Dave Gradwell
Hi, I'm on Mac OS 10.9, using rsync 3.1.1. When the rsync daemon logs, it fails to determine the correct time: 2014/08/18 18:47:24 [1002] connect from localhost (::1) 2014/08/18 17:47:24 [1003] rsync to dave/in-progress/data/ from dave@localhost (::1) When I specify use chroot = false in the