2.2.8 vs. 2.1.15: different process spawning behavior?

Henrique de Moraes Holschuh hmh at debian.org
Sat Oct 16 23:31:13 EDT 2004


On Sat, 16 Oct 2004, Ken Murchison wrote:
> >Formerly this would mean that there were 100 processes max, but the 
> >actual number would fluctuate quite a bit. When any given process had 
> >been idle for too long, master would kill it. Now it seems as though 
> >processes that are spawned stick around indefinitely.

This sounds like what you get when you use the -T <timeout> options on the
services...  Or when you use -U <max uses>.

There were also bugs that caused things do die without using -U or -T due to
a sigalarm gone rogue, which was also fixed I think.

Anyway, just set -T and -U to sensible values for every service in
cyrus.conf, and you will get the variable number of processes back.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html




More information about the Info-cyrus mailing list