LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

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

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

Print Reply
Nathan Brindle <[log in to unmask]>
Tue, 9 Dec 1997 17:08:54 EST
text/plain (34 lines)
On Tue, 9 Dec 1997 13:11:46 CST Listserv Manager said:
>I just looked and there were over 4000 files in the /var/spool/listserv
>directory (we run 1.8c on Solaris).  Most of these files are dated
>*a long* time ago (several months).  My question is:  how much, if any,
>of this can I delete?
>
>A couple of the sample filenames are (from a ls -al)
>  1161 Oct 23  1996 10072.error
>  1247 Oct 15 17:05 3154034_0_10_x-supd_job.error
>  1174 Jul 31 13:55 2038400_8_gun
>  4375 Sep 12 13:41 2521642_8_"listname".jobh
>   755 Nov  4 12:52 3794010_0_9_x-del_job.error
>     0 Nov 19 15:15 in347356ed-000ab

Any .error file can probably be deleted unless you want to see what the
error might have been (there would have been a notification sent to the
LISTSERV maintainer that job number xxxxx was transfered to user@host).
.error files can be examined with the jobview utility.

.jobh files are held jobs, possibly jobs that were being processed when
LISTSERV crashed and could have been released (by renaming them to .job)
when you brought LISTSERV back up.  You probably don't want to release
a job as old as the one in your sample above, though.

The other two (well, one is null length so it can be deleted) can probably
just be deleted.  2038400_8_gun looks like an old .job file that might
have been renamed, in347356ed-000ab would have been an incoming queue file
being written by lsv_amin.

You'll probably want to jobview anything of relative newness just to make
sure it isn't something you might want to release or try again.

Nathan

ATOM RSS1 RSS2