Date: Mon, 1 Mar 1999 17:15:30 -0600 (CST) From: Jack Winslade <jsw@cywub.sitel.net> To: M.S.Powell@ais.salford.ac.uk (Mark Powell) Cc: jsw@cywub.sitel.net, freebsd-questions@freebsd.org, freebsd-bugs@freebsd.org Subject: Re: 3.1-R nightly panic on news server whilst running expire. Message-ID: <199903012315.XAA25766@cywub.sitel.com> In-Reply-To: <Pine.BSF.4.05.9903012241480.8462-100000@plato.salford.ac.uk> from "Mark Powell" at Mar 1, 99 10:50:33 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> I was rather hoping, someone wouldn't say that. This Apricot server can't > reboot itself. It couldn't under NT either. It just hangs. Thus I just > can't live with any reboots. I know this ain't ideal for a service > machine, but a decent box really shouldn't be expected to reboot that much > (and it's easily accessible for a manual reboot). I can just see the > meeting now; Boss - "But it worked fine under NT. What's wrong with > FreeBSD?" :( I guess I should feel fortunate that it reboots into more or less a known state. It's hung solid a couple times, but very infrequently. > Does anyone have any pointers as to what I can try to keep this box up? I've tried weekly (and even daily) forced reboots. Seems not to matter. > It does seem pretty much linked to the expire process. If I disable expire > then the box stays up. I'm guessing expire is paging back into RAM parts > of INN that aren't generally in use, but this isn't being done properly. > The system is getting an upgrade from 96MB to 384MB of RAM soonish, so > maybe that'll help this problem. However, that still isn't ideal. I'm gonna go WAY overboard on the new machine, in regards to RAM and swap space. Hopefully this will help. Good day JSW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903012315.XAA25766>