Wednesday, July 28, 2004, 11:38:40 AM, David Teigland wrote: > On Wed, Jul 28, 2004 at 11:15:17AM -0400, Jeff wrote: >> dlm_unlock() is documented as being asynchronous and it >> takes an astarg as one of its arguments. However it does >> not take an AST routine as an argument. >> >> What routine gets executed when an unlock completes? > The AST routine from dlm_lock() is saved and used for dlm_unlock(). This makes it difficult to update an application which works with other DLM's as all the completion AST routines need to be updated to test for EUNLOCK to figure out why they've been invoked. Would it be possible to add an optional argument to dlm_unlock() for the AST routine to call when the unlock completes? If this is omitted, the existing completion AST routine is executed.
