Hi, I am using Linux version- OpenSSL 0.9.7a Feb 19 2003 built on: Thu May 19 18:22:25 EDT 2005 platform: linux-elf options: bn(64,32) md2(int) rc4(idx,int) des(ptr,risc1,16,long) blowfish(idx)

My problem is that when I run a process (say ./gw), a large no. of different PIDs(around 150) are getting created with only single PPID. This also interrupts other processes to execute.

Can anyone please suggest what can I do here?

What is ./gw and does this occur on any other command or process you start? What are these other processes? Output of ps would be helpful.

you could try 'nicing' the process so that it (and I think the child processes) will be nicer to the other processes.

For example, I have a program that competes with production processes that still needs to run --
nice -n19 ./myprocess

Note: nicing or renicing process overrides the process priority the kernel assigns. -19 is as nice (aka as low of priority) as you can go. +20 is a "mean" process and requires root privelidges to change above 0.

Or you could try putting the process into the background --
./myprocess &

That would only help these 150 processes behave a little better. As far as the 150 children my first guess is that your application has defined 150 worker/child processes for the parent, but have little else to go on since we have no idea what "./gw" is.

Also, what do your resources look like? free -mt, top...are you hitting your system's limit? Are you swapping a lot (or none at all)? What type of system is it on?

Thanks for ur valuable suggestions.
Let me clear you the problem I anm facing.
Actually I want that the process which I am running only should run with only single PID(as for any normal case).
But problem is when I run a process, a large no. of processes run automatically with same name. Hence a lot of PIDs are creating with single PPID.

Is there any way so that only single process should run when I execute a single process.

I have checked the top amd free -mt, but find nothing.




you could try 'nicing' the process so that it (and I think the child processes) will be nicer to the other processes.

For example, I have a program that competes with production processes that still needs to run --
nice -n19 ./myprocess

Note: nicing or renicing process overrides the process priority the kernel assigns. -19 is as nice (aka as low of priority) as you can go. +20 is a "mean" process and requires root privelidges to change above 0.

Or you could try putting the process into the background --
./myprocess &

That would only help these 150 processes behave a little better. As far as the 150 children my first guess is that your application has defined 150 worker/child processes for the parent, but have little else to go on since we have no idea what "./gw" is.

Also, what do your resources look like? free -mt, top...are you hitting your system's limit? Are you swapping a lot (or none at all)? What type of system is it on?[/QUOTE]

That still may not be a bad thing. I have a number of processes all spawned from the same parent. That's normal for many programs. Trickykid's question is still important -- run a ps -ef and list them for us.