At 2:04 AM +0100 1/15/05, Eric Thomas wrote
>A large PERMVARS file means more virtual storage is used, and there is a small performance degradation. It does not in itself explain a crash unless you are running against a virtual memory quota. You need to look at the traceback to see what happened.
>
>In 14.3 there is code to clean up old historical PERMVARS entries automatically. If you've been running LISTSERV for many years, this can make a big difference. But again, on your average mail server with 1G of RAM and 100G of disk space, another 1M of PERMVARS data isn't going to make a big difference.
>
>  Eric

I've crippled core files on our server, so I don't know why it is crashing.  Is the move to 14.3 fairly transparent.  The move from 1.8d to 1.8e was not, since the web interface improved so much.  Thank goodness I'm running a script to check on the server every 1/2 hour.  It's been rebooting A LOT!  Three times today!  The script sends me mail when it forces a reboot.  I annotate the subject line with what I think was the problem.  Here are the reboots this month.  Is there a standalone utility to clean up permvars?

12:40 AM 1/6/05		Listserv rebooting - L-WEBMASTER
9:40 AM 1/7/05		Listserv rebooting - permvars
1:10 AM 1/11/05		Listserv rebooting - permvars
7:40 AM 1/12/05		Listserv rebooting - permvars
3:10 AM 1/14/05		Listserv rebooting - permvars
12:40 AM 1/15/05		Listserv rebooting - reindexing
2:10 AM 1/16/05		Listserv rebooting - permvars
12:40 AM 1/17/05		Listserv rebooting - permvars
5:10 PM 1/17/05		Listserv rebooting - permvars
5:40 PM 1/17/05		Listserv rebooting - permvars
-- 
What happens when you illegally park a frog? It gets toad away.

Bill Verity - 814-865-4758  Fax: 814-863-7049
215A Computer Building - Information Technology Services, Penn State University
At the office - on my Mac, of course ;-)