I guess the first question to ask is: Do you ever dup that file
descriptor?  The io_ocb_close() is only called once all open handles
(fds) to the OCB are closed.  You can register a "close_dup" function
and see if that handler gets called when the thread closes the file
descriptor.

David Sarrazin

> -----Original Message-----
> From: Gordon Molek [mailto:community-noreply@qnx.com] 
> Sent: July 30, 2008 12:11 PM
> To: ostech-core_os
> Subject: File System Resource Manager question
> 
> I'm not sure if this is the right place to ask this, but as 
> part of our project we're creating a special purpose file 
> system resource manager.  We're creating a "FIFO"-like set of 
> files which support blocking and non-blocking access.  We 
> have a process that opens a file and spawns a thread that 
> does a blocking read on the file descriptor.  At some future 
> time, another thread closes the file descriptor.  Our file 
> system resource manager does not get an "io_close_ocb()" 
> call.  Should it?  Since file descriptors are shared across 
> threads of a process we would have expected the 
> io_close_ocb() call to happen.
> 
> Thanks,
> 
> Gordon Molek
> Zebra Technologies Corp.
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post11249
> 
>