| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 5942.1 |  | TARKIN::LIN | Bill Lin | Mon Apr 21 1997 16:11 | 8 | 
|  |     re: OTOOA::kap901.kao.dec.com::trimble
    
    Hi Jason,
    
    Do you mean other than using the Server applet in Control Panel or
    double clicking on a System Name in Srvmgr in a domain?
    
    Bill
 | 
| 5942.2 | Yes, besides Server Manager | OTOOA::kap901.kao.dec.com::trimble |  | Tue Apr 22 1997 11:31 | 7 | 
|  | Yes.  That method does not show the file in question
as being locked by anything.  Yet when I try to 
delete it, it fails saying it's open by another
process.
Jason
 | 
| 5942.3 |  | MARVIN::GOODWIN | Pete Goodwin | Wed Apr 23 1997 01:20 | 6 | 
|  |     I've seen this - files that the system claims as being locked yet
    there's no way to find out what's locking it. Nothing shows up in the
    Server applet in the control panel. The only way I've found to get
    round locked files is to either reboot or rename the file!
    
    Pete.
 | 
| 5942.4 | I'd be interested in knowing how also... | TARKIN::LIN | Bill Lin | Wed Apr 23 1997 02:11 | 6 | 
|  |     The server applet is only useful for connections to file made via the
    network I believe.  I haven't found a way to view lock information for
    connections from local processes to local disk resources.  Sorry for my
    misinterpretation of the base note.
    
    /Bill
 | 
| 5942.5 | These guys make good stuff | nova05.vbo.dec.com::BERGER |  | Wed Apr 23 1997 03:09 | 8 | 
|  | This might be a job for NT Filemon, see
http://www.ntinternals.com/ntfilmon.htm
Note that I've had personally mixed experience with this thing, going 
from instant blue screen crash to not doing anything useful, so 
beware, don't install it on a production server. YMMV
	Vincent
 | 
| 5942.6 | It is a production server | OTOOA::kap901.kao.dec.com::trimble |  | Thu Apr 24 1997 12:25 | 14 | 
|  | RE: -1
That utility simply logs file activity.  It doesn't look like it 
actually tells who did the activity, at least not in their 
screen shot.  Besides, this *IS* a production server and I can't
just reboot it on a whim, nor can I run programs which may bring
it down.  I thought there would be a simple lovely utility (even
in the resource kit) that might answer my problem, but I guess 
it's looking more like I'll have to schedule it for a reboot.
Regards,
Jason
 |