On Fri, 23 Apr 1999 07:53:03 EDT, "K.V. Rao" <[log in to unmask]>  said:
> I am also looking for the same thing for quite sometime. The problem in
> running listserv and www on the same server has been slow response time
> when listserv is posted a message for deliv. I have seen the search req
> sit on the web and finally give up due to lack of response from lsv. I
> really like to be able to run the archive web interface on the different
> system than the listserv to avoid this problem.

The real issue here is that Listserv is "busy" doing something else
and has to wait till it finishes before it can process the next command.
You should make a *careful* note of when you see these problems, and then
go back and examine the Listserv console log for that time and see what
it was doing at the time.

One hidden "Gotcha" with Listserv performance is proper tuning of Sendmail.
Two things in particular can help a *LOT* if you are able to do them:

1) Running a local caching-only nameserver - helps speed up DNS lookups,
which Sendmail does a LOT of if you're an active site.

2) Putting a 'FEATURE(nocanonify)' in your sendmail.mc file and re-running
m4 to build a new sendmail.cf file can also help vastly.  Note that this
*does* have some trade-offs - most noticably, Listserv will then start
Losing Big Time if presented with a hostname 'foo' that isn't fully
qualified as 'foo.bar.baz.com'.  Of course, the RFCs say essentially
that this Shouldn't Happen Anyway, but... ;)

I originally added number (2) to speed up the delivery of one large
mailing list (about 4,000 recipients) - Listserv was basically sitting
and waiting for Sendmail to do a DNS lookup on every single RCPT TO:.
Adding it dropped the time for Listserv to hand it off to Sendmail
from 6-8 minutes down to 10-15 seconds.

--
                                Valdis Kletnieks
                                Computer Systems Senior Engineer
                                Virginia Tech