PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Forums Hébergement > Forum Logiciels d'hébergement > comp.mail.sendmail > Fork Each Job, Fails
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
comp.mail.sendmail Configuring and using the BSD sendmail agent.

Fork Each Job, Fails

Réponse
 
LinkBack Outils de la discussion
Vieux 19/09/2006, 05h22   #1
NM
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Fork Each Job, Fails

Hi All...

I have a problem that I'm not sure how to overcome.
Sendmail wont fork a new child for each message to multiple recipients.

If sending different messages to different domains it appears to, but
sending one message to multiple domains uses only one sendmail process
it does not spawn others and do them all in parallel like Qmail and
exim etc do, this can make for a slow process on a mailing list
server, I prefer to not replace sendmail as I'm sure this is possible, I
do have the conf option forkeachjob defined.

After a lot of google-ing, I have tried a few things like ensuring I don't
have queue children set or a few other max settings...But the little devil
just wont do it.

Any suggestions would be greatly appreciated.

  Réponse avec citation
Vieux 21/09/2006, 23h01   #2
Per Hedeland
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: Fork Each Job, Fails

In article <pan.2006.09.19.04.22.27.1555@westnet.com.au> NM
<nomail@westnet.com.au> writes:
>
>I have a problem that I'm not sure how to overcome.
>Sendmail wont fork a new child for each message to multiple recipients.


Um, that isn't the problem you describe below...

>If sending different messages to different domains it appears to, but
>sending one message to multiple domains uses only one sendmail process
>it does not spawn others and do them all in parallel like Qmail and
>exim etc do, this can make for a slow process on a mailing list
>server, I prefer to not replace sendmail as I'm sure this is possible, I
>do have the conf option forkeachjob defined.


So, there is *one* message, and consequently "a new child for each
message" still means only one child. And btw, ForkEachJob only applies
to queue runs, but maybe you are submitting the messages with
DeliveryMode=queue.

But anyway, the way to achieve what you actually want, i.e. having a
single message split into multiple jobs that can be run in parallel
(and during submission they will be run in parallel even without
ForkEachJob AFAIK), is to use the queue group functionality. E.g. with
an example shamelessly stolen from Nick Christenson's excellent book
"sendmail Performance Tuning":

[...] limit the maximum number of recipients per envelope to 10 for the
default queue:

QUEUE_GROUP(`mqueue', `P=/var/spool/mqueue, r=10')

--Per Hedeland
per@hedeland.org
  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 12h09.


Édité par : vBulletin® version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières ©2000-2008
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,10191 seconds with 10 queries