Re: [gentoo-amd64] Problem with latest timezone update?

[Peter Humphrey <peter@humphrey.ukfsn.org>]

On Thursday 17 January 2008 10:15:12 Nicolas Litchinko wrote:

> There's a variable in /etc/conf.d/clock that controls whether or not
> /etc/localtime should be updated when a new version of
> sys-libs/timezone-data is merged: TIMEZONE. If this variable is set, the
> specified timezone data file is copied over /etc/localtime.
>
> as you can read in /etc/conf.d/clock:
> # Select the proper timezone.  For valid values, peek inside of the
> # /usr/share/zoneinfo/ directory.  For example, some common values are
> # "America/New_York" or "EST5EDT" or "Europe/Berlin".  If you want to
> # manage /etc/localtime yourself, set this to "".
>
> If TIMEZONE is not set, /etc/localtime is not updated by
> sys-libs/timezone-data. However, if TIMEZONE is set to an invalid value,
> then /etc/localtime is overwritten by the "Factory" timezone data file.

That's useful - thanks.

Now, how do I prevent /etc/init.d/clock being run at boot time? If I 
command "rc-update del clock" it gets put back again at shutdown time.

My reason is that I want to run chrony on my network, for its smooth 
adjustment of system time, and it can't work properly if another program 
also changes the system time.

-- 
Rgds
Peter
-- 
gentoo-amd64@lists.gentoo.org mailing list