At boot time, and when I restart the service, I am warned: * Service clock starting Your TIMEZONE in /etc/conf.d/clock is still set to Factory! so ... "yes I know, and whats the matter ? any thing wrong with the fact I am happy with default TIMEZONE set to UTC ?" Initscript complain as if something was wrong. and what about if admin really do want to have clock set to UTC ? I think /etc/conf.d/clock should contain an additionnal variable; init script should only complain if somthing like HAD_BEEN_CUSTOMISED="no" was set, and shut up when switching it to yes. Because I do like UTC, and clock init script prompt at every boot as if something was wronf, what becomes frustrating with time. Similar process exist in DHCPd and Amsrtmontools boot scripts.
TIMEZONE="UTC"
--- clock 2007-04-05 08:27:06.000000000 -0300 +++ clock.orig 2007-04-05 08:26:49.000000000 -0300 @@ -57,7 +57,7 @@ # Make sure people set their timezone ... we do it here # even though we don't actually use the variable so that # people see the warning on boot. - if [[ ${CLOCK:-Factory} == "Factory" ]] ; then + if [[ ${TIMEZONE:-Factory} == "Factory" ]] ; then ewarn "Your TIMEZONE in /etc/conf.d/clock is still set to Factory!" fi } I made this to solve the problem, because init.d/clock make sure you aren't using rc.conf and using conf.d/clock, and in this conf file the comments is to you set your timezone at CLOCK variable, that's why I prefered changed my init.d/clock cya.
your system is out of date, current baselayout's clock init.d does not look like that
(In reply to comment #3) > your system is out of date, current baselayout's clock init.d does not look > like that > I gave a emerge --sync right now, than emerge -uD world -pv doesn't show me any update on clock.. I always put the update of init.d scripts in the place of my olds one, doesn't know what happened. Sorry for this inconvenience with this bug, I'll use this init.d modified till next update, than I post what happened here. Thanks.
