| 1 |
Hi, |
| 2 |
|
| 3 |
On Wed, Jan 16, 2008 at 05:37:21PM -0800, Mark Knecht wrote: |
| 4 |
> On Jan 16, 2008 4:56 PM, Drake Donahue <donahue95@×××××××.net> wrote: |
| 5 |
> > Thus etc-update and/or dispatch-conf can't change localtime; but can change |
| 6 |
> > whether localtime runs or not. |
| 7 |
> |
| 8 |
> Humm...seems like what you say is true but doesn't explain how emerge |
| 9 |
> -DuN system changed the file. It was clearly changed since I could |
| 10 |
> look inside with vi and compare to the Los_Angeles file and see that |
| 11 |
> they were clearly different... |
| 12 |
|
| 13 |
There's a variable in /etc/conf.d/clock that controls whether or not |
| 14 |
/etc/localtime should be updated when a new version of |
| 15 |
sys-libs/timezone-data is merged: TIMEZONE. If this variable is set, the |
| 16 |
specified timezone data file is copied over /etc/localtime. |
| 17 |
|
| 18 |
as you can read in /etc/conf.d/clock: |
| 19 |
# Select the proper timezone. For valid values, peek inside of the |
| 20 |
# /usr/share/zoneinfo/ directory. For example, some common values are |
| 21 |
# "America/New_York" or "EST5EDT" or "Europe/Berlin". If you want to |
| 22 |
# manage /etc/localtime yourself, set this to "". |
| 23 |
|
| 24 |
If TIMEZONE is not set, /etc/localtime is not updated by |
| 25 |
sys-libs/timezone-data. However, if TIMEZONE is set to an invalid value, |
| 26 |
then /etc/localtime is overwritten by the "Factory" timezone data file. |
| 27 |
|
| 28 |
etc-update has probably changed the value of this variable after a |
| 29 |
baselayout update. Then a timezone-data update used the wrong value to |
| 30 |
update /etc/localtime. In your, case, the value of TIMEZONE should be |
| 31 |
TIMEZONE="America/Los_Angeles". |
| 32 |
|
| 33 |
-- |
| 34 |
Nicolas Litchinko |
| 35 |
BOFH excuse #348: |
| 36 |
We're on Token Ring, and it looks like the token got loose. |
| 37 |
-- |
| 38 |
gentoo-amd64@l.g.o mailing list |
Archives