LSTOWN-L Archives

LISTSERV List Owners' Forum

LSTOWN-L

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Parts/Attachments: text/plain (33 lines)
Print Reply
Mime-Version:
1.0
Sender:
LISTSERV list owners' forum <[log in to unmask]>
Date:
Mon, 22 Sep 1997 17:26:18 -0400
Reply-To:
LISTSERV list owners' forum <[log in to unmask]>
Subject:
From:
"David M. Rosenberg" <[log in to unmask]>
In-Reply-To:
Content-Type:
text/plain; charset="us-ascii"
Comments:
Pete,

Thank you for replying. In order to avoid having LISTSERV shutdown,
we have acted on both of your suggestions:

1. the virtual storage was increased and we found that despite
additional increases, LISTSERV seemed to have difficulty with
archives > 36 megabytes, so
2. we then trimmed the archives back to 36 megabytes

I'm still interested in knowing whether that is a known limit in
LISTSERV-NJE 1.8c on VM and whether the same limit exits in either
LISTSERV-TCP/IP on VM or LISTSERV for NT.

At 2:50 PM -0400 9/22/97, Pete Weiss wrote:
>I think this means that either the archives have to be trimmed or the
>LISTSERV Vitual Machine VStoreage must be increased.
>
>At 13:18 9/22/97 -0400, you wrote:
>|MIT is running LISTSERV-NJE 1.8c on VM. The local LISTSERV maintainers
>|tell me that when LISTSERV is processing a CJLI database search job on
>|archives totaling more than (about) 36 megabytes, LISTSERV seems to
>|(sometimes) exhaust its working storage and shutdown.
>|
>|Is this a recognized problem?
>|
>|If so, is there a fix or workaround for it?
>|
>|Is it known whether LISTSERV-TCP/IP on VM or LISTSERV for NT suffer
>|from the same problem?
>|
>|/David M. Rosenberg        [log in to unmask]        1-617-253-8054

ATOM RSS1 RSS2