Re: Date out of Sync?

OK, I have found the logging problem. In /usr/share/current/logger.py on
line 53 there is the following.

# Our timestamp format is:  MMM DD hh:mm:ss (this reproduces syslog
format
# in all but one way - the day is zero-padded, in syslog it's
space-padded)
tmp = time.strftime("%b %2m %H:%M:%S ", time.localtime(time.time()))

Notice how the comment says the format is MMM DD but the time is
formatted as MMM MM.

I simply changed this to read,

tmp = time.strftime("%b %2d %H:%M:%S ", time.localtime(time.time()))

and the log is now correct. This doesn't solve my current (pun
intended!) problem but I will prevail.

--
Greg





On Thu, 2002-04-25 at 14:51, Greg Wildman wrote:
> Hi Draco,
> 
> Good idea, I hadn't thought of that <blush>. I checked by removing the
> logfile and restarting current 3 times to make sure, but to no avail.
> 
> Log below.
> 
> ------------------------------------------------------------------
> 
> [root@mid-ftp-01 log]# tail -f current.log 
> Apr 04 14:47:23 Current server v1.0.2 starting, released under the GPL
> Apr 04 14:47:29 Goodbye.
> Apr 04 14:47:30 Current server v1.0.2 starting, released under the GPL
> Apr 04 14:47:34 Goodbye.
> Apr 04 14:47:38 Current server v1.0.2 starting, released under the GPL
> 
> [root@mid-ftp-01 log]# date
> Thu Apr 25 14:47:51 SAST 2002
> [root@mid-ftp-01 log]# 
> 
> ------------------------------------------------------------------
> 
> 
> On Thu, 2002-04-25 at 14:43, Draco Benden wrote:
> > On Thu, Apr 25, 2002 at 01:37:46PM +0200, Greg Wildman wrote current-server:
> > > Yesterday I got the usual error you get when there is a time difference
> > > between the server and clients. After poking around I have found
> > > something strange. The date in the log is for Apr 04 whereas today is
> > > the 25th. I checked the current system date as well as sync with ntpdate
> > > and it was correct giving Apr 25.
> > > 
> > > Any ideas? Log below.
> > A) When's the last time your log file was modified?
> > B) Is the current server still running?
> > 
> > seems to me like th server crashed on the 4th and just hasn't done anything
> > since (but of course I could be wrong).
> 
> 
> _______________________________________________
> Current-server mailing list
> [email protected]
> http://lists.dulug.duke.edu/mailman/listinfo/current-server