system wide semaphores problem

Rob Savoye <[email protected]> Sun, 11 Aug 2002 13:29:07 -0600
Newsgroups gmane.linux.ngpt.user
Message-ID <[email protected]>
  I'm trying to port an application from Solaris, and I seem to be having
problems with system wide shared semaphores. (sem_init(,1,)). I've gone
through the kernel patch carefully to make sure I didn't forget anything,
and I've spent a few days trying diferent things, and reading through
the list archives. Before I say screw it, and rewrite this code to ue Sys V
semaphores, I figured I'd ask around.

  I'm using ngpt-2.0.0 on 2.4.18-5 (Redhat kernel branch). NGPT installs
fine, and other than a problem with fastlock not being defined, my application
compiles beautifully. All usages of semaphores for threads works great. The
problem is for shared semaphores. The child process core dumps as soon as
it tries to lock/unlock the semapore which was created by the parent process. 

  I've made sure /dev/shm is mounted (none on /dev/shm type tmpfs (rw)), I
run ngptinit in rc.local or by hand, and no such luck. The first access by the
child process always crashes. Any ideas ? I'd really love to able to claim
Linux's pthread support is now as good as Solaris's or HPUX's. (well, closer :-)

  I also never found any mention of pubic readonly access to CVS ? (other than
through cvsweb)

	- rob