[comp.sys.ibm.pc] How to determine the filenames of open files

larry@focsys.UUCP (Larry Williamson) (03/23/89)

Is there someway I can determine the filenames of all the currently
open files?

I have an application that, after many hours of running, dies when
I try to open another file. The error is something like, "too many
open files."

It is our application, but we are calling a number of third party
library routines (GSS CGI is the main one) that open and (hopefully)
close temporary files. 

We cannot track down any place where we open a file and don't close
it, so we are beginning to suspect the other library routines. One
of them is possibly not closing some temp file. But who?

Any suggestions?

Thanks,
  -Larry.
-- 
Larry Williamson  -- Focus Systems -- Waterloo, Ontario
                  watmath!focsys!larry  (519) 746-4918

izumi@violet.berkeley.edu (Izumi Ohzawa) (03/24/89)

In article <408@focsys.UUCP> larry@focsys.UUCP (Larry Williamson) writes:
>Is there someway I can determine the filenames of all the currently
>open files?
>
>Any suggestions?

Run your application over PC Lan or PC Network.  Check on the server
with "net file" command.

Izumi Ohzawa,  izumi@violet.berkeley.edu

geoff@hinode.east.sun.com (Geoff Arnold) (04/05/89)

In article <408@focsys.UUCP> larry@focsys.UUCP (Larry Williamson) writes:
>Is there someway I can determine the filenames of all the currently
>open files?
>[...]
>We cannot track down any place where we open a file and don't close
>it, so we are beginning to suspect the other library routines. One
>of them is possibly not closing some temp file. But who?
>
>Any suggestions?
>
>Thanks,
>  -Larry.
>-- 
>Larry Williamson  -- Focus Systems -- Waterloo, Ontario
>                  watmath!focsys!larry  (519) 746-4918

It looks like you are without one of the most essential of all
DOS developer's tools: PCWATCH. This is an IBM product (from their
Pesonally Developed Software series, though I believe they
may have sold the reseller rights to someone else recently),
which allows you to monitor selected DOS system calls. If your
application uses full screen graphics, not to worry: you can
drop an MDA into the PC, hook up a monochrome monitor and redirect the
output to that. It's quite invaluable.

Geoff
Geoff Arnold,                              Internet: garnold@sun.com
Manager, PC-NFS Engineering                UUCP: ....!sun!garnold
PCDS Group, Sun Microsystems Inc.
*** I SPEAK ONLY FOR MYSELF *** (MY CHILDREN INSISTED THAT I SAY THAT) ***

nelson@sun.soe.clarkson.edu (Russ Nelson) (04/05/89)

Intercep (aka interc) is also quite handy.  It monitors dos calls and most
bios calls.  If you want me to post it to c.b.i.p, send mail.
--
--russ (nelson@clutx [.bitnet | .clarkson.edu])
If you can, help others.  If you can't,       |        Leftoid and proud of it
at least don't hurt others--the Dalai Lama    |