From owner-freebsd-questions@FreeBSD.ORG Sun Apr 17 13:04:06 2005 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 AFBA616A4CE for ; Sun, 17 Apr 2005 13:04:06 +0000 (GMT) Received: from ipact2.infopact.nl (x71.infopact.nl [212.29.160.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0330943D1D for ; Sun, 17 Apr 2005 13:04:06 +0000 (GMT) (envelope-from joost@amiculus.com) Received: from [192.168.1.101] (32-11-ftth.onsnet.nu [84.35.11.32]) by ipact2.infopact.nl (8.12.10/8.12.10) with ESMTP id j3HD44AC019144 for ; Sun, 17 Apr 2005 15:04:05 +0200 From: Joost van Dijk Organization: Amiculus To: freebsd-questions@freebsd.org Date: Sun, 17 Apr 2005 15:03:49 +0200 User-Agent: KMail/1.7.1 References: <200504171304.48447.joost@amiculus.com> <20050417115614.GB42258@slackbox.xs4all.nl> In-Reply-To: <20050417115614.GB42258@slackbox.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200504171503.49367.joost@amiculus.com> X-Scanned-By: MIMEDefang - SpamAssassin Subject: Re: messages from dhclient 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: Sun, 17 Apr 2005 13:04:06 -0000 On Sunday 17 April 2005 13:56, Roland Smith wrote: > It looks to me like you're not running dhclient with sufficient > permissions (i.e. not as root), or you have a firewall that doesn't let the > traffic through. I am logging in as root. The firewall is enabled, but I have not got up to the chapter in the book on firewalls yet, so I have absolutely no idea what so ever about how to configure it. > The message is written on your terminal, but should not be written into > the file. Does pressing crtl+l help restore the screen? That sounds like a very useful tip. I shall try it next time it happens. > You could redirect the standard error stream for dhclient to /dev/null > when you start it up: "dhclient 2>/dev/null". Or kill dhclient while > you're editing. I think I won't do that. It is probably better that I see the message when something is going wrong. If, as you say, it is not actually written into the file, then it is less damaging than I thought. Thanks. Joost.