lkml.org 
[lkml]   [1999]   [May]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: FD_CLFORK or equivalent?
On Tue, 4 May 1999, Sam Roberts wrote:

>
> Hi,
>
> This is a question about implementing a module access policy
> where only the process that opened a device can have a copy
> of that fd, i.e. I want the fd closed on fork().
>
switch(fork())
{
case 0: /* Child */
(void)close(fd);


In Unix, we close what we want, when we want.


Cheers,
Dick Johnson
***** FILE SYSTEM WAS MODIFIED *****
Penguin : Linux version 2.2.6 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:51    [from the cache]
©2003-2011 Jasper Spaans. Advertise on this site