From owner-freebsd-stable@FreeBSD.ORG  Wed Jun 29 10:29:40 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
X-Original-To: freebsd-stable@freebsd.org
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3161616A41C;
	Wed, 29 Jun 2005 10:29:40 +0000 (GMT)
	(envelope-from gabor.kovesdan@t-hosting.hu)
Received: from viefep17-int.chello.at (viefep17-int.chello.at [213.46.255.23])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 43CC743D1D;
	Wed, 29 Jun 2005 10:29:38 +0000 (GMT)
	(envelope-from gabor.kovesdan@t-hosting.hu)
Received: from [80.98.156.20] by viefep17-int.chello.at
	(InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP
	id <20050629102937.GAWF19956.viefep17-int.chello.at@[80.98.156.20]>;
	Wed, 29 Jun 2005 12:29:37 +0200
Message-ID: <42C2780A.3010504@t-hosting.hu>
Date: Wed, 29 Jun 2005 12:29:30 +0200
From: =?ISO-8859-1?Q?K=F6vesd=E1n_G=E1bor?= <gabor.kovesdan@t-hosting.hu>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-stable@freebsd.org,  freebsd-questions@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: 
Subject: sysctls issue
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, 
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jun 2005 10:29:40 -0000

Hello,

I think the net.link.ether.inet.log_arp_movements and 
net.link.ether.inet.log_arp_wrong_iface sysctls should control the arp 
messages in /var/log/messages. I don't want to see this kind of errors, 
thus I've set them to 0. Now there mustn't be any arp logs in 
/var/log/messages, must they?

Actually, there has been one since I set the two sysctls:
Jun 28 12:51:42 server kernel: arplookup 195.70.50.6 failed: host is not 
on local network


Before I set them to 0, there had been much more arplookup messages, 
just the same as I wrote above. Have I missed something? Or should I 
post this issue as a bugreport?

Cheers,

Gábor Kövesdán