On Oct 21, 8:08 pm, Philip Semanchuk <[EMAIL PROTECTED]> wrote: > On Oct 21, 2008, at 6:45 PM, [EMAIL PROTECTED] wrote: > > > It seems that the multiprocessing module in 2.6 is broken for *BSD; > > I've seen issue 3770 regarding this. I'm curious if there are more > > details on this issue since the posts in 3770 were a bit unclear. For > > example, one post claimed that the problem was that sem_open isn't > > implemented in *BSD, but it is available on FreeBSD 7 (I checked). I'd > > be willing to help get this working if someone could point me in the > > right direction. > > Hi Al, > I don't know anything about the multiprocessing module, but I have > some recent experience with the semaphores on FreeBSD 6 & 7 as a > result of implementing my posix_ipc module. > > Since you mentioned sem_open, I assume you're talking about POSIX > semaphores, rather than System V semaphores, yes? On FreeBSD 6 & 7 > sem_open exists and works, but support for said semaphores are listed > as "very experimental". I experienced a problem that looked like a bug > to me, and a rather big one at that. There's more detail here (scroll > down to the part about FreeBSD 6/7) including a link to the bug report > I filed against the FreeBSD kernel: > > http://semanchuk.com/philip/posix_ipc/#platforms > > HTH > Philip
Thanks for the background on FreeBSD semaphores. I read through the link; it should help. -- http://mail.python.org/mailman/listinfo/python-list
