Too many open file

We’ve beeen getting this message on one of our CPU here whenever we have
our software running for a while. I’ve used osinfo and did find any OS
limitations being exceeded. I believe this is a problem generated by Fsys,
as doing an ls //1/dev works, but not an ls //1/. Any ideal what could be
causing this?

Richard Doucet <NOdoucetr@aecl.caspam> wrote:

We’ve beeen getting this message on one of our CPU here whenever we have
our software running for a while. I’ve used osinfo and did find any OS
limitations being exceeded. I believe this is a problem generated by Fsys,
as doing an ls //1/dev works, but not an ls //1/. Any ideal what could be
causing this?

Have you looked at the output of “fsysinof //1/”?

-David

QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.

Richard Doucet <NOdoucetr@aecl.caspam> wrote:

We’ve beeen getting this message on one of our CPU here whenever we have
our software running for a while. I’ve used osinfo and did find any OS
limitations being exceeded. I believe this is a problem generated by Fsys,
as doing an ls //1/dev works, but not an ls //1/. Any ideal what could be
causing this?

To fix it, look at the -H option to Fsys…

This has come up before, search the archives for the “more detailed” answer…

Cheers,
-RK


[If replying via email, you’ll need to click on the URL that’s emailed to you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector http://www.parse.com/~pdp8/

Robert Krten <rk@parse.com> wrote:
RK > Richard Doucet <NOdoucetr@aecl.caspam> wrote:

We’ve beeen getting this message on one of our CPU here whenever we have
our software running for a while. I’ve used osinfo and did find any OS
limitations being exceeded. I believe this is a problem generated by Fsys,
as doing an ls //1/dev works, but not an ls //1/. Any ideal what could be
causing this?

RK > To fix it, look at the -H option to Fsys…

RK > This has come up before, search the archives for the “more detailed” answer…

RK > Cheers,
RK > -RK

Fsys uses some kind of internal (H)eap. The default values for this
heap are insuffient to deal with the larger disks of today. So you
need to up your Heap!

I don’t remember how to computer what a good new value should be. But
like Robert said, there are some old posts about it.

Seems to have worked. Is 60000 is sufficiently large number to specify
to -H? Would be nice to know what the default value is. We have a 40G
drive, but also need to configure some systems with 60G drive. Should be
use a larger value?

“Robert Krten” <rk@parse.com> wrote in message
news:bn9qnm$49$1@inn.qnx.com

Richard Doucet <> NOdoucetr@aecl.caspam> > wrote:
We’ve beeen getting this message on one of our CPU here whenever we
have
our software running for a while. I’ve used osinfo and did find any OS
limitations being exceeded. I believe this is a problem generated by
Fsys,
as doing an ls //1/dev works, but not an ls //1/. Any ideal what could
be
causing this?

To fix it, look at the -H option to Fsys…

This has come up before, search the archives for the “more detailed”
answer…

Cheers,
-RK


[If replying via email, you’ll need to click on the URL that’s emailed to
you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~pdp8/

Like Bill said, there’s a calculation somewhere in the news archives. It’s
rather complicated.

However, if you’re using the 4.25G release, you can just specify it
as -Hdisk40 or -Hdisk60, and the calculation is taken care of for you.

-Rob

“Richard Doucet” <NOdoucetr@aecl.caSPAM> wrote in message
news:bnb6o2$svl$1@inn.qnx.com

Seems to have worked. Is 60000 is sufficiently large number to specify
to -H? Would be nice to know what the default value is. We have a 40G
drive, but also need to configure some systems with 60G drive. Should be
use a larger value?

“Robert Krten” <> rk@parse.com> > wrote in message
news:bn9qnm$49$> 1@inn.qnx.com> …
Richard Doucet <> NOdoucetr@aecl.caspam> > wrote:
We’ve beeen getting this message on one of our CPU here whenever we
have
our software running for a while. I’ve used osinfo and did find any
OS
limitations being exceeded. I believe this is a problem generated by
Fsys,
as doing an ls //1/dev works, but not an ls //1/. Any ideal what
could
be
causing this?

To fix it, look at the -H option to Fsys…

This has come up before, search the archives for the “more detailed”
answer…

Cheers,
-RK


[If replying via email, you’ll need to click on the URL that’s emailed
to
you
afterwards to forward the email to me – spam filters and all that]
Robert Krten, PDP minicomputer collector > http://www.parse.com/~pdp8/