sem(4) lockup in python?

[Ivan Voras]

On 11 January 2012 17:47, Garrett Cooper <yanegomi at gmail.com> wrote:

> when doing interactive builds as well. The issue appears to be
> exacerbated when we have more builds running in parallel on the same
> machine. I've also run into the same issue compiling talloc because it
> uses the same waf infrastructure as tdb, which was designed to "speed
> things up by forcing builds to be parallelized" (It builds
> kern.smp.ncpus jobs instead of -j 1). Furthermore, it seems to occur
> regardless of whether or not we have the WITH_SEM enabled in python or
> not

... which is interesting as I've habitually enabled WITH_SEM on 8.x
systems and there it worked without problems. Must be the new code.