From owner-freebsd-questions@FreeBSD.ORG Tue Apr 27 07:58:57 2004 Return-Path: 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 11C1F16A4CF for ; Tue, 27 Apr 2004 07:58:57 -0700 (PDT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86A3D43D2D for ; Tue, 27 Apr 2004 07:58:56 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from be-well.no-ip.com ([66.30.196.44]) by comcast.net (sccrmhc13) with ESMTP id <2004042714585101600d4apqe>; Tue, 27 Apr 2004 14:58:56 +0000 Received: by be-well.no-ip.com (Postfix, from userid 1147) id 4895C12; Tue, 27 Apr 2004 10:58:51 -0400 (EDT) Sender: lowell@be-well.ilk.org To: Bill Moran References: <408DBF4D.1000900@users.sourceforge.net> <408E6D34.3080704@potentialtech.com> From: Lowell Gilbert Date: 27 Apr 2004 10:58:51 -0400 In-Reply-To: <408E6D34.3080704@potentialtech.com> Message-ID: <443c6ptql0.fsf@be-well.ilk.org> Lines: 39 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-questions@freebsd.org cc: Rob Subject: Re: dhcpd-client floods /var/log/messages. Can I stop this? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Apr 2004 14:58:57 -0000 Bill Moran writes: > Unfortunately, I couldn't find any config options for dhclient to > reduce (or stop) the logging. It's always possible to configure syslog to put the messages elsewhere (or nowhere at all). dhclient logs to the 'user' facility at the 'notice' level, so I just limit 'user' messages to the 'warning' level in /var/log/messages, and have a separate log file for 'notice' (and above). The relevant syslog.conf(5) lines look like this: *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err;user.warning /var/log/messages user.notice /var/log/user.messages > However, I do have an improvement that can be implemented on the dhcp > server. If you see below, you default lease time is 10 minutes (600 > seconds) In the logs, your lease is being renewed every 5 minutes (per > the dhcp spec, the client should start trying to renew the lease > halfway before it expires). [Unless the server indicates a different renewal time... half the lease is only a default.] Also note that the original DHCP spec suggested leases be at least an hour. This requirement was removed when the spec was updated. > So, one way to reduce the amount of data that is logged is to increase > the default lease time. If you have more addresses than you have > machines (which is probably likely with the IP range you're using) you > can safely set the lease time to several days (maybe even weeks ... I > don't remember what the max value is). If you set the default lease > time to two days (for example) you will only get a renewal log message > once a day. The maximum value is 2 to the 32nd (minus one) seconds. This is over 100 years. In the environment described by the original poster, there's no reason to be renewing every 10 minutes; he controls the whole LAN.