On Sat, 2005-Nov-26 22:27:49 -0700, Brett Glass wrote:
>I am wondering if I shouldn't just redo everything in the system that
>has to do with time zones and time keeping (deleting files and re-creating
>them if need be), reboot, and see what happens.
That's as good as idea as any other. I know cr
Brett Glass wrote this message on Sat, Nov 26, 2005 at 22:27 -0700:
> At 09:14 PM 11/26/2005, Peter Jeremy wrote:
>
> >On Sat, 2005-Nov-26 15:07:26 -0700, Brett Glass wrote:
> >>By the way, the "date" command does report the correct time. It's cron
> >>that seems to be getting the time wrong.
> >
At 09:14 PM 11/26/2005, Peter Jeremy wrote:
>On Sat, 2005-Nov-26 15:07:26 -0700, Brett Glass wrote:
>>By the way, the "date" command does report the correct time. It's cron
>>that seems to be getting the time wrong.
>
>You haven't accidently created a line that looks like 'TZ=' in the
>crontab ha
On Sat, 2005-Nov-26 15:07:26 -0700, Brett Glass wrote:
>By the way, the "date" command does report the correct time. It's cron
>that seems to be getting the time wrong.
You haven't accidently created a line that looks like 'TZ=' in the
crontab have you?
Is this affecting all users or just one?
-
At 05:40 PM 11/26/2005, Jon Dama wrote:
>What is the output of
>
>date vs date -u
>
>on your system?
>
>What's the value of machdep.adjkerntz ?
www# date
Sat Nov 26 17:53:20 MST 2005
www# date -u
Sun Nov 27 00:53:22 UTC 2005
www# sysctl -a | grep kerntz
machdep.adjkerntz: 25200
>Is /etc/localti
What is the output of
date vs date -u
on your system?
What's the value of machdep.adjkerntz ?
Is /etc/localtime intact?
Does anything change if you rerun tzsetup?
On Sat, 26 Nov 2005, Brett Glass wrote:
> At 07:20 PM 11/25/2005, Jon Dama wrote:
>
> >Uh, the problem would be that kernel d
At 09:08 PM 11/25/2005, Joseph Koshy wrote:
>> Just created a server using FreeBSD 6.0, and it's quite
>> stable and fast. One glitch, though: Jobs scheduled to
>> run at midnight via /etc/crontab are running at 6 PM
>> (midnight GMT). I've double checked, and the CMOS clock
>> is set to local ti
At 07:20 PM 11/25/2005, Jon Dama wrote:
>Uh, the problem would be that kernel does not know that the CMOS clock is
>set to the local time. Standard practice is that the CMOS clock should be
>set to UTC.
We've never set the CMOS clock to UTC/GMT on any previous version of
FreeBSD, and yet have n
> Just created a server using FreeBSD 6.0, and it's quite
> stable and fast. One glitch, though: Jobs scheduled to
> run at midnight via /etc/crontab are running at 6 PM
> (midnight GMT). I've double checked, and the CMOS clock
> is set to local time and the time zone is specified as
> Mountain Sta
Uh, the problem would be that kernel does not know that the CMOS clock is
set to the local time. Standard practice is that the CMOS clock should be
set to UTC. libc then uses knowledge of the timezone to properly report
the local time.
see man adjkerntz
(adjust kernel time zone)
On Fri, 25 Nov
Just created a server using FreeBSD 6.0, and it's quite
stable and fast. One glitch, though: Jobs scheduled to
run at midnight via /etc/crontab are running at 6 PM
(midnight GMT). I've double checked, and the CMOS clock
is set to local time and the time zone is specified as
Mountain Standard Time.
11 matches
Mail list logo
