From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] silly question
Date: Tue, 2 Sep 2014 19:18:39 +0100 [thread overview]
Message-ID: <346c54679a6cdc9bb557724d8b93bbc6@quintile.net> (raw)
In-Reply-To: <ab993a34ff2fe79b6e6ebfe90baa437e@ladd.quanstro.net>
> i'm not sure what your particular problem domain is since you don't say
True.
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.
This is why I was asking if there was an external app called somthing like
tm2sec which calls its eponomymous library function.
it seems there isn't one and its the work of 30secs to write one, no problem,
I just thought there was one but I had forgotten its name...
-Steve
next prev parent reply other threads:[~2014-09-02 18:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 7:07 Steve Simon
2014-09-02 8:27 ` lucio
2014-09-02 8:46 ` arnold
2014-09-02 9:40 ` Jens Staal
2014-09-02 14:07 ` arnold
2014-09-02 14:22 ` Steve Simon
2014-09-02 14:29 ` arnold
2014-09-02 17:02 ` erik quanstrom
2014-09-02 18:18 ` Steve Simon [this message]
2014-09-02 19:10 ` erik quanstrom
2014-09-02 20:04 ` Bakul Shah
2014-09-02 21:05 ` erik quanstrom
2014-09-02 21:50 ` Kurt H Maier
2014-09-02 23:00 ` erik quanstrom
2014-09-02 23:04 ` Bakul Shah
2014-09-02 23:19 ` erik quanstrom
2014-09-02 23:29 ` Bakul Shah
2014-09-02 21:10 ` Skip Tavakkolian
2014-09-02 21:14 ` Steve Simon
2014-09-02 21:27 ` Bakul Shah
2014-09-02 21:43 ` Skip Tavakkolian
2014-09-02 18:36 ` Kurt H Maier
2014-09-02 19:18 ` Steve Simon
2014-09-02 23:34 sl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=346c54679a6cdc9bb557724d8b93bbc6@quintile.net \
--to=steve@quintile.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).