Operating Systems > Linux and UNIX

How big is PID??

<< < (2/2)

caveman_piet:
Yep - I've been monitoring the system
the past day - and it wraps at 32k numbers.
Re-using unused numbers. Done that about
three times in the past 24 hrs.

Had to stop the jobs this evening to get some
bugs/enhancements in.

So the next test takes about 3-4 days of non
stop running. An thats where we reckon the
file handles gets used up - (nothing else
seems to make sense)..

In brief - 4 main processes each fork of 1 or 2
child processes which then activate the next
layer of jobs using "execl". These jobs can
run anything between 5 seconds and many minutes
depending on the system load and terminates
with an "_exit". After about 3-4 days -
everything apparently just stops. I haven't
seen this yet - so waiting,waiting waiting....

The system is home grown using suse 7.3 kernel - built on a 64 MB flash disc and 128 MB of memory.

Q -
{
if ((msgctl(y_QueueNo[Name], IPC_STAT, &Buffer)) < -1)
syslog(LOG_ERR, "QStat: Message ctl failed; %m");
return (Buffer.b_qnum);
}
usually gives back the number of entries on a queue. But blocks with no return
after a while when the queue is full. Any
suggestions?

TX.

voidmain:
You wouldn't happen to have the source for the app in question would you? Have you checked for the number of "fopen()"s vs the number of "fclose()"s? And whether or not the program could terminate without closing a file?

Again you can use "lsof" to determine the number of files that are opened either totally or process by process. Do a "man lsof" for the extensive list of options.

[ January 10, 2003: Message edited by: void main ]

Navigation

[0] Message Index

[*] Previous page