|
Sender: |
Revised LISTSERV forum <LSTSRV-L@DEARN> |
Subject: |
|
From: |
"Eric Thomas (CERN/L3)" <ERIC@LEPICS> |
Date: |
Sat, 20 Aug 88 16:46:12 GMT |
Reply-To: |
Revised LISTSERV forum <LSTSRV-L@DEARN> |
Up to now, the priority assigned to the various LISTSERV command input sources
was as follows: console input buffer, message request, reader file, WAKEPARM
FILE. Several people have complained that this could cause the processing of
WAKEPARM events not to take place if LISTSERV is overwhelmed with work
(usually from reader files). This can have rather serious consequences:
1. If you have an event in WAKEPARM FILE scheduled to execute every day at
23:55 to close the console log, and LISTSERV is busy from 23:54 into the
next day with reader work, the event will be skipped (and re-scheduled for
the next day 23:55).
2. If your LISTSERV is flooded with INFO-VAX jobs, which may take over 1h to
clear up, the line monitor will cease to function. The line monitor is
indeed driven by a repetitive event in WAKEPARM FILE (&00:03 EXEC LSV$LMNT,
or something similar) which will not execute until the reader is empty.
The processing priority will therefore be changed in the next release to:
console input buffer, WAKEPARM FILE, message request, reader file.
Eric
|
|
|