LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

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

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

Parts/Attachments: text/plain (25 lines)
Print Reply
Sender:
LISTSERV give-and-take forum <[log in to unmask]>
Subject:
From:
Date:
Thu, 16 Feb 1995 14:58:01 EST
In-Reply-To:
Message of Thu, 16 Feb 1995 10:57:36 -0500 from <ADAM@SIUCVMB>
Organization:
University at Albany Computing and Network Services
Reply-To:
LISTSERV give-and-take forum <[log in to unmask]>
On Thu, 16 Feb 1995 10:57:36 -0500 Adam Floro said:
>Our LISTSERV 200 disk which stores all the logs for our lists
>is filling up (86% full).  I want to blow away the old log files
>to make room for more.  Can anyone suggest a proper method?  Is
>issuing 'TELL LISTSERV CMS ERASE listname LOGnnnnn fm' a sufficient
>method?  Do I need to do anything else to inform LISTSERV of the
>change, such as rebuilding index files?  How does one do that?
 
The only problem with this method is that LISTSERV may not have the
disk accessed.  In that case, I suppose you could TELL LISTSERV CMS
ACCESS nnn x .  Then ERASE, as you describe above, and finally nuke
the database pointers which aren't any good any more:
TELL LISTSERV CMS ERASE listname DBNAMES x
TELL LISTSERV CMS ERASE listname DBINDEX x
The next time someone does an LDBASE against the list these files will
automatically be rebuilt.  Or if you want to clean things up right away,
do a
 
LDBASE yournode
SELECT * in listname
QUIT
 
(Me?  I'd log on as LISTSERV, do a SHUTDOWN, and just do the ERASEs.)
                                             /b

ATOM RSS1 RSS2