charles@c3pe.UUCP (Charles Green) (05/06/89)
We're running 'sendmail' here in order to gateway mail to a non-UNIX network
via a custom mail program. Each incoming message generates an acknowledgement
message which is handled via 'sendmail'. During periods when a few dozen
messages come in, our system gets swamped with 'sendmail' processes all
trying to process acknowledgements simultaneously, resulting in a load average
above 20 (murder on a single 68020) as well as running out of kernel resources,
and resulting in little bits of message shards lying around the system. :-)
Anyway, I'm looking at ways to tame this flood. I'm considering using '-oc'
to queue up all messages until the dialogue is finished, then run the queue
with '-q'. But what I'd really like is to have 'sendmail' be smart enough to
queue the message and, if a 'sendmail' process is already running the queue,
exit. If not, it goes to work, handling its message and any others that come
along. If possible, I'd like to avoid having to wait N minutes for a scheduled
queue run, handling things as they come in. Something roughly equivalent to
'uucico' spawning a 'uuxqt' every time a 'X.sysnameNNN' file set is complete,
if that analogy makes any sense.
I've RTMP, but the man page didn't seem to have *quite* what I'm after here.
Any suggestions would be appreciated. Please Email (our disks have been
overcrowded due to reconstruction around here lately, and we've been losing
news as a result), and I'll summarize if there's interest.
Thanks, Charles Green
--
{decuac.dec.com,cucstud,sundc}!c3pe!charles ex::!echo Boo: