[gentoo-amd64] Clock set to FACTORY warning.

[gentoo-amd64] Clock set to FACTORY warning.

[Mark Haney]

I've got a warning (or error) when I boot up or shot down saying that 
/etc/conf.d/clock is still set to 'Factory'.  However, when I look at 
that file it actually set to 'local'.  Is anyone else seeing this?


-- 
Ita erat quando hic adveni.

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Clock set to FACTORY warning.

[Bob Sanders]

Mark Haney, mused, then expounded:
> I've got a warning (or error) when I boot up or shot down saying that 
> /etc/conf.d/clock is still set to 'Factory'.  However, when I look at 
> that file it actually set to 'local'.  Is anyone else seeing this?
>

Did you uncomment the "#TIMEZONE="Factory"" and change it to your
local timzone?

Bob
-  
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Clock set to FACTORY warning.

[Martins]

On Tuesday 27 February 2007 16:54:10 Mark Haney wrote:
> I've got a warning (or error) when I boot up or shot down saying that
> /etc/conf.d/clock is still set to 'Factory'.  However, when I look at
> that file it actually set to 'local'.  Is anyone else seeing this?

same here, i think that warning shows when 'local' is set

martins


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: Clock set to FACTORY warning.

[Arnaud Launay]

Le Tue, Feb 27, 2007 at 09:54:10AM -0500, Mark Haney a écrit:
> I've got a warning (or error) when I boot up or shot down saying that 
> /etc/conf.d/clock is still set to 'Factory'.  However, when I look at 
> that file it actually set to 'local'.  Is anyone else seeing this?

Either you updated baselayout without doing and etc-update or
dispatch-conf thereafter, either you're looking for the wrong
parameter, it should be

TIMEZONE="Where/Iam"

in /etc/conf.d/clock

	Arnaud.
-- 
Hébergement: http://www.nocworld.com/
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Clock set to FACTORY warning.

[Dieter Ries]

[-- Attachment #1: Type: text/plain, Size: 870 bytes --]

Am Dienstag 27 Februar 2007 16:10 schrieb Martins:
> On Tuesday 27 February 2007 16:54:10 Mark Haney wrote:
> > I've got a warning (or error) when I boot up or shot down saying that
> > /etc/conf.d/clock is still set to 'Factory'.  However, when I look at
> > that file it actually set to 'local'.  Is anyone else seeing this?


CLOCK="local"

# 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".

TIMEZONE="Europe/Berlin"

# If you wish to pass any other arguments to hwclock during bootup,
# you may do so here.


this is how it should look like, there are two variables


>
> same here, i think that warning shows when 'local' is set
>
> martins

-- 
Frank Castle is dead!
Call me 'The PUNISHER'!

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] Clock set to FACTORY warning.

[Mark Haney]

Bob Sanders wrote:
> Mark Haney, mused, then expounded:
>> I've got a warning (or error) when I boot up or shot down saying that 
>> /etc/conf.d/clock is still set to 'Factory'.  However, when I look at 
>> that file it actually set to 'local'.  Is anyone else seeing this?
>>
> 
> Did you uncomment the "#TIMEZONE="Factory"" and change it to your
> local timzone?
> 
> Bob
> -  
Well, I don't have that option in my /etc/conf.d/clock file.  I know I 
updated a few things and went through dispatch-conf, which is when I 
noticed, but on any files I haven't edited, I generally select the 'use 
new' option.  So either this file didn't get updated properly or something.


-- 
Ita erat quando hic adveni.

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Clock set to FACTORY warning.

[Bob Sanders]

Mark Haney, mused, then expounded:
> Bob Sanders wrote:
> >Mark Haney, mused, then expounded:
> >>I've got a warning (or error) when I boot up or shot down saying that 
> >>/etc/conf.d/clock is still set to 'Factory'.  However, when I look at 
> >>that file it actually set to 'local'.  Is anyone else seeing this?
> >>
> >
> >Did you uncomment the "#TIMEZONE="Factory"" and change it to your
> >local timzone?
> >
> >Bob
> >-  
> Well, I don't have that option in my /etc/conf.d/clock file.  I know I 
> updated a few things and went through dispatch-conf, which is when I 
> noticed, but on any files I haven't edited, I generally select the 'use 
> new' option.  So either this file didn't get updated properly or something.
>

