|
Sender: |
|
Subject: |
|
From: |
|
Date: |
Tue, 15 Mar 1994 16:51:31 EST |
In-Reply-To: |
Message of Tue, 15 Mar 1994 21:18:50 +0100 from <ERIC@SEARN> |
Organization: |
Michigan State University Computer Lab |
Reply-To: |
|
On Tue, 15 Mar 1994 21:18:50 +0100 Eric Thomas said:
>What's wrong with just stopping LISTSERV? I believe your plan is
>sufficient but in general it is safer to simply stop LISTSERV.
My approach is typically to HOLD the list, ask Listserv to CMS REL (DET the
disk, VMSECURE MANAGE the disk to "move" it to a larger disk, then ask
Listserv to CMS LINK and ACCESS it. I look first to make sure Listserv
hasn't recycled the file mode. I do this so that Listserv isn't down, so
that it doesn't miss interactive messages. Generally, the pool of file modes
isn't reused fast enough to cause problems for me, except in one case out of
the many times I've done this.
So, how awful is this?
How about a command to lock down one of the dynamic file modes, so that
safety is guaranteed?
Dennis
|
|
|