Clearing table locks

Path: emory!swrinde!zaphod.mps.ohio-state.edu!ncar!csn!cherokee!cherokee!bruce From: bruce@patton.USWest.COM ( Bruce W. Hoylman x5806 ) Newsgroups: comp.databases.informix Message-ID: <BRUCE.91Dec11202149@patton.USWest.COM> Date: 12 Dec 91 03:21:49 GMT Sender: news@cherokee.uswest.com (Telegraph Row) Organization: U S West Advanced Technologies Nntp-Posting-Host: patton.uswest.com Now that Informix 4.XX no longer offers the ".lok" file if your machine supports kernel locking, how does one go about clearing mutant or unwanted locks on a table? It used to be one could cat /dev/null to the .lok file and bingo. Even as the dba/owner of the database/tables, I cannot unlock the table. This really hoses the late night backup utilities which used to be able to clear the locks of folks that leave an interface up and unattended overnight, for example. I don't have root access, so killing processes isn't an option. Let me add that I *know* the tables are not in use so clearing the locks would not effect table data integrity. Any suggestions/hints/clever anecdotes? Email responses are preferred and I can certainly post a summary if interest warrants. Thanks. Later ... -- Bruce W. Hoylman (303-541-6557) -- bruce@USWest.COM if [ -n ${CYCLE} -a ${SOIL_SAMPLE} ]; then __o echo '** stump fault -- biker dump **'; fi >/dev/bummer -\\<, "Cold Filtered, because you don't know what that means." ......O/ O...