It's part of - 

sys-apps/baselayout-1.12.9 (/etc/conf.d/clock) 

Perhaps check the emerge? Or simply add the TIMEZONE="" statement?

Bob
-  
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Clock set to FACTORY warning.

[Denis Solaro]

On Tue, 27 Feb 2007 16:28:21 +0100
Dieter Ries <clip2@gmx.de> wrote:

> Am Dienstag 27 Februar 2007 16:10 schrieb Martins:
> > On Tuesday 27 February 2007 16:54:10 Mark Haney wrote:
> > > I've got a warning (or error) when I boot up or shot down saying that
> > > /etc/conf.d/clock is still set to 'Factory'.  However, when I look at
> > > that file it actually set to 'local'.  Is anyone else seeing this?
> 
> 
> CLOCK="local"

I did edit that to CLOCK="UTC" and it works in my case, but as you say the comments ontop of this line clearly state :

# Set CLOCK to "UTC" if your system clock is set to UTC (also known as
# Greenwich Mean Time).  If your clock is set to the local time, then 
# set CLOCK to "local".  Note that if you dual boot with Windows, then 
# you should set it to "local".


-- 
If all the world's a stage, I want to operate the trap door.
		-- Paul Beatty
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Clock set to FACTORY warning.

[Daniel Gryniewicz]

On Tue, 2007-02-27 at 17:06 +0100, Denis Solaro wrote:
> On Tue, 27 Feb 2007 16:28:21 +0100
> Dieter Ries <clip2@gmx.de> wrote:
> 
> > Am Dienstag 27 Februar 2007 16:10 schrieb Martins:
> > > On Tuesday 27 February 2007 16:54:10 Mark Haney wrote:
> > > > I've got a warning (or error) when I boot up or shot down saying that
> > > > /etc/conf.d/clock is still set to 'Factory'.  However, when I look at
> > > > that file it actually set to 'local'.  Is anyone else seeing this?
> > 
> > 
> > CLOCK="local"
> 
> I did edit that to CLOCK="UTC" and it works in my case, but as you say the comments ontop of this line clearly state :
> 
> # Set CLOCK to "UTC" if your system clock is set to UTC (also known as
> # Greenwich Mean Time).  If your clock is set to the local time, then 
> # set CLOCK to "local".  Note that if you dual boot with Windows, then 
> # you should set it to "local".
> 

That warning has nothing to do with the CLOCK= line.  It's related to
the TIMEZONE= line, which is new in recent baselayout.  It replaces
symlinking /etc/localtime as the way to set the timezone.  If you didn't
merge in changes to /etc/conf.d/clock when you updated baselayout, you
won't have the correct section.  Paste it from here, or re-emerge
baselayout and re-run etc-update:

# 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".

TIMEZONE="America/Detroit"

Daniel

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Clock set to FACTORY warning.

[Peter Humphrey]

On Tuesday 27 February 2007 15:10:21 Martins wrote:
> On Tuesday 27 February 2007 16:54:10 Mark Haney wrote:
> > I've got a warning (or error) when I boot up or shot down saying that
> > /etc/conf.d/clock is still set to 'Factory'.  However, when I look at
> > that file it actually set to 'local'.  Is anyone else seeing this?
>
> same here, i think that warning shows when 'local' is set

No, it comes from some silly logic that says "if I don't have a recognisable 
timezone set, I'll complain that it's set to Factory, even though it 
isn't."

When I started getting this erroneous error message I had to insert this 
manually in /etc/conf.d/clock:

# Put in speculatively by PRH after silly error message during boot:
TIMEZONE="Europe/London"

Yes, I did run etc-update, as I do after every emerge that warns of the need 
to. I thought of raising a bug report, but didn't in the end. Sometimes I 
wonder at the thought processes whose results I see.

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