Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 201019 - rsyncd gets confused with timezones when logging to syslog
rsyncd gets confused with timezones when logging to syslog
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rsync (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jan Zeleny
: 205326 (view as bug list)
Depends On:
Blocks: 575022
  Show dependency treegraph
Reported: 2006-08-02 06:30 EDT by David Johnson
Modified: 2010-03-19 03:48 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 575022 (view as bug list)
Last Closed: 2010-03-19 03:47:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Johnson 2006-08-02 06:30:04 EDT
Description of problem:
I'm running rsyncd and it seems to be getting confused with the time-zone when
logging. Here's a typical entry in messages:

Aug 2 09:30:01 rsyncd[8174]: rsync on /home from user@host (
Aug 2 08:30:01 rsyncd[8174]: wrote 2629 bytes read 122 bytes total size 626582

The correct local time is 09:30:01, whereas GMT is 08:30:01. So for some reason
it logs its first entry in local time, then the second entry in GMT. Every other
application logs using local time.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run rsyncd
2. Connect to it and perform some operation

Actual results:
The two log entries generated by rsyncd in messages use different time zones.

Expected results:
The two log entries generated by rsyncd in messages both use local time.
Comment 1 David Tonhofer 2007-10-21 17:29:59 EDT
Same as bug #205326

Comment 2 Simo Sorce 2007-10-22 03:30:58 EDT
*** Bug 205326 has been marked as a duplicate of this bug. ***
Comment 3 Jan Zeleny 2010-03-05 05:04:59 EST
Since there is only one more release of RHEL-4 planned and it will be focused on security and performance, I'm planning to close this bug as WONTFIX. Can you please confirm this behavior in RHEL5 or is it solved there?
Comment 4 David Johnson 2010-03-18 14:20:21 EDT
I'm afraid I no longer have a RHEL system to test this with, but I managed to find this upstream bug, which says that this bug was fixed in rsync 2.6.9:
Comment 5 Jan Zeleny 2010-03-19 03:47:35 EDT
Thank you very much. It looks like the issue hasn't been fixed in RHEL-5. I'm copying the bug there and closing this one.

Note You need to log in before you can comment on or make changes to this bug.