Subj : "stuck" open files
To   : Peter Knapper
From : Marc Lewis
Date : Sat Aug 13 2005 10:51 pm

Hello Peter!

     In your message you said:

 PK> Hi Marc,

 ML> I have run into a few occasions of a log file (Maximus
 ML> specifically) that have been left 'dirty'.

 PK> What OS (and version) and App (and version) are you
 PK> talking about?

Warp 4.52 FP3  Maximus/2 3.01

 PK> I have never seen an OS/2 version of Maximus leave any file
 PK> "open" at all, its always been very clean in that respect.

I would expect that, particularly from Maximus.  But somehow, twice now the 
MAX4.LOG has been left in an untouchable state.  Three finger salute was the 
only way I could figure to close it and allow Maximus to run on that node.

 ML> Is there a method of closing these
 ML> aberrant files other than rebooting the machine?
 PK> Are you sure that the Task that had the file open has in fact "gone"?

No, I'm not...

 PK> I can't recall ever seeing any OS/2 task hold open a
 PK> file after the task has gone. The times a file has
 PK> still been held "open", the process that last touched
 PK> that file was still present in the system, even though
 PK> it wasn't always "visible" to the average user.

I've tried using Ctrl+ a click on the task list icon in Warp Center to show the 
running processes, but it seemed inconclusive and a bit confusing.

 PK>  Grab a good process listing utilty such as TOP and see if
 PK> something is still running. Sometimes you may find the
 PK> odd task that becomes a true Zombie and cannot be
 PK> "touched" by anything, then you are simply out of
 PK> luck, but I have never seen Maximus like that.

Thanks, I track that down and see what it reveals the next time it happens. 
(Hopefully never!).

Best regards,
Marc
telnet://bbs.sursum-corda.com

-+- QuikEdit 2.41R+

--- Maximus/2 3.01
 * Origin: Sursum Corda! BBS-New Orleans 1-504-897-6006 USR33k6 (1:396/45)

.