I'm sure a faster server with more memory and disks would help, but if Gerry was set up to reboot itself once a week, we may find that the memory leak problems that eventually cause Gerry to stop functioning properly go away since the "leaked" memory would be reclaimed during the reboot process. I'm not sure how to do this on an NT environment, but it's probably not to difficult. If it is, perhaps just a manual reboot once every week or two by the server administrator would help. While it may seem like it is to us, the vanagon mailing list is not a "mission-critical" application that must never go down. A five minute reboot once a week to reclaim memory would probably go unnoticed by all but the most diehard list lurker. "Reboot first, ask questions later" and "when in doubt, reboot" are two rules that have worked well for me in the past on other non-mission-critical systems. Rebooting is not a permanent fix for a memory leak-related problem, but it makes a pretty good bandaid because it "nips it in the bud" before it can become a problem. Plus it doesn't cost anything other than the time to do it. My 2 cents, Steve 89 Westy |
Please note - During the past 17 years of operation, several gigabytes of
Vanagon mail messages have been archived. Searching the entire collection
will take up to five minutes to complete. Please be patient!
Return to the archives @ gerry.vanagon.com
The vanagon mailing list archives are copyright (c) 1994-2011, and may not be reproduced without the express written permission of the list administrators. Posting messages to this mailing list grants a license to the mailing list administrators to reproduce the message in a compilation, either printed or electronic. All compilations will be not-for-profit, with any excess proceeds going to the Vanagon mailing list.
Any profits from list compilations go exclusively towards the management and operation of the Vanagon mailing list and vanagon mailing list web site.