Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-mirrors
Navigation:
Lists: gentoo-mirrors: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-mirrors@g.o
From: Tobias Klausmann <klausman@...>
Subject: chroot() and broken logging with rsyncd
Date: Sat, 6 Nov 2004 15:33:45 +0100
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

Replies:
Re: chroot() and broken logging with rsyncd
-- Tobias Klausmann
Navigation:
Lists: gentoo-mirrors: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
webrsync
Next by thread:
Re: chroot() and broken logging with rsyncd
Previous by date:
acl change request
Next by date:
mirror.tucdemonic.org


Updated Jun 17, 2009

Summary: Archive of the gentoo-mirrors mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.