Re: Time Server by IBC
IBC
Mon Jan 12 14:39:43 CST 2004
I stopped the time service before issuing the command, so I don't think this
is the issue. I'll try it again though to make sure.
AMEN brother, preaching to the choir here! Unfortunately I have several
people in this office who are unbelievably focused on that time being
EXACTLY right. Not a minute off, not 4 minutes off, EXACT. I figured if I
forced it to update 3 times a day I could tell them it isn't getting anymore
precise. Alternatively I could lie and say its already that way, but I'd
have to live with that overpowering guilt.......=P
Unfortunately during one of the office meetings I was grilled about why the
clocks can't be accurate to which a smartly responded "It's synched to the
atomic clock, we aren't getting any more accurate.", only to find out that
my time server IP had been changed or quit serving all together. (sat down,
ate large plate of crow....) I've picked a new time server from our
University system and I'm using the DNS, not the IP so I shouldn't have to
worry about that again. I hope.
Thanks for the time Dave!
(no pun intended, but it sure worked out well......)
"Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:eIBddGU2DHA.3016@TK2MSFTNGP09.phx.gbl...
> You may be having a conflict between the windows time service and the
w32tm
> command. Does it work if you shut down windows time in services first?
>
> I hate to answer a question with unsolicited advice, but why mess with
this?
> The time service will modify it's update period automatically based on how
> big or small a correction needs to be made - if the clock is relatively
> accurate, the time service will update less than if it's usually off by
> quite a bit. IMHO this is a case where if it ain't broke, don't fix it.
>
>
> "IBC" <it@ibcengineering.com> wrote in message
> news:O25D8aT2DHA.2700@tk2msftngp13.phx.gbl...
> > I've used the Time service before, however it appears that at some point
> the
> > time server I was using changed IP's or gave up time serving. So when I
> went
> > in to fiddle around with the time service again, I decided to try and
set
> > the switch "w32tm -period" to a different value than the default.
Trouble
> is
> > that after I type the command (ie: w32tm -period 3) it just sits there.
> > Doesn't return me to the comand line, doesn't provide any feedback, just
> > sits like its hung during the command. Is this normal? I had to CTRL-C
out
> > of the command to get my cursor back.
> >
> > Appreciate any enlightenment you may bestow upon me.
> >
> > Thanks.
> >
> >
>
>