Re: linux has added "close on exec" flags to lots of fd calls

To: tech-kern%NetBSD.org@localhost
Subject: Re: linux has added "close on exec" flags to lots of fd calls
From: der Mouse <mouse%Rodents-Montreal.ORG@localhost>
Date: Mon, 4 Aug 2008 23:37:32 -0400 (EDT)

>> Assume you are a library that wants to open a file, what mutex
>> should you lock ?
> Define one.

How do you ensure that you get the same mutex as the one the next
library over defines for _its_ file-open operations?

/~\ The ASCII                           der Mouse
\ / Ribbon Campaign
 X  Against HTML                mouse%rodents-montreal.org@localhost
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

References:
- linux has added "close on exec" flags to lots of fd calls
  - From: Perry E. Metzger
- Re: linux has added "close on exec" flags to lots of fd calls
  - From: Joerg Sonnenberger
- Re: linux has added "close on exec" flags to lots of fd calls
  - From: Joerg Sonnenberger
- Re: linux has added "close on exec" flags to lots of fd calls
  - From: Love Hörnquist Åstrand
- Re: linux has added "close on exec" flags to lots of fd calls
  - From: Joerg Sonnenberger

Prev by Date: Re: rfc: POSIX conformance
Next by Date: cpu_need_resched(t_vp->l_cpu, RESCHED_IMMED) for NetBSD-4
Previous by Thread: Re: linux has added "close on exec" flags to lots of fd calls
Next by Thread: Re: linux has added "close on exec" flags to lots of fd calls
Indexes:

Home | Main Index | Thread Index | Old Index