From owner-freebsd-questions@FreeBSD.ORG Thu Feb 16 21:10:28 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D24D16A420 for ; Thu, 16 Feb 2006 21:10:28 +0000 (GMT) (envelope-from viper@fx-services.com) Received: from mamata.fx-services.com (mamata.fx-services.com [193.238.27.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BD0243D53 for ; Thu, 16 Feb 2006 21:10:27 +0000 (GMT) (envelope-from viper@fx-services.com) Received: from c83-250-235-77.bredband.comhem.se ([83.250.235.77] helo=[192.168.2.160]) by mamata.fx-services.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1F9qOd-00076K-FY for freebsd-questions@freebsd.org; Thu, 16 Feb 2006 22:10:40 +0100 Message-ID: <43F4EA85.7060703@fx-services.com> Date: Thu, 16 Feb 2006 22:11:33 +0100 From: Robin Vley User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <022a01c63338$1ba87d90$0401a8c0@Mike8500> In-Reply-To: <022a01c63338$1ba87d90$0401a8c0@Mike8500> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Mail is Virus Free, FXS MailGateway X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - mamata.fx-services.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [26 6] X-AntiAbuse: Sender Address Domain - fx-services.com X-Source: X-Source-Args: X-Source-Dir: Subject: Re: Mysterious reboot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Feb 2006 21:10:28 -0000 Mike Loiterman wrote: Mike, Wouter, > Before I make these changes, I would like to just get a second opinion from > the list about their value and what impact, if any, they might have on > system stability, compatibility, etc. I don't know really how to set the maxfiles parameter (mine is at 32000 for now on a web/mail server). However, as far as I understand the net.inet.tcp.delayed_ack is not something you want to set at 0 normally. This is part of the TCP system of flow control. By not delaying ACKs high speed connections will not be fully utilized. However, like someone else already answered: it's kind of hard to say if this is a good idea for YOUR setup. Maybe Wouter can explain why he came with the tip about that one? Maybe there is a good reason to it. :) My machine also has trouble with sudden reboots. Much quicker than weeks though, I barely hold out for 5 days. So I'm reading up on this sort of cases now, hence my interest in this thread. So far I've looked at the maxfiles (increased it a little), and kern.maxvnodes (increased it to 100.000, my vfs.vnodes was at 91000 at the time). My trouble is kind of exactly the same as I read in the original messaage: the result is like someone pulls the plug and puts it back in. No logs, no dumps, no nothing. And completely normal operation right before the reboot. Pretty annoying. I've had it on 2 machines, different hardware so far. First I expected hardware, but now I moved everything to a freshly installed machine with hardware that I'm 100% sure of it's OK. So it must be something else then, right? :) /Robin