From owner-freebsd-questions  Thu Aug 28 14:17:38 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id OAA21086
          for questions-outgoing; Thu, 28 Aug 1997 14:17:38 -0700 (PDT)
Received: from mail.san.rr.com (san.rr.com [204.210.0.1])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA21069;
          Thu, 28 Aug 1997 14:17:33 -0700 (PDT)
Received: (from uucp@localhost)
	by mail.san.rr.com (8.8.7/8.8.7) id OAA07244;
	Thu, 28 Aug 1997 14:17:02 -0700 (PDT)
Message-Id: <199708282117.OAA07244@mail.san.rr.com>
Received: from dt5h1n61.san.rr.com(204.210.31.97) by mail via smap (V2.0)
	id xma007149; Thu, 28 Aug 97 14:16:56 -0700
From: "Studded" <Studded@dal.net>
To: "freebsd-bugs@freebsd.org" <freebsd-bugs@freebsd.org>,
        "Philippe SCHACK" <phschack@inba.fr>
Cc: "FreeBSD Questions" <FreeBSD-Questions@freebsd.org>
Date: Thu, 28 Aug 97 14:16:55 -0700
Reply-To: "Studded" <Studded@dal.net>
Priority: Normal
X-Mailer: PMMail 1.92 For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: in_rtqtimo message
Sender: owner-freebsd-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

	This is not a bug, it's a question, so I'm sending  you there, and
that is where you should follow up if need be. :)  

On Thu, 28 Aug 1997 08:45:49 +0200, Philippe SCHACK wrote:

>I have the following messages on my FreeBSD 2.1.7.1 console :
>
>Aug 28 07:46:28 machine /kernel: in_rtqtimo: adjusted rtq_reallyold to 2400
>Aug 28 07:56:28 machine /kernel: in_rtqtimo: adjusted rtq_reallyold to 1600
>Aug 28 08:06:28 machine /kernel: in_rtqtimo: adjusted rtq_reallyold to 1066
>Aug 28 08:16:28 machine /kernel: in_rtqtimo: adjusted rtq_reallyold to 710

	A quick search of http://www.freebsd.org/search.html in the mail
archives will give you reams on this topic (always a good place to start
btw :).  The essential facts are that this is a harmless message from your
ethernet card telling you that it's readjusting it's timing with the
network.  No interaction on your part is needed.

>I had this message and add :
>options "NMBCLUSTERS=4096"
>in the config file, but it seems to have no effect.

	That's cuz the two things are not related. :)  Try the handbook
section of the search page above, and look up nmbclusters.

Hope this helps,

Doug

Do thou amend they face,
	and I'll amend my life.
-Shakespeare, "Henry V"