From: "Ted Ts'o" <tytso@mit.edu>
To: Tim Pepper <tpepper@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: libuuid clock.txt fd leaks
Date: Wed, 21 Sep 2011 17:15:33 -0400 [thread overview]
Message-ID: <20110921211533.GA3032@thunk.org> (raw)
In-Reply-To: <20110921202620.GD4056@thunk.org>
On Wed, Sep 21, 2011 at 04:26:20PM -0400, Ted Ts'o wrote:
> Part of the problem is that the uuid library was originally designed
> non-thread-using libraries, and I originally was trying to force all
Sigh, s/to force/to avoid forcing/
> programs to link against -lpthread. (Remember, libuuid as found in
> e2fsprogs predates Linux having a standardized threads support, or any
> threads support at all.)
- Ted
next prev parent reply other threads:[~2011-09-21 21:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 16:58 libuuid clock.txt fd leaks Tim Pepper
2011-09-21 20:26 ` Ted Ts'o
2011-09-21 21:15 ` Ted Ts'o [this message]
2011-09-21 22:02 ` Tim Pepper
2011-09-21 22:19 ` Tim Pepper
2011-09-21 22:24 ` Ted Ts'o
2011-09-21 22:32 ` Tim Pepper
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=20110921211533.GA3032@thunk.org \
--to=tytso@mit.edu \
--cc=tpepper@gmail.com \
--cc=util-linux@vger.kernel.org \
/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