‡Ć `Nö9csÚdZdkZdkZdkZdkZdklZy(eiƒddjo ed‚nWnej onXy ei Wnej oed‚nXdZ dZ d Z hZ dZd „Zd „ZeƒdS( s™This test checks for correct fork() behavior. We want fork1() semantics -- only the forking thread survives in the child after a fork(). On some systems (e.g. Solaris without posix threads) we find that all active threads survive in the child after a fork(); this is an error. On BeOS, you CANNOT mix threads and fork(), the behaviour is undefined. That's OK, fork() is a grotesque hack anyway. ;-) [cjh] N(s TestSkippedisBeOSs&can't mix os.fork with threads on BeOSs*os.fork not defined -- skipping test_fork1if0.5icsKxDt o;tiƒt|