From mboxrd@z Thu Jan  1 00:00:00 1970
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-reply-to: Your message of "Tue, 02 Sep 2014 15:10:56 EDT."
	<6e2a7a02201fcf3ea5d0d894d0d16916@ladd.quanstro.net>
References: <346c54679a6cdc9bb557724d8b93bbc6@quintile.net>
	<6e2a7a02201fcf3ea5d0d894d0d16916@ladd.quanstro.net>
Date: Tue,  2 Sep 2014 13:04:00 -0700
From: Bakul Shah <bakul@bitblocks.com>
Message-Id: <20140902200400.81EAAB827@mail.bitblocks.com>
Subject: Re: [9fans] silly question
Topicbox-Message-UUID: 14c9a0f4-ead9-11e9-9d60-3106f5b1d025

On Tue, 02 Sep 2014 15:10:56 EDT erik quanstrom <quanstro@quanstro.net> wrote:
> > Strftime is a red herring (sorry), I can use  and "date" | getline
> > to generate pretty much any date string I need.
> >
> > The issue is more going the other way. tm2sec in awk is quite complex
> > and hids many pitfalls if you want to do it correctly.
> >
> > My problem is parsing logfiles which contain dates in the form
> > of date(1) / ctime(2).
> >
> > I want to graph stuff over time and so I want a monotonically incrementing
> > number (secs sinc 1/1/70 would be ideal). I have coded this in awk but
> > for one year leap years break - though not by much.
>
> if the hair is just leap years, the algorithm used by /sys/src/libc/9sys/ctim
> e.c
> is pretty attractive.  the idea is to just loop through the years between giv
> en
> and 1970, and add a day for each leap year encountered.  should be easy
> to do in awk.

plan9 doesn't deal with leap seconds, right?  There've been 35
leap seconds since 1972 (International Atomic Time is 35
seconds ahead of GMT).  Though this probably doesn't matter
for timestamps in log files.