mò ­fIc@s¨dZdkZdkZdkZdkZdklZlZlZy ei Wne j oed‚nXdZ dZ dZ hZdad„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. While BeOS doesn't officially support fork and native threading in the same application, the present example should work just fine. DC N(sverifysverboses TestSkippeds*os.fork not defined -- skipping test_fork1if0.5iicCsJxCtp;tiƒt|