Noel Jones: > Is postscreen supposed to always run with stress=yes? > Seems to me stress-adaptive behavior would be useful in > postscreen.
The stress=yes setting indicates that a master.cf service is using up all its process slots. It is applicable only for servers that accept connections from remote clients. By design, postscreen runs as a single process. The stress=yes parameter value therefore carries no useful information. Either the postscreen service is not running at all, or it uses up all its process slots because there is only one. I could make a special case for single-process servers in master.cf so that they don't have a stress parameter. Wietse *** ./master_ent.c- Sat Jan 10 19:02:29 2009 --- ./master_ent.c Wed Jan 13 15:04:47 2010 *************** *** 526,532 **** argv_add(serv->args, "-u", (char *) 0); if (chroot) argv_add(serv->args, "-c", (char *) 0); ! if ((serv->flags & MASTER_FLAG_LOCAL_ONLY) == 0) { argv_add(serv->args, "-o", "stress=" CONFIG_BOOL_YES, (char *) 0); serv->stress_param_val = serv->args->argv[serv->args->argc - 1] + sizeof("stress=") - 1; --- 526,532 ---- argv_add(serv->args, "-u", (char *) 0); if (chroot) argv_add(serv->args, "-c", (char *) 0); ! if ((serv->flags & MASTER_FLAG_LOCAL_ONLY) == 0 && serv->max_proc > 1) { argv_add(serv->args, "-o", "stress=" CONFIG_BOOL_YES, (char *) 0); serv->stress_param_val = serv->args->argv[serv->args->argc - 1] + sizeof("stress=") - 1;