Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 108890 - Timezones causes incorrect time (modification time in future)
Summary: Timezones causes incorrect time (modification time in future)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-11 09:48 UTC by Alexander Roos
Modified: 2005-10-27 19:13 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Roos 2005-10-11 09:48:37 UTC
Hi, 
 
today I installed 2005.1 with ~AMD64. 
When I symlink /etc/localtime to a timezone and reboot my system some 
folders / files show a diffrent modification date (no time ist shown - but the 
year). 
The system than gives me lots of warnings that the time is in the 
future, ... . Only UTC works very well. But I want Europe/Berlin. 

Reproducible: Always
Steps to Reproduce:
1. Install 2005.1, ~AMD64 
2. Change /etc/localtime to something diffrent from UTC 
3. Reboot system 
 
Actual Results:  
Some folders / files shown wrong timeformat / time (after reboot) 

Expected Results:  
Show all times correct.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2005-10-11 10:09:09 UTC
So set your BIOS time to UTC.
Comment 2 Alexander Roos 2005-10-11 10:15:10 UTC
This isn't a solution. 
I can change BIOS-Clock to UTC or local - nothing changes on this behaviour. 
Everytime I have a timezone diffrent from UTC choosen and reboot the system - 
some files / folders shows a diffrent timestring and I get warnings (time in 
future). 
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2005-10-11 10:16:43 UTC
Sure, if you have screwed timestamps, you'll have fix them manually or wait
until they are not in future. Your system time is set up incorrectly, this is
not a bug. 
Comment 4 Alexander Roos 2005-10-11 10:21:58 UTC
Example: 
ls -a 
... 
drwxr-xr-x  3 root root  4096 11. Okt 15:20 home 
drwxr-xr-x 43 root root  4096 11. Okt 2005  etc 
... 
 
This happens when I choose a timezone diffrent to UTC and reboot the system. 
When I set /etc/localtime to UTC again and reboot all is shown correctly (like 
example "home"). 
 
Comment 5 Alexander Roos 2005-10-11 10:26:37 UTC
I can recursivly "touch" all files / folders to get the correct time shown - 
but after a reboot all changes are gone. 
I think it
Comment 6 Alexander Roos 2005-10-11 10:26:37 UTC
I can recursivly "touch" all files / folders to get the correct time shown - 
but after a reboot all changes are gone. 
I think it´s a bug. 
 
When I do a "ls -al --time-style=full-iso" all is shown correctly - but a 
simple "ls -al" shows the output like in my posted example. Some processes 
(bootscripts, make, ... tell me that the modification time is in the future. 
Only UTC works. 
Comment 7 Jakub Moc (RETIRED) gentoo-dev 2005-10-11 10:40:34 UTC
Post the output of 'hwclock --show' and 'date' 
Comment 8 Alexander Roos 2005-10-11 10:53:34 UTC
hwclock --show outputs: 
Di 11 Okt 2005 19:47:29 CEST  -0.436354 Sekunden 
 
date outputs: 
Di Okt 11 19:47:36 CEST 2005 
 
ls -al example output: 
insgesamt 96 
drwxr-xr-x  20 root root  4096 11. Okt 17:48 . 
drwxr-xr-x  20 root root  4096 11. Okt 17:48 .. 
-rw-------   1 root root  1173 11. Okt 13:13 .bash_history 
drwxr-xr-x   2 root root  4096 11. Okt 15:20 bin 
drwxr-xr-x   2 root root  4096 11. Okt 15:20 boot 
drwxr-xr-x  18 root root 13760 11. Okt 17:46 dev 
drwxr-xr-x  44 root root  4096 11. Okt 17:48 etc 
drwxr-xr-x   3 root root  4096 11. Okt 13:23 home 
-rw-r--r--   1 root root    35 11. Okt 13:13 .lesshst 
lrwxrwxrwx   1 root root     5 11. Okt 08:08 lib -> lib64 
drwxr-xr-x   2 root root  4096 11. Okt 13:13 lib32 
drwxr-xr-x   8 root root  4096 11. Okt 15:20 lib64 
drwx------   2 root root  4096 11. Okt 15:20 .links 
drwx------   2 root root 16384 11. Okt 15:20 lost+found 
drwxr-xr-x   9 root root  4096 11. Okt 15:20 mnt 
drwxr-xr-x   4 root root  4096 11. Okt 15:20 opt 
-rw-r--r--   1 root root    78 11. Okt 17:47 output 
-rw-r--r--   1 root root     0 11. Okt 17:48 output2 
dr-xr-xr-x  53 root root     0 11. Okt 2005  proc 
drwx------   2 root root  4096 11. Okt 15:20 root 
drwxr-xr-x   2 root root  4096 11. Okt 2005  sbin 
drwxr-xr-x  10 root root     0 11. Okt 2005  sys 
drwxrwxrwt   5 root root  8192 11. Okt 17:46 tmp 
drwxr-xr-x  15 root root  4096 11. Okt 17:42 usr 
drwxr-xr-x  12 root root  4096 11. Okt 15:20 var 
 
The files / folders with year shown in "ls -al" changes every time I reboot 
the system. 
Comment 9 Andreas Arens 2005-10-11 15:23:34 UTC
I just had the same thing happen after an update to baselayout-1.12.0_pre9 
(2005.1 ~amd64). The next reboot I got a bunch of "time in the future warning" 
from /etc/init.d/depscan.sh. None of the files were touched or modified (except 
the obvious updates through the new baselayout). My system time is kept up to 
date against internet time servers through an ipup.local script (verified to 
work correctly) and the hwclock is also fine.  
I however do not see the strange date output, and the problem didn't appear 
during the next reboot (the depcache in /var/lib/init.d obviously was rebuilt 
correctly). 
My timezone happens to be CEST also, clock set to localtime. 
I have set globally set LC_ALL to "en_US.UTF-8", interestingly 'date' uses 
24h mode while 'hwclock' uses 12h AM/PM mode in its output. 
Comment 10 Alexander Roos 2005-10-12 02:11:31 UTC
I have tried to install 2005.1, ~x86 instead of ~AMD64. 
There is the same problem.  
Comment 11 SpanKY gentoo-dev 2005-10-12 06:21:17 UTC
do you setup /etc/conf.d/clock ?
Comment 12 Alexander Roos 2005-10-12 06:23:46 UTC
yes, I tried UTC and local setting - but nothing changs this mysterious 
behaviour. Now I
Comment 13 Alexander Roos 2005-10-12 06:23:46 UTC
yes, I tried UTC and local setting - but nothing changs this mysterious 
behaviour. Now I´m triing to instal AMD64 (stable). 
Comment 14 SpanKY gentoo-dev 2005-10-12 06:28:31 UTC
did you also try changing the CLOCK_SYSTOHC setting ?
Comment 15 Alexander Roos 2005-10-12 06:32:03 UTC
no, this setting i didn't change. 
My previous Gentoo-installation wordked well without. 
The behaviour only happens when I set /etc/localtime so a zoneinfo diffrent to 
UTC. 
Comment 16 Alexander Roos 2005-10-12 07:24:37 UTC
The result with an AMD64 (not ~AMD64) is the same. 
Comment 17 Alexander Roos 2005-10-12 07:56:40 UTC
Now only the directories proc and sys show the wrong date-string. 
I think it
Comment 18 Alexander Roos 2005-10-12 07:56:40 UTC
Now only the directories proc and sys show the wrong date-string. 
I think it´s because clock is set after creating / mounting the directories. 
Anybody an advice? 
Comment 19 SpanKY gentoo-dev 2005-10-27 19:13:35 UTC
sounds about right