From owner-freebsd-stable Sun Apr 18 17:15:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dazed.slacker.com (dazed.slacker.com [208.15.208.76]) by hub.freebsd.org (Postfix) with SMTP id 4F1D014DF2 for ; Sun, 18 Apr 1999 17:15:25 -0700 (PDT) (envelope-from nugget@dazed.slacker.com) Received: (qmail 377 invoked by uid 1000); 19 Apr 1999 00:12:59 -0000 Date: Sun, 18 Apr 1999 19:12:58 -0500 From: David McNett To: The Hermit Hacker Cc: Paul Saab , Bill Paul , freebsd-stable@FreeBSD.ORG, ghelmer@scl.ameslab.gov Subject: Re: xl0 timeouts in -STABLE Message-ID: <19990418191258.A369@dazed.slacker.com> References: <19990418171958.A16138@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from The Hermit Hacker on Sun, Apr 18, 1999 at 08:32:51PM -0300 X-Operating-System: FreeBSD 3.1-STABLE i386 X-Distributed: Join the Effort! http://www.distributed.net Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Apr-1999, The Hermit Hacker wrote: > Hi Paul... > > Got the same problem this afternoon, after upgradig my server last > night. Since I didn't have ready access to the server when it happened, I > just got them to reboot the machine, but, does an 'ifconfig xl0 > down;ifconfig xl0 up' correct the problem, or is a totaly reboot > required? The patch files Paul pointed me to this morning have just failed. No, I've not been able to ressurect the interface by issuing an ifconfig down; ifconfig up either. -- ________________________________________________________________________ |David McNett |To ensure privacy and data integrity this message has| |nugget@slacker.com|been encrypted using dual rounds of ROT-13 encryption| |Birmingham, AL USA|Please encrypt all important correspondence with PGP!| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message