Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga
Subject: Re: File sources
Keywords: C, file manipulation, lock
Message-ID: <966@lpami.wimsey.bc.ca>
Date: 31 Dec 89 16:04:17 GMT
Lines: 24
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <2629@jolnet.ORPK.IL.US>, caw@jolnet.ORPK.IL.US (Chris Wichura) writes:
> 
>Also, always remember to UnLock() locks you have obtained or you could
>keep the system from fully accessing a file and the only way to get
>access back is to reboot the system (unless someone has written a utility 
>to UnLock specific locks [I forget if XOper has a function to do this]).

Khalid Aldoseri wrote a 'locks' program, based loosely on one that was posted
to the net some time ago. Khalid's version allows you to both view and remove
locks left lying around by errant programs. I don't think it's been posted to
Usenet, though I know it's on Compuserve (AmigaTech, LIB 13 or 14). It's a
little dangerous if you aren't careful or don't know what you're doing, but is
incredibly handy when you need it.

-larry

--
" All I ask of my body is that it carry around my head."
         - Thomas Alva Edison -
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+