how many fds opened?
Re: how many fds opened?
inn.qnx.com <tburhan@dodo.com.au> wrote:
From inside the process that has the fds open, from outside?
The information is probably available by using devctl()s on the
/proc filesystem -- I just don't know the right ones off-hand.
-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Per-process? System wide? Per server?Can we find out how many fds are opened in QNX through code??
From inside the process that has the fds open, from outside?
The information is probably available by using devctl()s on the
/proc filesystem -- I just don't know the right ones off-hand.
-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Re: how many fds opened?
Spin shows that information, along other things.
-- igor
"David Gibbs" <dagibbs@qnx.com> wrote in message
news:bq7t1n$l9e$2@nntp.qnx.com...
-- igor
"David Gibbs" <dagibbs@qnx.com> wrote in message
news:bq7t1n$l9e$2@nntp.qnx.com...
inn.qnx.com <tburhan@dodo.com.au> wrote:
Can we find out how many fds are opened in QNX through code??
Per-process? System wide? Per server?
From inside the process that has the fds open, from outside?
The information is probably available by using devctl()s on the
/proc filesystem -- I just don't know the right ones off-hand.
-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.
Re: how many fds opened?
Hi,
As you talk about spin Igor, I want to tell you about a problem you may
know yet.
When you launch spin with default parameters, you start it with a 1
second refresh delay.
The problem is that you initialize the 1 second timer with the nsec
timespec field:
itime.it_value.tv_sec = 0;
itime.it_value.tv_nsec = interval/10;
itime.it_interval.tv_sec = 0;
itime.it_interval.tv_nsec = interval;
Strangely that works on many targets but hangs on some others, the timer
never fires.
I suggest you take care about interval value to initialize correctly the
structure using nsec or sec or limit the interval value to 990
micro-second and set the default value accordingly.
Cheers,
Alain.
Igor Kovalenko a écrit:
As you talk about spin Igor, I want to tell you about a problem you may
know yet.
When you launch spin with default parameters, you start it with a 1
second refresh delay.
The problem is that you initialize the 1 second timer with the nsec
timespec field:
itime.it_value.tv_sec = 0;
itime.it_value.tv_nsec = interval/10;
itime.it_interval.tv_sec = 0;
itime.it_interval.tv_nsec = interval;
Strangely that works on many targets but hangs on some others, the timer
never fires.
I suggest you take care about interval value to initialize correctly the
structure using nsec or sec or limit the interval value to 990
micro-second and set the default value accordingly.
Cheers,
Alain.
Igor Kovalenko a écrit:
Spin shows that information, along other things.
-- igor
"David Gibbs" <dagibbs@qnx.com> wrote in message
news:bq7t1n$l9e$2@nntp.qnx.com...
inn.qnx.com <tburhan@dodo.com.au> wrote:
Can we find out how many fds are opened in QNX through code??
Per-process? System wide? Per server?
From inside the process that has the fds open, from outside?
The information is probably available by using devctl()s on the
/proc filesystem -- I just don't know the right ones off-hand.
-David
--
QNX Training Services
http://www.qnx.com/support/training/
Please followup in this newsgroup if you have further questions.