> Is there a setting that controls the timeout on wa.exe processes somewhere
> in Listserv?

There is not.  But keep in mind that wa.exe is nothing more than a command
pipe to LISTSERV, and that LISTSERV itself is a single-threaded process.
As such, if someone submits a wa.exe request that takes a long time (such
as searching a massive archive file), wa.exe is essentially idle while
LISTSERV processes the request.  So you may need to look at the tail of
your LISTSERV log file at the time at which wa.exe "hangs", in order to
find out what LISTSERV is up to.  If it *is* churning through a massive
archive, then it may be in your best interest to break up the archive
files into smaller pieces, change your DBRINDEX and/or FIOC settings, or
otherwise tune your LISTSERV installation.  L-Soft should be able to make
more specific recommendations to that effect.

Good luck!

--
Liam