Mailing List Archive
tlug.jp Mailing List tlug archive tlug Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: [tlug] Erratic Rsync Behavior: Coping with Multi-Booting Effects on Time-keeping
- Date: Sun, 1 May 2011 01:11:48 +0800
- From: Stephen Lee <sl-tlug@example.com>
- Subject: Re: [tlug] Erratic Rsync Behavior: Coping with Multi-Booting Effects on Time-keeping
- References: <4DB7BB1D.1010700@example.com> <87sjt487md.fsf@example.com> <4DB7D5AC.4010105@example.com> <87oc3ranpg.fsf@example.com> <4DB883FB.3040601@example.com> <4DB95687.2010904@example.com> <4DB9718A.5060806@example.com> <BANLkTi=VUduf1ntZ2D50mD82Q6B6NePs5g@example.com> <4DBA2160.80506@example.com> <4DBA3C52.6040405@example.com> <20110429094807.7af6e870.jep200404@example.com> <BANLkTikW8qLNf1uGCnCgRunoxPyF-KAqoQ@example.com> <4DBBE263.4090104@example.com>
Try looking for the hwclock command in the startup scripts, which AFAICG (*) is responsible for (A) setting the system clock initially from the hardware clock and (B) setting the kernel timezone which is responsible for the time offset for the fat filesystem (FAT stores timestamps in local time and not UTC). Since (A) and (B) are both wrong on your system, wrong environment/parameters to hwclock would seem to be the likely culpit. If you can't find where it is called, check the initial RAM disk as well if you use one. (*) as far as I can google -- Stephen Lee <sl-tlug@example.com>
- Follow-Ups:
- Re: [tlug] Erratic Rsync Behavior: Coping with Multi-Booting Effects on Time-keeping
- From: Charles Muller
Home | Main Index | Thread Index
- Next by Date: Re: [tlug] Erratic Rsync Behavior: Coping with Multi-Booting Effects on Time-keeping
- Next by thread: Re: [tlug] Erratic Rsync Behavior: Coping with Multi-Booting Effects on Time-keeping
- Index(es):
Home Page Mailing List Linux and Japan TLUG Members Links