;;; From: sugita@sra.co.jp
;;; Date: Tue, 16 Jul 2002 10:22:14 +0900 (JST)
;;;
;;; ;;; However, that doesn't explain our OS X problem. I added some debug
;;; ;;; printouts, and can now report positively that (a) the fork() call
;;; ;;; returns normally in the parent process, providing an apparently-correct
;;; ;;; child PID value; but (b) the fork never returns in the child. It
;;; ;;; doesn't ever get as far as trying to enable SIGTERM.
;;; &
;;; ;;; Is it possible that something in the child's fork() processing will wait
;;; ;;; around for a response from a service that's already died? Why is fork()
;;; ;;; dependent on any outside service whatever --- isn't that a certain
;;; ;;; recipe for system failures?
;;;
;;; I asked Apple this issue. This is a bug of Mac OS X. The problem is registered
;;; to their bug database for the appropriate eingineers for investigation.
This problem is fixed for Mac OS X 10.2.
Kenji Sugita
