Hello, During the course of execution of our filesystem there will be times when socket calls will be made that will sleep. The simple ones are soaccept on connections and soreceive on buffer, but there ares also times when the socket call will sleep due to memory acquisition and other unexpected reasons. Our filesystem requires a mechanism to wake up these calls and give an indication that the thread was interrupted/awoken. This indicator could be through an error or alternatively handle by our own code. But the mechanism to wake up the calls is MacOSX specific and even if we play with internal structures to mimic this... the outcome will be an OS version specific hack that can only be expected to handle the *obvious* conditions. Could somebody give me the supported mechanisms to wakeup/interrupt socket calls which will support all (hopefully) the cases that they could sleep. This is very important due to our filesystem being in a clustered network that must handle failover and redistribution. Thanks. -- Wally Crooze +-------------------------------------------------------+ | ,-_|\ Wally Crooze <wallycrooze@pobox.com> | | / \ | | \_,-._/ | | v | +-------------------------------------------------------+ _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.