Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail
From: JohnF <john@please.see.sig.for.email.com>
Newsgroups: comp.os.linux.misc
Subject: Re: time problem
Date: Mon, 27 Oct 2014 12:11:52 +0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Lines: 30
Message-ID: <m2lcq8$7p7$2@reader1.panix.com>
References: <m2h7ul$78n$1@speranza.aioe.org> <m2hgmc$898$1@dont-email.me> <m2hh7n$vnb$1@speranza.aioe.org> <msuthbxd1a.ln2@goaway.wombat.san-francisco.ca.us> <m2hpu0$qqt$1@reader1.panix.com> <m2i18n$ems$1@dont-email.me> <m2i6qd$nta$1@reader1.panix.com> <m2j4r5$n7b$1@dont-email.me> <m2kjjg$cih$1@reader1.panix.com> <m2l6fo$qpq$2@dont-email.me>
NNTP-Posting-Host: panix3.panix.com
X-Trace: reader1.panix.com 1414411912 7975 166.84.1.3 (27 Oct 2014 12:11:52 GMT)
X-Complaints-To: abuse@panix.com
NNTP-Posting-Date: Mon, 27 Oct 2014 12:11:52 +0000 (UTC)
User-Agent: tin/2.0.0-20110823 ("Ardenistiel") (UNIX) (NetBSD/6.1.4 (i386))
Xref: csiph.com comp.os.linux.misc:12519

Rich <rich@example.invalid> wrote:
> JohnF <john@please.see.sig.for.email.com> wrote:
>> Rich <rich@example.invalid> wrote:
>> > <<big snip>>
>> > Or, setup an ntp client to keep your clocks synced with the ntp
>> > system on the internet, and just let the Slackware 14.1 rc.d
>> > scripts save the system time to the hardware clock when you do
>> > shutdown.
> 
>> I think you maybe solved the problem. On a hunch, just noticed that
>> rc.ntpd had 755 permissions, and indeed ps ax|grep ntp shows
>>     727 ?  Ss  0:00 /usr/sbin/ntpd -g -p /var/run/ntpd.pid
>> I must have inadvertantly told slackware's setup to run it during
>> install (which would also explain why previous releases never
>> exhibited the problem), and it's somehow been sporadically messing
>> stuff up ever since. Changed permissions (and kill'ed this instance),
>> so the problem's hopefully solved. No idea what, exactly, ntpd might
>> have been doing, but it'll hopefully stop now.

> That would do it.
> Having an /etc/hardwareclock file set as "localtime" and the ntpd
> daemon running would cause exactly what you've been seeing.
Good to know there's (finally) a rational explanation.

> Change /etc/localtime to UTC (as you've done, and leave it that way)
> and you can keep ntpd running and always have the correct time.
Actually, after all this, I feel more like taking ntpd out back
and feeding it into the wood chipper (channeling the movie Fargo).
-- 
John Forkosh  ( mailto:  j@f.com  where j=john and f=forkosh )