Hey guys,
I have a situation where I have several screen (/usr/bin/screen) sessions running. 2 of the screen sessions (ps1 and ps2) run a script that launched SipP with specific parameters. 1 script starts SipP and has it make 50 calls where the other makes only 20 calls. However The script is configured where we can change how many calls it makes if needed.

So the problem is, due to issues with SipP, we must restart everything every 12 hours (at maximum). So I am trying to work out scripts to stop the SipP processes cleanly. In order to do so I need to figure out which SipP process is spawned by which screen. i.e. which sipp was started by screen session ps1, and which one was started by screen session ps2.

Now I can do ps -ef | grep <number of calls configured> to find out but then I would have to change my stop script every time we reconfigure how many calls are made, and have a separate stop script for each screen session. I would much rather be able to send the screen name as a parameter to the stop script and have it work no matter how many calls SipP is configured to make.

Also your standard kill -1 <PID> does not shutdown SipP cleanly. So working out those details is a bit more tricky.

Anyone know how I can determine what processes are spawned from a specific screen session?

The screen session opens a new pseudo-tty device (e.g /dev/pts/4). (That is to say a different one than the underlying terminal session.) After opening the screen session typing "tty" in it will give you the device it is using. You can then do "ps -ft<tty>" to see any processes associated with that device.

Good idea. I guess I could pass a tty to the screen. I just have to figure out how to retrive the response from the screen in a script.