In reviewing my uvdlockd.log, I see that even when the deadlock daemon isn't running, it looks like it's being run. Does executing uvlictool clean_lic -a call the deadlock process?
Also, in configuring the daemon's resolution strategy, there are three options; random termination, terminate newest transaction, or terminate the transaction with fewest locks. I have chosen to terminate the newest, but I was little more than flipping a coin... simply using the 'first come, first server' approach. I can't seem to find anything in the documentation that would help me decide which resolution strategy I *should* employ. Any ideas? Mark Hennessey State of Connecticut DSS/MIS Child Support Systems Voice: 860-424-5261 Fax: 860-424-4956 ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
