Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Arbitrary shared memory file path for shm_open: (3 Items)
   
Arbitrary shared memory file path for shm_open  
I noticed in the library manual of QNX 6.3 that QNX now supports arbitrary path names for shared memory files created by
 shm_open, which was not the case before(at that time only paths with one slash('/') could be used as a shared memory 
file name).

So I want to know since when (which version of QNX, which year/month) did QNX operating system start supporting 
arbitrary path for shared memory files?

Thanks. 
RE: Arbitrary shared memory file path for shm_open  
 

> -----Original Message-----
> From: David Zhao [mailto:david.zhao@oracle.com] 
> Sent: September 21, 2007 12:45 AM
> To: ostech-core_os
> Subject: Arbitrary shared memory file path for shm_open
> 
> I noticed in the library manual of QNX 6.3 that QNX now 
> supports arbitrary path names for shared memory files created 
> by shm_open, which was not the case before(at that time only 
> paths with one slash('/') could be used as a shared memory file name).
> 
> So I want to know since when (which version of QNX, which 
> year/month) did QNX operating system start supporting 
> arbitrary path for shared memory files?

As far as I can tell, we have always supported them.  What is
different is that the documentation didn't reflect this.  

At least on the library side, we have always supported the
creation of a 'local' shared object if you didn't specify
a leading / on the name.

What are you trying to accomplish?

Hope this helps,
 Thomas
Re: RE: Arbitrary shared memory file path for shm_open  
Thanks, this is good news. 

We are developing the Oracle Berkeley DB product, which is a very powerful, efficient and scalable embeded database 
library widely used on various platforms, ranging from embeded systems to high-end servers.

Berkeley DB has a QNX port, and we are testing our product for portablilty on latest version of QNX. 

For previous versions of QNX, there was a path conversion workaround for shm_open path names in BDB, may be it is no 
longer needed now. :)

Thanks.