From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@9fans.net
Subject: Re: [9fans] a pair nec bugs
Date: Sun, 22 May 2011 14:30:53 +0100 [thread overview]
Message-ID: <506039e1e4114f7d4d49936ba8bd9217@terzarima.net> (raw)
In-Reply-To: <9b37d225088bda8d7f0dfae5d506837c@brasstown.quanstro.net>
[-- Attachment #1: Type: text/plain, Size: 257 bytes --]
>time calls an internal function, oldtime(),
>that adds another private file descriptor.
that's only a fall-back if the call
to nsec doesn't work because you're running on a kernel
that's years and years out of date; so it isn't really
relevant here.
[-- Attachment #2: Type: message/rfc822, Size: 1862 bytes --]
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] a pair nec bugs
Date: Sat, 21 May 2011 23:06:23 -0400
Message-ID: <9b37d225088bda8d7f0dfae5d506837c@brasstown.quanstro.net>
On Sat May 21 18:12:35 EDT 2011, forsyth@terzarima.net wrote:
> >and time(2).
>
> i didn't include that because it calls nsec
time calls an internal function, oldtime(),
that adds another private file descriptor.
i suppose that could be killed off by now.
- erik
next prev parent reply other threads:[~2011-05-22 13:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 1:30 erik quanstrom
2011-05-20 5:05 ` [9fans] a pair nsec bugs erik quanstrom
2011-05-20 10:43 ` [9fans] a pair nec bugs ron minnich
2011-05-20 10:52 ` roger peppe
2011-05-20 10:57 ` ron minnich
2011-05-20 12:47 ` erik quanstrom
2011-05-20 19:03 ` ron minnich
2011-05-20 19:16 ` erik quanstrom
2011-05-21 3:27 ` erik quanstrom
2011-05-21 9:59 ` Charles Forsyth
2011-05-21 12:16 ` erik quanstrom
2011-05-21 21:50 ` erik quanstrom
2011-05-21 22:14 ` Charles Forsyth
2011-05-22 3:06 ` erik quanstrom
2011-05-22 13:30 ` Charles Forsyth [this message]
2011-06-02 19:16 ` erik quanstrom
2011-06-03 9:52 ` Charles Forsyth
2011-06-04 18:12 ` adriano
2011-06-03 13:13 erik quanstrom
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=506039e1e4114f7d4d49936ba8bd9217@terzarima.net \
--to=forsyth@terzarima.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).