From: Roy Lanek <lanek@novenine.com>
Subject: ISO 8601 format (time)
Date: Mon, 12 Jun 2006 16:55:05 +0700 [thread overview]
Message-ID: <20060612095505.GA4978@kayumanis> (raw)
What about adding a ...
-ti
timestamp. Prefix each selected line with a human
readable, sortable, ISO 8601 compliant timestamp of
the form YYYY-MM-DDTHH:MM:SS.xxxxx when writing to log
or to standard error.
in the options of svlogd (runit/socklog)?
Notice the difference: -tt uses '_', -ti 'T' ... example:
2006-05-11_02:45:09.25607 vs. 2006-05-11T02:45:09.25607
-tt is fine, but not *standard* (ISO); on the other hand,
it can't be changed *a posteriori* that easily/quickly.
Cheers,
/Roy Lanek
--
######################## seperti pinang dibelah dua
##### . slackware ###### like a halved pinang
##### +-----linux ###### [means: two things that are quite different!, because
######################## you can never halve a pinang tree with an axe neatly]
next reply other threads:[~2006-06-12 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 9:55 Roy Lanek [this message]
2006-07-04 14:54 ` Gerrit Pape
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=20060612095505.GA4978@kayumanis \
--to=lanek@novenine.com \
/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).