Ok, here's a little more info. It seems that the procs are getting knocked off one by one at different places in the script. Sometimes it's a register, sometimes it's a reply (ack), random stuff. I have break; at each ending point, any suggestions? -----Original Message----- From: Greger V. Teigre [mailto:greger@teigre.com] Sent: Thursday, April 07, 2005 1:30 PM To: Matt Schulte; serusers(a)lists.iptel.org Subject: Re: [Serusers] Child procs Matt, Why do you believe that you have been running out of processes? At any given time you may have processes without CPU load, but over time the processes should have some CPU time. Have you run serctl ps? AFAIK, the standard number of processes for each protocol (udp/tcp) is 8 unless you specify children=x. If a ser process blocks due to problems with mysql or a radius failover situation, you may get a problem where all processes blocks. g-) Matt Schulte wrote: > only show 4 of the procs having CPU time, the rest having no cpu time > at all. Any thoughts on this? Thanks, Matt > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers > > _______________________________________________ > Serusers mailing list > serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers