Yes, uvlictool clean_lic does execute the same "clean up" code as the deadlock daemon, even unto logging to the same file. I don't believe it actually starts a uvdlockd process, however.
There is no documentation on strategy, because none is really to be preferred over the others in all cases. You need to decide what's right for you. My personal preference is not to enable automatic resolution at all, but instead to "choose victim" after weighing up the circumstances. Of course, it is then necessary to monitor the log to determine when a deadlock situation has been detected. In two years we've not had any, other than one created deliberately for testing the process. ----- Original Message ----- From: "Hennessey, Mark F." <[EMAIL PROTECTED]> To: [email protected] Subject: [U2] UV dead lock daemon questions Date: Wed, 19 Oct 2005 11:37:10 -0400 > > 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/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
