Date:  Tue, 15 Apr 2008 08:48:34 +0100
From:  Michael Stauber <bq (at mark) solarspeed.net>
Subject:  [coba-e:12584] Re: Different Clock Times
To:  coba-e (at mark) bluequartz.org
Message-Id:  <200804150948.34965.bq (at mark) solarspeed.net>
In-Reply-To:  <78072.92512.qm (at mark) web65608.mail.ac4.yahoo.com>
References:  <78072.92512.qm (at mark) web65608.mail.ac4.yahoo.com>
X-Mail-Count: 12584

Hi Dan,

> Any idea what services to restart, short of doing a reboot?
>
> Apr 14 17:31:11 admin sshd[22769]: Invalid user eaguilar from
> 203.197.82.242
> Apr 14 22:31:11 admin sshd[22772]: input_userauth_request: invalid user
> eaguilar
> Apr 14 17:31:12 admin sshd[22773]: Invalid user eaguilar from
> 203.197.82.242
> Apr 14 22:31:12 admin sshd[22776]: input_userauth_request: invalid user
> eaguilar
> Apr 14 17:31:35 admin sshd[22769]: Failed password for invalid user
> eaguilar from 203.197.82.242 port 39381 ssh2
> Apr 14 22:31:35 admin sshd[22772]: Connection closed by 203.197.82.242
> Apr 14 17:31:36 admin sshd[22773]: Failed password for invalid user
> eaguilar from 203.197.82.242 port 36154 ssh2
> Apr 14 22:31:36 admin sshd[22776]: Connection closed by 203.197.82.242
>
> I had previously restarted sshd to no effect.

While this by itself does no harm: Yeah, it sure doesn't look nice in the 
logs. :o)

To "unclutter" the logs after such a spectacular time drift it may be 
necessary restart pretty much all daemons - including Syslogd itself. To be 
honest: I'd rather do a reboot as it's less hassle than restarting all the 
required services manually. 

To prevent this from happening again, consider specifying a NTP server 
under "System Settings" / "Time" / "NTP Server Address".

-- 
With best regards,

Michael Stauber