Bug 167655 – wrong timezone definition when /etc/conf.d/clock* files persist

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description bess 2007-02-19 18:42:37 UTC]

I think that's some init.d script problem.
When I have default configuration in file /etc/conf.d/clock.default
and do some changes in /etc/conf.d/clock according to my timezone,
system says while starting or restarting /etc/init.d/clock:
 * Your TIMEZONE in /etc/conf.d/clock is still set to Factory!
 * Setting system clock using the hardware clock [UTC] ... 
After removing file /etc/conf.d/clock.default problem disappears.

Reproducible: Always

Steps to Reproduce:
1.Copy default configuration of /etc/conf.d/clock to /etc/conf.d/clock.default (CLOCK="UTC" and TIMEZONE isn't set)
2. Make some changes in /etc/conf.d/clock (example: CLOCK="UTC" TIMEZONE="Europe/Moscow")
3. /etc/init.d/clock restart

Actual Results:  
the result is:
 * Your TIMEZONE in /etc/conf.d/clock is still set to Factory!
 * Setting system clock using the hardware clock [UTC] ... 
though /etc/conf.d/clock configured to local settings

Expected Results:  
 * Setting system clock using the hardware clock [Local Time] ...

[Comment 1 SpanKY 2007-02-19 22:22:55 UTC]

you've most likely done something wrong as the test in init.d/clock is very basic; if TIMEZONE isnt set it warns

if you still think your /etc/conf.d/clock is correct, please post it as an attachment