I’m sure I knew the answer to this once, but it currently eludes me. My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an edit
session or killing a photon window allows things to be done again.
What do I need to increase?
thanks
Julian Thornhill
One possibility is pseudo-teletypes. Another might be sessions. A third,
less likely, is process slots.
Julian Thornhill wrote:
I’m sure I knew the answer to this once, but it currently eludes me. My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an edit
session or killing a photon window allows things to be done again.What do I need to increase?
thanks
Julian Thornhill
Julian Thornhill wrote:
I’m sure I knew the answer to this once, but it currently eludes me. My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an edit
session or killing a photon window allows things to be done again.What do I need to increase?
thanks
Julian Thornhill
Dean Douthat <> ddouthat@faac.com> > wrote in message
news:3ABA168A.CDB9B0CD@faac.com…
One possibility is pseudo-teletypes. Another might be sessions. A third,
less likely, is process slots.
Thanks for the response.
Not ptty’s, since quitting a text mode editor, but keeping its pterm window
open frees the problem. Where are session limits configured?
thanks
Julian Thornhill
Get osinfo off of the website. It keeps track of peak use of common
resources.
-----Original Message-----
From: Julian Thornhill [mailto:jth@ion.le.ac.uk]
Posted At: Thursday, March 22, 2001 5:42 AM
Posted To: qnx4
Conversation: Resource temporarily unavailable - what causes this msg?
Subject: Resource temporarily unavailable - what causes this msg?
I’m sure I knew the answer to this once, but it currently eludes me. My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an edit
session or killing a photon window allows things to be done again.
What do I need to increase?
thanks
Julian Thornhill
Julian Thornhill <jth@ion.le.ac.uk> wrote:
Julian Thornhill wrote:
I’m sure I knew the answer to this once, but it currently eludes me. My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an edit
session or killing a photon window allows things to be done again.What do I need to increase?
thanks
Julian Thornhill
Dean Douthat <> ddouthat@faac.com> > wrote in message
news:> 3ABA168A.CDB9B0CD@faac.com> …
One possibility is pseudo-teletypes. Another might be sessions. A third,
less likely, is process slots.Thanks for the response.
Not ptty’s, since quitting a text mode editor, but keeping its pterm window
open frees the problem. Where are session limits configured?
You might try grabbing the “osinfo” (the archive is actually os_info.tgz)
utility – it tends to monitor a bunch of different things. Most of
these things are configured on Proc’s command line.
QNX Training Services
dagibbs@qnx.com
“Julian Thornhill” <jth@ion.le.ac.uk> wrote in message
news:99clvo$t8o$1@inn.qnx.com…
I’m sure I knew the answer to this once, but it currently eludes me.
My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an
edit
session or killing a photon window allows things to be done again.
I have seen this most commonly with either
Remember that processes are counted as real processes + proxies + virtual
circuits. Programs with bugs in their virtual circuit handling can easily
gobble
all available process spaces.
Cheers,
Andrew
Curious. Are you by any chance also running Ctree (database) on this
system?
Julian Thornhill wrote:
I’m sure I knew the answer to this once, but it currently eludes me. My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an edit
session or killing a photon window allows things to be done again.What do I need to increase?
thanks
Julian Thornhill
Sessions and process slots are configured by command line arguments to Proc.
You’ll need to build a new boot image to change them.
Julian Thornhill wrote:
Julian Thornhill wrote:
I’m sure I knew the answer to this once, but it currently eludes me. My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an edit
session or killing a photon window allows things to be done again.What do I need to increase?
thanks
Julian Thornhill
Dean Douthat <> ddouthat@faac.com> > wrote in message
news:> 3ABA168A.CDB9B0CD@faac.com> …
One possibility is pseudo-teletypes. Another might be sessions. A third,
less likely, is process slots.Thanks for the response.
Not ptty’s, since quitting a text mode editor, but keeping its pterm window
open frees the problem. Where are session limits configured?thanks
Julian Thornhill
“Rick Lake” <rwlake@SPAM.REDIRECTED.TO.DEV.NULL> wrote in message
news:3ABA6487.64C8B49B@SPAM.REDIRECTED.TO.DEV.NULL…
Curious. Are you by any chance also running Ctree (database) on this
system?No. It started happening after I started using a second QNX node, runing
phditto, to extend my original node’s desktop across two monitors. Both
systems are straightforward 4.25 systems with the released updates applied.
Just running the Watcom C compiler and a few edit sessions.
If I find the cause (thanks to those that mentioned osinfo) I’ll report
back…
Julian
If I find the cause (thanks to those that mentioned osinfo) I’ll report
back…It was a program I’d written that did a qnx_name_locate() every two seconds.
I did not realise that every call created another VC
Thanks for telling me about osinfo - did the trick
Julian
just a quick note on that osinfo program… it only does snapshots of the
system at defined intervals, so it will not capture resource usage if it
happens in a flurry between snapshots. but it is still useful to see how
close to the edge your default running system is.
and usually a program that grabs a resource (like fds or vc’s or memory)
doesn’t free it up right away anyway… so it is useful to trap those
conditions.
Rennie Allen <RAllen@csical.com> wrote:
Get osinfo off of the website. It keeps track of peak use of common
resources.-----Original Message-----
From: Julian Thornhill [mailto:> jth@ion.le.ac.uk> ]
Posted At: Thursday, March 22, 2001 5:42 AM
Posted To: qnx4
Conversation: Resource temporarily unavailable - what causes this msg?
Subject: Resource temporarily unavailable - what causes this msg?
I’m sure I knew the answer to this once, but it currently eludes me. My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an edit
session or killing a photon window allows things to be done again.What do I need to increase?
thanks
Julian Thornhill
–
Randy Martin randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579
Hmmm, I wasn’t aware that the peaks were peaks from the snapshots. I
assumed that Proc had internal peak hit counters for common resources.
Seems like it wouldn’t really be much overhead for Proc to do an
additional cmp/(conditional)mov on each resource
allocation/deallocation. One question Randy, what about the “no
abnormal deaths since” feature, I am hoping that it doesn’t only record
processes that happen to be terminating when osinfo polls ?
The things I have typically looked for with osinfo, have (apparently)
always been slow enough to be caught by osinfo, but it would certainly
be better if the peak usage were recorded by Proc, and simply reset by
osinfo when it starts.
-----Original Message-----
From: Randy Martin [mailto:randy@qnx.com]
Posted At: Friday, March 23, 2001 9:59 AM
Posted To: qnx4
Conversation: Resource temporarily unavailable - what causes this msg?
Subject: Re: Resource temporarily unavailable - what causes this msg?
just a quick note on that osinfo program… it only does snapshots of
the
system at defined intervals, so it will not capture resource usage if it
happens in a flurry between snapshots. but it is still useful to see how
close to the edge your default running system is.
and usually a program that grabs a resource (like fds or vc’s or memory)
doesn’t free it up right away anyway… so it is useful to trap those
conditions.
Rennie Allen <RAllen@csical.com> wrote:
Get osinfo off of the website. It keeps track of peak use of common
resources.-----Original Message-----
From: Julian Thornhill [mailto:> jth@ion.le.ac.uk> ]
Posted At: Thursday, March 22, 2001 5:42 AM
Posted To: qnx4
Conversation: Resource temporarily unavailable - what causes this msg?
Subject: Resource temporarily unavailable - what causes this msg?
I’m sure I knew the answer to this once, but it currently eludes me.
My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an
edit
session or killing a photon window allows things to be done again.What do I need to increase?
thanks
Julian Thornhill
the ‘no abnormal deaths’ is a poll of the directory where dumper puts its
files. simply a convenience message so that i can see if anything died and
where/when it died.
Rennie Allen <RAllen@csical.com> wrote:
Hmmm, I wasn’t aware that the peaks were peaks from the snapshots. I
assumed that Proc had internal peak hit counters for common resources.
Seems like it wouldn’t really be much overhead for Proc to do an
additional cmp/(conditional)mov on each resource
allocation/deallocation. One question Randy, what about the “no
abnormal deaths since” feature, I am hoping that it doesn’t only record
processes that happen to be terminating when osinfo polls ?The things I have typically looked for with osinfo, have (apparently)
always been slow enough to be caught by osinfo, but it would certainly
be better if the peak usage were recorded by Proc, and simply reset by
osinfo when it starts.-----Original Message-----
From: Randy Martin [mailto:> randy@qnx.com> ]
Posted At: Friday, March 23, 2001 9:59 AM
Posted To: qnx4
Conversation: Resource temporarily unavailable - what causes this msg?
Subject: Re: Resource temporarily unavailable - what causes this msg?
just a quick note on that osinfo program… it only does snapshots of
the
system at defined intervals, so it will not capture resource usage if it
happens in a flurry between snapshots. but it is still useful to see how
close to the edge your default running system is.
and usually a program that grabs a resource (like fds or vc’s or memory)doesn’t free it up right away anyway… so it is useful to trap those
conditions.Rennie Allen <> RAllen@csical.com> > wrote:
Get osinfo off of the website. It keeps track of peak use of common
resources.-----Original Message-----
From: Julian Thornhill [mailto:> jth@ion.le.ac.uk> ]
Posted At: Thursday, March 22, 2001 5:42 AM
Posted To: qnx4
Conversation: Resource temporarily unavailable - what causes this msg?
Subject: Resource temporarily unavailable - what causes this msg?
I’m sure I knew the answer to this once, but it currently eludes me.
My
development system sometimes refuses to execute anything at the shell
prompt, giving “resource temporarily unavailable”. Shutting down an
edit
session or killing a photon window allows things to be done again.What do I need to increase?
thanks
Julian Thornhill
–
Randy Martin randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579