From owner-freebsd-stable Sun May 26 0:12:57 2002 Delivered-To: freebsd-stable@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [194.19.15.2]) by hub.freebsd.org (Postfix) with SMTP id A1BE137B40F for ; Sun, 26 May 2002 00:12:52 -0700 (PDT) Received: (qmail 15251 invoked by uid 1001); 26 May 2002 07:12:49 +0000 (GMT) To: Gerhard.Sittig@gmx.net Cc: stable@freebsd.org Subject: Re: 4.6-PRERELASE fxp alias woes From: sthaug@nethelp.no In-Reply-To: Your message of "Sat, 25 May 2002 21:18:58 +0200" References: <20020525211858.N1494@shell.gsinet.sittig.org> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 26 May 2002 09:12:49 +0200 Message-ID: <15249.1022397169@verdi.nethelp.no> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > >ifconfig_fxp0="inet 216.109.194.4 netmask 255.255.255.0" > > >ifconfig_fxp0_alias0="inet 216.109.194.8 netmask 255.255.255.0" > > > > As everyone has pointed out, the kernel is now enforcing netmasks on > > same-subnet aliases. > > > > But I've got a really simple question: Why, if it is so easy to detect > > programatically, do we not just *fix* it automagically? Is there *ever* > > a case where it is useful to have a same-subnet alias with a different > > subnet mask (besides the obvious point of it doesn't work with the > > current code). > > Huh? I trust a computer to detect _that_ there are collisions. > But I'd *never* trust the machine to decide _which_ one of > multiple parameters is the wrong one. Very simple. Allow the same netmask as the primary address, *and* /32. Nothing else. Thus ifconfig_fxp0="inet 216.109.194.4 netmask 255.255.255.0" ifconfig_fxp0_alias0="inet 216.109.194.8 netmask 255.255.255.0" and ifconfig_fxp0="inet 216.109.194.4 netmask 255.255.255.0" ifconfig_fxp0_alias0="inet 216.109.194.8 netmask 255.255.255.255" would both be allowed. For other subnets (not on the same subnet as the primary address): Let the first alias decide the netmask, complain if further aliases within the same subnet (as specified by the alias of the first netmask) use a different netmask (but allow /32). There is plenty of prior art here - Cisco routers being the example I know best. One particular real-life example: interface FastEthernet0/1/0 ip address 195.18.218.25 255.255.255.248 secondary ip address 195.18.233.193 255.255.255.224 secondary ip address 194.19.112.97 255.255.255.224 secondary ip address 194.19.112.65 255.255.255.224 secondary ip address 194.19.112.225 255.255.255.240 secondary ip address 194.19.112.193 255.255.255.224 secondary ip address 194.19.112.194 255.255.255.224 secondary ip address 194.19.112.33 255.255.255.224 secondary ip address 194.19.112.129 255.255.255.224 secondary ip address 194.19.112.2 255.255.255.224 secondary ip address 194.19.112.1 255.255.255.224 > This would be some kind > of "no matter what I tell you, do what I mean" or even worse > "don't take me too serious, do what you think I meant". This > is definitely not the UNIX way. If you wish for this kind of > features, don't hesitate to install a different OS on your > machine. :> As long as it is possible to do this without requiring any kind of DWIM, I see no problem. And it *is* possible, As Cisco has shown. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 1:54:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id B0BE237B405 for ; Sun, 26 May 2002 01:54:31 -0700 (PDT) Received: (qmail 7963 invoked from network); 26 May 2002 08:54:30 -0000 Received: from unknown (HELO killa) ([66.92.221.23]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 26 May 2002 08:54:30 -0000 From: "mc" To: Subject: upgrading Date: Sun, 26 May 2002 05:02:41 -0400 Message-ID: <000001c20494$187077d0$17dd5c42@killa> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C20472.915ED7D0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C20472.915ED7D0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I'm trying to upgrade from 4.4-stable to the latest stable. In single user mode, I initialized make in /usr/src but its messed up when making getpeereid.o saying In function 'getpeereid": /usr/src/lib/libc/../libc/gen/getpeereid.c:41: storage size of 'xuc' isn't known /usr/src/lib/libc/../libc/gen/getpeereid.c:46: 'LOCAL_PEERCRED' undeclared (first use in this function) /usr/src/lib/libc/../libc/gen/getpeereid.c:46: (Each undeclared identifier is reported only once /usr/src/lib/libc/../libc/gen/getpeereid.c:46: for each function it appears in.) /usr/src/lib/libc/../libc/gen/getpeereid.c:49: 'XUCRED_VERSION' undeclared (first use of this function) *** Error code 1 then everything stops.. looks to that xuc is the source of this problem but I don't know how to fix it nor can I really diagnose it. ------=_NextPart_000_0001_01C20472.915ED7D0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I’m trying to upgrade from 4.4-stable to the = latest stable. In single user mode, I initialized make in /usr/src but its messed up when making getpeereid.o saying In function ‘getpeereid”:

 

/usr/src/lib/libc/..<= /font>/libc/gen/getpeereid.c:41:  storage size of  ‘xuc’ isn’t known

/usr/src/lib/libc/..<= /font>/libc/gen/getpeereid.c:46: ‘LOCAL_PEERCRED’ undeclared (first use in this = function)

/usr/src/lib/libc/..<= /font>/libc/gen/getpeereid.c:46: (Each undeclared identifier is reported only = once

/usr/src/lib/libc/..<= /font>/libc/gen/getpeereid.c:46: for each function it appears in.)

/usr/src/lib/libc/..<= /font>/libc/gen/getpeereid.c:49: ‘XUCRED_VERSION’ undeclared (first use of this = function)

*** Error code 1

 

 

then everything stops..

 

looks to that xuc is the source of this problem but I = don’t know how to fix it nor can I really diagnose it.

 

 

------=_NextPart_000_0001_01C20472.915ED7D0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 2:44:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 4737737B401 for ; Sun, 26 May 2002 02:44:09 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=rip.psg.com.psg.com) by rip.psg.com with esmtp (Exim 4.04) id 17BuZM-000DJS-00 for freebsd-stable@freebsd.org; Sun, 26 May 2002 02:44:09 -0700 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Stable Subject: ADI 1885 audio support Message-Id: Date: Sun, 26 May 2002 02:44:09 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG the intel D850EMV2 mobo has an on-board audio using the ADI 1885. does freebsd -stable support it? i can not find it in HARDWARE.TXT. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 3:27:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [212.61.40.17]) by hub.freebsd.org (Postfix) with ESMTP id 68A9F37B415 for ; Sun, 26 May 2002 03:26:59 -0700 (PDT) Received: by gvr.gvr.org (Postfix, from userid 657) id D89ED57CA; Sun, 26 May 2002 12:26:56 +0200 (CEST) Date: Sun, 26 May 2002 12:26:56 +0200 From: Guido van Rooij To: freebsd-stable@freebsd.org Subject: freebsd RC2 and fxp: SCB error Message-ID: <20020526102656.GA40771@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a vaio Z505SX running 4.6-RC2. It has a built in fxp. It functions fine, however, when I disconnect the utp cable from the fxp0 interface while it is still up, within one to about 30 minutes, the system will freeze completely. Just before that, the kernel tried to print the SCB timeout error message. It gets corrupted though. Some characters are replaced by spaces, and some with characters\with the high bit set. I haven't had time to look into this further due to that system being used for a tutorial I have to gie shortly. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 3:29:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from gvr.gvr.org (gvr.gvr.org [212.61.40.17]) by hub.freebsd.org (Postfix) with ESMTP id 0BE9037B405 for ; Sun, 26 May 2002 03:29:42 -0700 (PDT) Received: by gvr.gvr.org (Postfix, from userid 657) id D243E57CA; Sun, 26 May 2002 12:29:40 +0200 (CEST) Date: Sun, 26 May 2002 12:29:40 +0200 From: Guido van Rooij To: freebsd-stable@freebsd.org Subject: Re: freebsd RC2 and fxp: SCB error Message-ID: <20020526102940.GA40761@gvr.gvr.org> References: <20020526102656.GA40771@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020526102656.GA40771@gvr.gvr.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, May 26, 2002 at 12:26:56PM +0200, Guido van Rooij wrote: > I have a vaio Z505SX running 4.6-RC2. It has a built in fxp. > It functions fine, however, when I disconnect the utp cable from > the fxp0 interface while it is still up, within one to about 30 > minutes, the system will freeze completely. > Just before that, the kernel tried to print the SCB timeout error > message. It gets corrupted though. Some characters are replaced > by spaces, and some with characters\with the high bit set. > > I haven't had time to look into this further due to that system being used > for a tutorial I have to gie shortly. Just to be clear: this vaio is a PII system, and has no smp kernel. -Guido To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 4:31:20 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tarakan-network.com (chojin.adsl.nerim.net [62.4.22.98]) by hub.freebsd.org (Postfix) with ESMTP id 64FBB37B400 for ; Sun, 26 May 2002 04:31:16 -0700 (PDT) Received: from chojinlaptop (unknown [192.168.1.6]) by tarakan-network.com (Postfix) with SMTP id 8954C20E3C for ; Sun, 26 May 2002 13:31:19 +0200 (CEST) Message-ID: <00c001c204a8$bf40b160$0601a8c0@chojinlaptop> From: "Chojin" To: Subject: About gigabit ethernet card support Date: Sun, 26 May 2002 13:30:32 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I would like to know if Edimax EN-9210TX-64 (1 gigabit 64 bit ethernet card) is supported by FreeBSD ? I did not find it on ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/4.5-RELEASE/HARDWARE.TXT Regards. -- Chojin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 5:29:57 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mta5.rcsntx.swbell.net (mta5.rcsntx.swbell.net [151.164.30.29]) by hub.freebsd.org (Postfix) with ESMTP id DD76B37B400 for ; Sun, 26 May 2002 05:29:51 -0700 (PDT) Received: from aragonsworld.net ([208.190.106.2]) by mta5.rcsntx.swbell.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with SMTP id <0GWP00JNJXDR29@mta5.rcsntx.swbell.net> for freebsd-stable@FreeBSD.org; Sun, 26 May 2002 07:29:51 -0500 (CDT) Received: (qmail 82703 invoked from network); Sun, 26 May 2002 12:28:33 +0000 Received: from unknown (HELO veeger) (192.168.0.2) by 0 with SMTP; Sun, 26 May 2002 12:28:33 +0000 Date: Sun, 26 May 2002 07:29:56 -0500 From: Aragon Subject: subscribe To: freebsd-stable@FreeBSD.org Message-id: <000a01c204b1$0baced40$0200a8c0@aragonsworld.net> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: multipart/alternative; boundary="Boundary_(ID_AULpj+ayn1cSzRuGX8YhMA)" X-Priority: 3 X-MSMail-priority: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --Boundary_(ID_AULpj+ayn1cSzRuGX8YhMA) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT --Boundary_(ID_AULpj+ayn1cSzRuGX8YhMA) Content-type: text/html; charset=iso-8859-1 Content-transfer-encoding: 7BIT
 
--Boundary_(ID_AULpj+ayn1cSzRuGX8YhMA)-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 5:38:15 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.root.nis.za (root.nis.za [196.36.198.81]) by hub.freebsd.org (Postfix) with ESMTP id 9CE2D37B400 for ; Sun, 26 May 2002 05:38:10 -0700 (PDT) Received: by mail.root.nis.za (Postfix, from userid 1000) id 74F2824EE2; Sun, 26 May 2002 14:38:07 +0200 (SAST) Received: from localhost (localhost [127.0.0.1]) by mail.root.nis.za (Postfix) with ESMTP id 724D224D22 for ; Sun, 26 May 2002 14:38:07 +0200 (SAST) Date: Sun, 26 May 2002 14:38:07 +0200 (SAST) From: Aragon Gouveia X-X-Sender: aragon@root.nis.za To: freebsd-stable@freebsd.org Subject: 4.6-RC sshd exiting on signal 11 (Core dump) Message-ID: <20020526143255.G1389-100000@root.nis.za> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I cvsupped and rebuilt world 3 days ago to 4.6-RC. Since then I've been having very strange problems with sshd core dumping. It still listens on port 22 and supplies its version string on connecting, but trying to login causes it to core dump. In some cases it doesnt supply a complete version string. One instance I had it just output "SSH-2.0-" and nothing more. I'm running 2 jails on the same machine and those sshd's are also doing the same. Giving the master process a SIGHUP fixes it temporarily. Can anyone help me debug this? Thanks, Aragon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 5:47: 2 2002 Delivered-To: freebsd-stable@freebsd.org Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by hub.freebsd.org (Postfix) with ESMTP id 2860937B403 for ; Sun, 26 May 2002 05:46:46 -0700 (PDT) Received: from alogis.com (ppp-cuaa7.int1.b.intern [10.1.1.36]) by alogis.com (8.11.1/8.9.3) with ESMTP id g4QCkil43272; Sun, 26 May 2002 14:46:44 +0200 (CEST) (envelope-from holger.kipp@alogis.com) Message-ID: <3CF0D593.1D485451@alogis.com> Date: Sun, 26 May 2002 14:31:16 +0200 From: Holger Kipp X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: NFS exporting with map_static? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I'm looking for an option to be used within exports similar to map_static=/path/to/mapfile.map (as seen on linux) which allows to define several mappings, both uid and gid, by defining a file with all those mappings. Currently I don't see how this can be done easily with freebsd. Regards, Holger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 5:58:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 4027537B405 for ; Sun, 26 May 2002 05:58:32 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id FAA28954; Sun, 26 May 2002 05:54:44 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda28952; Sun May 26 05:54:44 2002 Received: from cwsys.cwsent.com (cwsys2 [10.1.2.1]) by passer.osg.gov.bc.ca (8.12.3/8.12.3) with ESMTP id g4QCsceQ047183; Sun, 26 May 2002 05:54:38 -0700 (PDT) (envelope-from cy@cwsent.com) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.12.3/8.12.3) with ESMTP id g4QCsXoM047150; Sun, 26 May 2002 05:54:33 -0700 (PDT) (envelope-from cy@cwsys.cwsent.com) Message-Id: <200205261254.g4QCsXoM047150@cwsys.cwsent.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - CITS Open Systems Group From: Cy Schubert - CITS Open Systems Group X-os: FreeBSD X-Sender: cy@cwsent.com To: Holger Kipp Cc: stable@FreeBSD.ORG Subject: Re: NFS exporting with map_static? In-Reply-To: Message from Holger Kipp of "Sun, 26 May 2002 14:31:16 +0200." <3CF0D593.1D485451@alogis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 26 May 2002 05:54:33 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3CF0D593.1D485451@alogis.com>, Holger Kipp writes: > Hi, > > I'm looking for an option to be used within exports similar to > > map_static=/path/to/mapfile.map (as seen on linux) > > which allows to define several mappings, both uid and gid, by > defining a file with all those mappings. > Currently I don't see how this can be done easily with > freebsd. man mount_umap -- Cheers, Phone: 250-387-8437 Cy Schubert Fax: 250-387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, CITS Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 6:27:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by hub.freebsd.org (Postfix) with ESMTP id E3E8437B406 for ; Sun, 26 May 2002 06:27:13 -0700 (PDT) Received: from alogis.com (ppp-cuaa7.int1.b.intern [10.1.1.36]) by alogis.com (8.11.1/8.9.3) with ESMTP id g4QDQYl44485; Sun, 26 May 2002 15:26:34 +0200 (CEST) (envelope-from holger.kipp@alogis.com) Message-ID: <3CF0DEEA.7117DF08@alogis.com> Date: Sun, 26 May 2002 15:11:06 +0200 From: Holger Kipp X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Cy Schubert - CITS Open Systems Group Cc: stable@FreeBSD.ORG Subject: Re: NFS exporting with map_static? References: <200205261254.g4QCsXoM047150@cwsys.cwsent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cy Schubert - CITS Open Systems Group wrote: > > I'm looking for an option to be used within exports similar to > > > > map_static=/path/to/mapfile.map (as seen on linux) > > > > which allows to define several mappings, both uid and gid, by > > defining a file with all those mappings. > > Currently I don't see how this can be done easily with > > freebsd. > > man mount_umap I wouldn't call fs-layering the right way to do this. Furthermore, man mount_umap states: - at most 64 uids, 16 gids. - simple example of fs layering - not meant for production use. So mount_umap won't help me here. Regards, Holger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 9:14:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from nitrogen.wanadoo.fr (ca-ol-sqy-20-193.abo.wanadoo.fr [80.8.57.193]) by hub.freebsd.org (Postfix) with ESMTP id 0FFEF37B401 for ; Sun, 26 May 2002 09:14:23 -0700 (PDT) Received: from nitrogen.wanadoo.fr (nitrogen [127.0.0.1]) by nitrogen.wanadoo.fr (8.12.3/8.12.3) with ESMTP id g4QGCskY000622 for ; Sun, 26 May 2002 18:12:55 +0200 (CEST) (envelope-from dak@nitrogen.wanadoo.fr) Received: (from dak@localhost) by nitrogen.wanadoo.fr (8.12.3/8.12.3/Submit) id g4QGCsB3000621 for stable@freebsd.org; Sun, 26 May 2002 18:12:54 +0200 (CEST) Date: Sun, 26 May 2002 18:12:54 +0200 From: dak To: stable@freebsd.org Subject: Mouse problems Message-ID: <20020526161254.GA516@nitrogen> Mime-Version: 1.0 Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, Since I have my laptop (~ 1 year) I have a mouse problem. Sometimes, the mouse become crazy: when I click, it doesn't click where the mouse pointer is but ~1cm on the left. It's very anoying to click ... Of course, when I move my mouse to the left border, the pointer stops at ~1cm of it :) I'm using a PS/2 mouse (but even if I unplug it, if I move my mouse with the touchpad it does the same thing). Moreover, even if I reboot, it fixes the problem randomly (sometimes it does, sometimes if doesn't). Thanks in advance. - Aurélien To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 10:32:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (pc-62-31-42-140-hy.blueyonder.co.uk [62.31.42.140]) by hub.freebsd.org (Postfix) with ESMTP id 51BDA37B404 for ; Sun, 26 May 2002 10:32:42 -0700 (PDT) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.11.3/8.11.3) id g4Q63Ox27442; Sun, 26 May 2002 07:03:24 +0100 (BST) (envelope-from nik) Date: Sun, 26 May 2002 07:03:23 +0100 From: Nik Clayton To: Mike Gratton Cc: Kirill Alder-Ponazdyr , freebsd-stable@FreeBSD.ORG Subject: Re: FreeBSD and LDAP Directory Message-ID: <20020526070323.B11002@canyon.nothing-going-on.org> References: <20020521222314.3C47D37B40C@hub.freebsd.org> <20020521153245.K10179@techometer.net> <20020521223735.AA60537B409@hub.freebsd.org> <3CEAD1BE.6020306@vee.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="GID0FwUMdk1T2AWN" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3CEAD1BE.6020306@vee.net>; from mike@vee.net on Wed, May 22, 2002 at 08:31:18AM +0930 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --GID0FwUMdk1T2AWN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 22, 2002 at 08:31:18AM +0930, Mike Gratton wrote: > The long answer is: You need something like nsswitch to be able to use=20 > LDAP directly. There was a port of NetBSD's nsswitch implementation to=20 > -STABLE and -CURRENT a while ago by Jacques Vidrine. Unfortunately it=20 > didn't work with LDAP for a few reasons, and he doesn't have the time to= =20 > rework it so it does. See =20 > for details. An alternative would be to use YP on your FBSD machines=20 > with a LDAP to YP bridge for the master. PADL =20 > have a commerical LDAP/YP bridge which you could use. There's also the OS X Open Directory system, which is also in Darwin (the opensource component of OS X). See http://developer.apple.com/techpubs/macosx/Darwin/PortingUNIX/additiona= lfeatures/NetInfo.html for a brief introduction, and the Open Directory pages at http://developer.apple.com/darwin/projects/opendirectory/ for links to API documentation, and source code. Basically, Open Directory is an API to abstract lookups to a number of different directory services, including NetInfo, and LDAP. N --=20 FreeBSD: The Power to Serve http://www.freebsd.org/ (__) FreeBSD Documentation Project http://www.freebsd.org/docproj/ \\\'',) \/ \= ^ --- 15B8 3FFC DDB4 34B0 AA5F 94B7 93A8 0764 2C37 E375 --- .\._/= _) --GID0FwUMdk1T2AWN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE88Hqqk6gHZCw343URAppvAJ4gRKXI43TNu98snhv8k8dV75MAUACcCjzl E+Dmdc5BaMs/RdacDlJ6JGA= =/VKM -----END PGP SIGNATURE----- --GID0FwUMdk1T2AWN-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 11:15:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id D046E37B407 for ; Sun, 26 May 2002 11:15:42 -0700 (PDT) Received: (qmail 21601 invoked by uid 0); 26 May 2002 18:15:41 -0000 Received: from p509103ab.dip0.t-ipconnect.de (HELO mail.gsinet.sittig.org) (80.145.3.171) by mail.gmx.net (mp001-rz3) with SMTP; 26 May 2002 18:15:41 -0000 Received: (qmail 70288 invoked from network); 26 May 2002 08:54:04 -0000 Received: from shell.gsinet.sittig.org (192.168.11.153) by mail.gsinet.sittig.org with SMTP; 26 May 2002 08:54:04 -0000 Received: (from sittig@localhost) by shell.gsinet.sittig.org (8.11.3/8.11.3) id g4Q8s4L70284 for stable@freebsd.org; Sun, 26 May 2002 10:54:04 +0200 (CEST) (envelope-from sittig) Date: Sun, 26 May 2002 10:54:04 +0200 From: Gerhard Sittig To: stable@freebsd.org Subject: Re: 4.6-PRERELASE fxp alias woes Message-ID: <20020526105404.Q1494@shell.gsinet.sittig.org> Mail-Followup-To: stable@freebsd.org References: <20020525211858.N1494@shell.gsinet.sittig.org> <15249.1022397169@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15249.1022397169@verdi.nethelp.no>; from sthaug@nethelp.no on Sun, May 26, 2002 at 09:12:49AM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ why did you break the attribution? please leave this info intact! ] On Sun, May 26, 2002 at 09:12 +0200, sthaug@nethelp.no wrote: > > > > >ifconfig_fxp0="inet 216.109.194.4 netmask 255.255.255.0" > > > >ifconfig_fxp0_alias0="inet 216.109.194.8 netmask 255.255.255.0" > > > > > > As everyone has pointed out, the kernel is now enforcing netmasks on > > > same-subnet aliases. > > > > > > But I've got a really simple question: Why, if it is so easy to detect > > > programatically, do we not just *fix* it automagically? Is there *ever* > > > a case where it is useful to have a same-subnet alias with a different > > > subnet mask (besides the obvious point of it doesn't work with the > > > current code). > > > > Huh? I trust a computer to detect _that_ there are collisions. > > But I'd *never* trust the machine to decide _which_ one of > > multiple parameters is the wrong one. > > Very simple. Allow the same netmask as the primary address, *and* /32. > Nothing else. Thus > > ifconfig_fxp0="inet 216.109.194.4 netmask 255.255.255.0" > ifconfig_fxp0_alias0="inet 216.109.194.8 netmask 255.255.255.0" > and > ifconfig_fxp0="inet 216.109.194.4 netmask 255.255.255.0" > ifconfig_fxp0_alias0="inet 216.109.194.8 netmask 255.255.255.255" > > would both be allowed. Well, right after sending my first reply I felt that I should have put an example in it. :) Imagine the following setup: ifconfig_fxp0=" inet 192.168.20.120 netmask 255.255.255.0" ifconfig_fxp0_alias0="inet 192.168.30.130 netmask 255.255.255.255" Of course a program can detect that these values "don't fit". But how do you determine if the alias entry's address is wrong or the netmask? Only an admin can, looking at the local topology. Not even human spectators can decide which of the parameters needs correction. And since your above restriction doesn't solve any problem while it prevents perfectly legal scenarios from working (like ifconfig_fxp0=" inet 192.168.20.120 netmask 255.255.255.0" ifconfig_fxp0_alias0="inet 192.168.20.122 netmask 255.255.255.255" ifconfig_fxp0_alias1="inet 172.16.120.130 netmask 255.255.0.0" ) it is to be rejected. :> virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 13:10: 3 2002 Delivered-To: freebsd-stable@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [194.19.15.2]) by hub.freebsd.org (Postfix) with SMTP id E7A4337B406 for ; Sun, 26 May 2002 13:09:55 -0700 (PDT) Received: (qmail 19771 invoked by uid 1001); 26 May 2002 20:09:49 +0000 (GMT) To: Gerhard.Sittig@gmx.net Cc: stable@freebsd.org Subject: Re: 4.6-PRERELASE fxp alias woes From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 26 May 2002 10:54:04 +0200" References: <20020526105404.Q1494@shell.gsinet.sittig.org> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sun, 26 May 2002 22:09:49 +0200 Message-ID: <19769.1022443789@verdi.nethelp.no> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > Huh? I trust a computer to detect _that_ there are collisions. > > > But I'd *never* trust the machine to decide _which_ one of > > > multiple parameters is the wrong one. > > > > Very simple. Allow the same netmask as the primary address, *and* /32. > > Nothing else. Thus > > > > ifconfig_fxp0="inet 216.109.194.4 netmask 255.255.255.0" > > ifconfig_fxp0_alias0="inet 216.109.194.8 netmask 255.255.255.0" > > and > > ifconfig_fxp0="inet 216.109.194.4 netmask 255.255.255.0" > > ifconfig_fxp0_alias0="inet 216.109.194.8 netmask 255.255.255.255" > > > > would both be allowed. > > Well, right after sending my first reply I felt that I should > have put an example in it. :) Imagine the following setup: > > ifconfig_fxp0=" inet 192.168.20.120 netmask 255.255.255.0" > ifconfig_fxp0_alias0="inet 192.168.30.130 netmask 255.255.255.255" > > Of course a program can detect that these values "don't fit". But > how do you determine if the alias entry's address is wrong or the > netmask? Only an admin can, looking at the local topology. Not > even human spectators can decide which of the parameters needs > correction. *Why* should the program try to guess anything at all? Only if the configuration lines are in conflict should the program try to do something - otherwise it should assume that the values are correct. In this case, 192.168.20.120/24 as the primary address and 192.168.30.130/32 as an alias are perfectly fine. No conflict, no reason for ifconfig (or the kernel) to try to guess anything. > And since your above restriction doesn't solve any problem while > it prevents perfectly legal scenarios from working (like > > ifconfig_fxp0=" inet 192.168.20.120 netmask 255.255.255.0" > ifconfig_fxp0_alias0="inet 192.168.20.122 netmask 255.255.255.255" > ifconfig_fxp0_alias1="inet 172.16.120.130 netmask 255.255.0.0" > > ) it is to be rejected. :> How do the rules I proposed prevent this example? I wrote: > Very simple. Allow the same netmask as the primary address, *and* /32. > Nothing else. ... > For other subnets (not on the same subnet as the primary address): Let > the first alias decide the netmask, complain if further aliases within > the same subnet (as specified by the alias of the first netmask) use a > different netmask (but allow /32). 172.16.120.130/16 is not on the same subnet as 192.168.20.120/24, so there is no conflict. I'm perfectly willing to believe that these rules need to be refined. My main point is that this *can be done* in a consistent way - and that Cisco is one example which shows that it can indeed be done. And Cisco had had this at least since around 1990 (my first contact with Cisco IOS version 8.3). A further point is that having addresses on the same subnet all use the same netmask is more natural than using /32 for the aliases, if you've never used an alias before. Having to use /32 breaks POLA. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 18:13:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mile.nevermind.kiev.ua (freebsddiary.org.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id 6C52B37B405 for ; Sun, 26 May 2002 18:13:22 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.3/8.12.3) with ESMTP id g4R1DEjj036285; Mon, 27 May 2002 04:13:14 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.3/8.12.3/Submit) id g4R1DEqD036284; Mon, 27 May 2002 04:13:14 +0300 (EEST) Date: Mon, 27 May 2002 04:13:14 +0300 From: Alexandr Kovalenko To: dak Cc: stable@FreeBSD.ORG Subject: Re: Mouse problems Message-ID: <20020527011314.GA36214@nevermind.kiev.ua> References: <20020526161254.GA516@nitrogen> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20020526161254.GA516@nitrogen> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, dak! On Sun, May 26, 2002 at 06:12:54PM +0200, you wrote: > Since I have my laptop (~ 1 year) I have a mouse problem. Sometimes, the mouse become crazy: when I click, it doesn't click > where the mouse pointer is but ~1cm on the left. It's very anoying to click ... Of course, when I move my mouse to the left border, > the pointer stops at ~1cm of it :) > > I'm using a PS/2 mouse (but even if I unplug it, if I move my mouse with the touchpad it does the same thing). > Moreover, even if I reboot, it fixes the problem randomly (sometimes it does, sometimes if doesn't). > > Thanks in advance. uname -a, pls :) if -CURRENT, then check knu@'s postings in freebasd-current@ week ago. -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 19:39:59 2002 Delivered-To: freebsd-stable@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by hub.freebsd.org (Postfix) with ESMTP id 61B3337B401 for ; Sun, 26 May 2002 19:39:56 -0700 (PDT) Received: from pc-02 (pc02.ekahuna.com [198.144.200.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Sun, 26 May 2002 19:39:55 -0700 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: stable@FreeBSD.ORG Date: Sun, 26 May 2002 19:39:54 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: FreeBSD and LDAP Directory Reply-To: pjklist@ekahuna.com In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12c) Message-ID: <20020527023955871.AAA478@empty1.ekahuna.com@pc02.ekahuna.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Date: Sun, 26 May 2002 07:03:23 +0100 > From: Nik Clayton > There's also the OS X Open Directory system, which is also in Darwin (the > opensource component of OS X). See > > http://developer.apple.com/techpubs/macosx/Darwin/PortingUNIX/additiona= > lfeatures/NetInfo.html > > for a brief introduction, and the Open Directory pages at > > http://developer.apple.com/darwin/projects/opendirectory/ > > for links to API documentation, and source code. > > Basically, Open Directory is an API to abstract lookups to a number of > different directory services, including NetInfo, and LDAP. Yanno, it's kinda funny how everyone has all these proprietary "open" directory API's. Kinda like Microsoft and their "proprietary" kerberos, or how Sun says Java is "open to everyone", as long as they get to control it. -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 20:43:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from lexus.isprime.com (lexus.isprime.com [66.230.130.130]) by hub.freebsd.org (Postfix) with ESMTP id 2BB2637B403 for ; Sun, 26 May 2002 20:43:54 -0700 (PDT) Received: from zoom (winter@localhost [127.0.0.1]) by lexus.isprime.com (8.11.6/8.11.6) with SMTP id g4R3hmj43605 for ; Sun, 26 May 2002 23:43:48 -0400 (EDT) (envelope-from winter@villaweb.net) Message-ID: <004701c20530$68e98a20$0700a8c0@zoom> From: "Phil Rosenthal" To: Subject: Hardware RAID vs vinum Date: Sun, 26 May 2002 23:41:39 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Disposition-Notification-To: "Phil Rosenthal" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been using vinum for about a year now, and have been using it on some pretty large, heavily accessed RAID5 file system (500GB & 70MBits/sec constantly ). Is there any reason why a hardware raid would be better, am I missing out on anything? What hardware RAID cards are best under FreeBSD 4.6? --Phil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 20:53: 8 2002 Delivered-To: freebsd-stable@freebsd.org Received: from kanga.honeypot.net (kanga.honeypot.net [208.162.254.122]) by hub.freebsd.org (Postfix) with ESMTP id 60FF237B405 for ; Sun, 26 May 2002 20:52:44 -0700 (PDT) Received: from pooh.int (mail@pooh.int [10.0.1.2]) by kanga.honeypot.net (8.12.3/8.12.3) with ESMTP id g4R3qamS038699 for ; Sun, 26 May 2002 22:52:36 -0500 (CDT) (envelope-from kirk@strauser.com) Received: from kirk by pooh.int with local (Exim 3.35 #1 (Debian)) id 17CBYg-0002bs-00 for ; Sun, 26 May 2002 22:52:34 -0500 To: freebsd-stable@freebsd.org Subject: Re: Hardware RAID vs vinum References: <004701c20530$68e98a20$0700a8c0@zoom> From: Kirk Strauser Date: 26 May 2002 22:52:33 -0500 In-Reply-To: <004701c20530$68e98a20$0700a8c0@zoom> Message-ID: <87r8jy9ri6.fsf@pooh.int> Lines: 18 X-Mailer: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 2002-05-27T03:41:39Z, "Phil Rosenthal" writes: > Is there any reason why a hardware raid would be better, am I missing out > on anything? In theory, a hardware RAID should give you better CPU utilization. After all, a seperate processor (or DSP, etc.) would be doing all of the work that your main CPU is currently doing. Furthermore, your CPU would be able to forget about all of the extra abstractions of Vinum, such as plexes, subdisks, and so on - the RAID could look like one single harddrive. In reality, I don't think that the RAID controllers would protect the CPU from nearly so much work, and I'm almost positive that your CPU will be orders of magnitude faster than the processor on the controllers. -- Kirk Strauser The Strauser Group - http://www.strausergroup.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 21:43:20 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.cscoms.com (mail.cscoms.com [202.183.255.23]) by hub.freebsd.org (Postfix) with ESMTP id 7AFA637B401 for ; Sun, 26 May 2002 21:43:14 -0700 (PDT) Received: from mail.cscoms.com (dial-220.ras-16.bkk.c.cscoms.com [203.170.151.158]) by mail.cscoms.com (8.11.1/8.11.1) with SMTP id g4R4h5J28226 for ; Mon, 27 May 2002 11:43:06 +0700 (GMT) Message-Id: <1022474852.400@cscoms.com> Date: Mon, 27 May 2002 11:47:32 0700 To: stable@FreeBSD.org From: "richy" Subject: §Ò¹ Part Time ÊÃéÒ§ÃÒÂä´é´Õ ãªéà·¤â¹âÅÂշӧҹ᷹¤Ø³ MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG §Ò¹ Part Time ãªéà·¤â¹âÅÂշӧҹ᷹¤Ø³ äÁè¡ÃзºµèͪÕÇÔµ»ÃШÓÇѹ¢Í§¤Ø³ äÁèÇèҤس¨Ðà»ç¹ã¤Ã ¤Ø³µéͧ¡ÒçҹÍÂèÒ§¹ÕéËÃ×Íà»ÅèÒ ?? - âÍ¡ÒÊ·Õè¨Ðà»ç¹à¨éҢͧ¡Ô¨¡ÒÃẺ§èÒ æ - ÁÕ¸ØáԨ¢Í§µ¹àͧº¹ Internet ( E-Commerce ) - à»Ô´´Óà¹Ô¹§Ò¹µÅÍ´ 24 ªÑèÇâÁ§µèÍÇѹ 7ÇѹµèÍÊÑ»´ÒËì 365Çѹã¹Ë¹Ö觻ÕäÁèÁÕÇѹËÂØ´ - à§Ô¹Å§·Ø¹µèÓ ÃÒÂä´éÊÙ§ Part Time 15,000 ºÒ·¢Öé¹ä»µèÍà´×͹ / Full Time 45,000 ºÒ·¢Öé¹ä» - äÁèµéͧ¨éÒ§¾¹Ñ¡§Ò¹¢Ò äÁèµéͧ»Ç´ËÑÇàÃ×èͧ¢Ö鹤èÒáç ¡ÒùѴËÂØ´§Ò¹ áÅÐäÁèµéͧ¨èÒÂÊÇÑÊ´Ô¡Òà - ãªéà·¤â¹âÅÂշӧҹ᷹¤Ø³ äÁè¡ÃзºµèÍ¡ÒôÓà¹Ô¹ªÕÇÔµ»ÃШÓÇѹ¢Í§¤Ø³ à¾Õ§á¤èÇѹÅÐ 2-3 ªÑèÇâÁ§ - ·Ó§Ò¹¨Ò¡·Õèä˹¡çä´é áµèÊÒÁÒöÁÕ¸ØáԨä´é·ÑèÇâÅ¡ - äÁèµéͧ¡Ñ¡µØ¹ÊÔ¹¤éÒ äÁèàÊÕ觵èͷع¨Á - ÁÕÃкº¨Ñ´Êè§ÊÔ¹¤éÒ ·Ñé§ã¹áÅеèÒ§»ÃÐà·È - äÁèãªè¡Òà Knock Door ¢ÒÂÊÔ¹¤éÒ áµèÅÙ¡¤éÒ¨ÐÇÔè§à¢éÒÁÒËҤس ÏÅÏ ¶éҤسÍÂÒ¡ÁÕ¡Ô¨¡ÒâͧµÑÇàͧáÅÐÂѧÊÒÁÒöãªéàÇÅÒÊèǹãË­è¡ÑºÊÔ觷Õè¤Ø³ªÍº ¤Ø³·Óä´éá¹è¹Í¹ ¾ºàÃÒä´é·Õè¹Õè http://www.thaiworkathome.com/win â·Ã 0-2277-7850 µèÍ 57 ==¤Ø³ÍÒ¨ã¹ä´é¾ºã¹ÊÔ觷Õè¤Ø³ËÒÁҹҹ㹪ÕÇÔµ¡Ò÷ӧҹ== ¢ÍÍÀÑÂËÒ¡¤Ø³äÁèµéͧ¡ÒÃáµèä´éÃѺ mail ¹Õé ËÒ¡äÁèµéͧ¡ÒÃÃѺ¢èÒÇÊÒèҡàÃÒÍÕ¡ ¡ÃØ³Ò CLICK ä»·Õè http://www.thaiworkathome.com/unsubscribe.asp ¡ÃÍ¡ email-address ¢Í§·èÒ¹ áÅÐ submit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun May 26 22: 0:59 2002 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2558837B404 for ; Sun, 26 May 2002 22:00:53 -0700 (PDT) Received: (from ken@localhost) by panzer.kdm.org (8.11.6/8.9.1) id g4R50o708120; Sun, 26 May 2002 23:00:50 -0600 (MDT) (envelope-from ken) Date: Sun, 26 May 2002 23:00:50 -0600 From: "Kenneth D. Merry" To: Phil Rosenthal Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020526230050.A8026@panzer.kdm.org> References: <004701c20530$68e98a20$0700a8c0@zoom> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <004701c20530$68e98a20$0700a8c0@zoom>; from winter@villaweb.net on Sun, May 26, 2002 at 11:41:39PM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, May 26, 2002 at 23:41:39 -0400, Phil Rosenthal wrote: > I've been using vinum for about a year now, and have been using it on some > pretty large, heavily accessed RAID5 file system (500GB & 70MBits/sec > constantly ). > Is there any reason why a hardware raid would be better, am I missing out on > anything? As someone else mentioned, CPU utilization, and possibly features, depending on the RAID card. > What hardware RAID cards are best under FreeBSD 4.6? I would recommend an Adaptec 5400S. It has a hardware parity engine to accelerate RAID-5 parity calculations, so writes will be faster than on a RAID card without a parity engine. On the read side, I've seen one of those cards pump out 175MBytes/sec. (under NT, the guy doing the test didn't have FreeBSD installed), and I think the benchmarks claim it can do up to 190MB/sec on reads. (From looking at the benchmark web page, it looks like they only got 160MB/sec, but since I've seen it go faster I think that's a tad low.) Writes are obviously slower, but the parity engine helps speed things up. The card also does well with high transaction loads. (disclaimer: I work for Adaptec) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 0:43:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from n12.grp.scd.yahoo.com (n12.grp.scd.yahoo.com [66.218.66.67]) by hub.freebsd.org (Postfix) with SMTP id AC54137B403 for ; Mon, 27 May 2002 00:43:32 -0700 (PDT) X-eGroups-Return: notify-return-stable=FreeBSD.org@returns.groups.yahoo.com Received: from [66.218.66.96] by n12.grp.scd.yahoo.com with NNFMP; 27 May 2002 07:43:30 -0000 Received: (qmail 34824 invoked by uid 7800); 27 May 2002 07:39:57 -0000 Date: 27 May 2002 07:39:57 -0000 Message-ID: <1022485197.166.34823.m13@yahoogroups.com> From: SKATINGEXTREME Moderator To: stable@FreeBSD.org Subject: Welcome to SKATINGEXTREME MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Thank you for being a subscriber to this list. I hope that you get a chance to check out my web sites. I have one at http://www.howard.net/hilary and one also at http://www.webpost.net/sk/SkatersChoice . I will try to be in the chat room on Thursday evenings. Go to Hilarys Skating Center then if you want to try to chat. I would love to get a lot of skaters out there in a chat. Pass the word and lets find some skaters eh. Thanks, Hilary Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 0:46:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from n23.grp.scd.yahoo.com (n23.grp.scd.yahoo.com [66.218.66.79]) by hub.freebsd.org (Postfix) with SMTP id AE3A237B407 for ; Mon, 27 May 2002 00:46:37 -0700 (PDT) X-eGroups-Return: notify-return-stable=FreeBSD.org@returns.groups.yahoo.com Received: from [66.218.66.96] by n23.grp.scd.yahoo.com with NNFMP; 27 May 2002 07:46:37 -0000 Received: (qmail 34824 invoked by uid 7800); 27 May 2002 07:39:57 -0000 Date: 27 May 2002 07:39:57 -0000 Message-ID: <1022485197.166.34823.m13@yahoogroups.com> From: SKATINGEXTREME Moderator To: stable@FreeBSD.org Subject: Welcome to SKATINGEXTREME MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Thank you for being a subscriber to this list. I hope that you get a chance to check out my web sites. I have one at http://www.howard.net/hilary and one also at http://www.webpost.net/sk/SkatersChoice . I will try to be in the chat room on Thursday evenings. Go to Hilarys Skating Center then if you want to try to chat. I would love to get a lot of skaters out there in a chat. Pass the word and lets find some skaters eh. Thanks, Hilary Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 0:53:36 2002 Delivered-To: freebsd-stable@freebsd.org Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by hub.freebsd.org (Postfix) with ESMTP id 12F0A37B401 for ; Mon, 27 May 2002 00:53:28 -0700 (PDT) Received: from alogis.com (kipp@clausthal.int1.b.intern [10.1.1.30]) by alogis.com (8.11.1/8.9.3) with ESMTP id g4R7rCl80299; Mon, 27 May 2002 09:53:12 +0200 (CEST) (envelope-from holger.kipp@alogis.com) Message-ID: <3CF1E1F4.9D9C8C1D@alogis.com> Date: Mon, 27 May 2002 09:36:20 +0200 From: Holger Kipp X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en MIME-Version: 1.0 To: Phil Rosenthal Cc: "Kenneth D. Merry" , freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum References: <004701c20530$68e98a20$0700a8c0@zoom> <20020526230050.A8026@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Kenneth D. Merry" wrote: > > On Sun, May 26, 2002 at 23:41:39 -0400, Phil Rosenthal wrote: > > I've been using vinum for about a year now, and have been using it on some > > pretty large, heavily accessed RAID5 file system (500GB & 70MBits/sec > > constantly ). > > Is there any reason why a hardware raid would be better, am I missing out on > > anything? > > As someone else mentioned, CPU utilization, and possibly features, > depending on the RAID card. Nowadays, the CPU utilization might not be an argument for file servers, as they usually have no CPU utilization. For larger Database-applications I'd always recommend hardware raid, though, especially if using RAID 5 (don't use cheap cards without hardware RAID 5), to avoid cache poisoning. RAID solutions that only use RAID 0 and 1 don't require hardware raid IMHO, but for production use, hot spare support, rebuilding of array in background, etc. might be an issue. Use RAID 0+1 (10) for maximum performance ;-) With hardware raid, you're bound to one controller, though. With software raid, you can mirror across controllers etc. > > What hardware RAID cards are best under FreeBSD 4.6? IMHO the supported ones are a good choice ;-) > I would recommend an Adaptec 5400S. It has a hardware parity engine to > accelerate RAID-5 parity calculations, so writes will be faster than on a > RAID card without a parity engine. We use - 3ware Escalade 7850 If you need RAID 5, but want to use cheaper IDE hard disks. Otherwise, 7810 might do (no hardware raid 5 support). - AMI MegaRAID (Dell PERC 3) If you use a DELL server ;-) - Mylex AcceleRAID 352 No problems so far - but then, each is for different requirements, you better have a look at http://www.freebsd.org/releases/4.5R/hardware-i386.html and choose the one best suited for your requirements ;-) Regards, Holger -- Holger Kipp, Dipl.-Math., Systemadministrator | alogis AG Fon: +49 (0)30 / 43 65 8 - 114 | Berliner Strasse 26 Fax: +49 (0)30 / 43 65 8 - 214 | D-13507 Berlin Tegel email: holger.kipp@alogis.com | http://www.alogis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 1:33:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from vbook.express.ru (asplinux.ru [195.133.213.194]) by hub.freebsd.org (Postfix) with ESMTP id 9CDBA37B47D for ; Mon, 27 May 2002 01:32:46 -0700 (PDT) Received: from vova by vbook.express.ru with local (Exim 3.36 #1) id 17CFvg-0000Fe-00; Mon, 27 May 2002 12:32:36 +0400 Subject: Re: freebsd RC2 and fxp: SCB error From: "Vladimir B. " Grebenschikov To: Guido van Rooij Cc: freebsd-stable@freebsd.org In-Reply-To: <20020526102656.GA40771@gvr.gvr.org> References: <20020526102656.GA40771@gvr.gvr.org> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Mailer: Ximian Evolution 1.0.5 Date: 27 May 2002 12:32:36 +0400 Message-Id: <1022488356.451.18.camel@vbook.express.ru> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG =F7 Sun, 26.05.2002, =D7 14:26, Guido van Rooij =CE=C1=D0=C9=D3=C1=CC: > I have a vaio Z505SX running 4.6-RC2. It has a built in fxp. > It functions fine, however, when I disconnect the utp cable from > the fxp0 interface while it is still up, within one to about 30 > minutes, the system will freeze completely. > Just before that, the kernel tried to print the SCB timeout error > message. It gets corrupted though. Some characters are replaced > by spaces, and some with characters\with the high bit set. >=20 > I haven't had time to look into this further due to that system being use= d > for a tutorial I have to gie shortly. I have seen multiple SCB errors on my VAIO Z505S when boot FreeBSD after windows with out hard reset, It seems windows configure fxp card a bit strange, anyway I didn't see lookups with this. > -Guido =20 --=20 Vladimir B. Grebenschikov vova@sw.ru, SWsoft, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 1:43:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from MX1.estpak.ee (ld1.estpak.ee [194.126.101.98]) by hub.freebsd.org (Postfix) with ESMTP id 97AE637B405 for ; Mon, 27 May 2002 01:43:51 -0700 (PDT) Received: from myhakas.estpak.ee (myhakas.estpak.ee [194.126.115.54]) by MX1.estpak.ee (Postfix) with ESMTP id 45689888D4; Mon, 27 May 2002 11:43:35 +0300 (EEST) Received: from myhakas.estpak.ee (localhost [127.0.0.1]) by myhakas.estpak.ee (8.12.3/8.12.3) with ESMTP id g4R8hmHS010264; Mon, 27 May 2002 11:43:48 +0300 (EEST) (envelope-from vallo@myhakas.estpak.ee) Received: (from vallo@localhost) by myhakas.estpak.ee (8.12.3/8.12.3/Submit) id g4R8hmlo010263; Mon, 27 May 2002 11:43:48 +0300 (EEST) Date: Mon, 27 May 2002 11:43:48 +0300 From: Vallo Kallaste To: Phil Rosenthal Cc: freebsd-stable@FreeBSD.ORG, grog@lemis.com Subject: Re: Hardware RAID vs vinum Message-ID: <20020527084348.GA9774@myhakas.estpak.ee> Reply-To: kalts@estpak.ee References: <004701c20530$68e98a20$0700a8c0@zoom> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <004701c20530$68e98a20$0700a8c0@zoom> User-Agent: Mutt/1.5.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, May 26, 2002 at 11:41:39PM -0400, Phil Rosenthal wrote: > I've been using vinum for about a year now, and have been using it on some > pretty large, heavily accessed RAID5 file system (500GB & 70MBits/sec > constantly ). Have you had dying disk in your vinum R5 configuration? If yes can you please tell me how you rebuilt new disk? I have had no luck rebuilding failed disk while filesystem on the degraded array is mounted and user I/O going on. The disk will be rebuilt and filesystem will be corrupted. I'm able to reproduce it at will with either SCSI or ATA disks, no matter on what system I try it. -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 1:48:43 2002 Delivered-To: freebsd-stable@freebsd.org Received: from n40.grp.scd.yahoo.com (n40.grp.scd.yahoo.com [66.218.66.108]) by hub.freebsd.org (Postfix) with SMTP id 8DC7737B403 for ; Mon, 27 May 2002 01:48:40 -0700 (PDT) X-eGroups-Return: confirm-return-stable=FreeBSD.org@returns.groups.yahoo.com Received: from [66.218.67.193] by n40.grp.scd.yahoo.com with NNFMP; 27 May 2002 08:48:40 -0000 Received: (qmail 2248 invoked by uid 7800); 27 May 2002 08:48:40 -0000 Date: 27 May 2002 08:48:40 -0000 Message-ID: <1022489320.66.2247.m11@yahoogroups.com> From: Yahoo!Groups Notification Reply-To: confirm-unsub-wnH-Cerln-6sJHsk0XzrIu_beDk@yahoogroups.com To: stable@FreeBSD.org Subject: Please reply to unsubscribe from SKATINGEXTREME MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, We have received a request from you to unsubscribe from the SKATINGEXTREME group. Please confirm your request by replying to this message. If you do not wish to unsubscribe from SKATINGEXTREME, please ignore this message. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 1:49:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from n37.grp.scd.yahoo.com (n37.grp.scd.yahoo.com [66.218.66.105]) by hub.freebsd.org (Postfix) with SMTP id 9F3FA37B404 for ; Mon, 27 May 2002 01:49:19 -0700 (PDT) X-eGroups-Return: notify-return-stable=FreeBSD.org@returns.groups.yahoo.com Received: from [66.218.67.201] by n37.grp.scd.yahoo.com with NNFMP; 27 May 2002 08:49:19 -0000 Received: (qmail 74449 invoked by uid 7800); 27 May 2002 08:49:18 -0000 Date: 27 May 2002 08:49:18 -0000 Message-ID: <1022489358.74.74448.m9@yahoogroups.com> From: Yahoo!Groups Notification To: stable@FreeBSD.org Subject: You have been unsubscribed from SKATINGEXTREME MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, This is to inform you that your request to unsubscribe from SKATINGEXTREME has been completed. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 3:12:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from relay2.skif.net (ns2.skif.net [195.58.224.33]) by hub.freebsd.org (Postfix) with ESMTP id 5B22D37B404 for ; Mon, 27 May 2002 03:12:20 -0700 (PDT) Received: from dru.dn.ua (dru.skif.net [195.58.224.122]) by relay2.skif.net (8.12.1/8.12.1) with ESMTP id g4RACGNC079095 for ; Mon, 27 May 2002 13:12:17 +0300 (EEST) Received: (from admin@localhost) by dru.dn.ua (8.12.3/8.12.3) id g4RACEtv082998 for freebsd-stable@freebsd.org; Mon, 27 May 2002 13:12:14 +0300 (EEST) (envelope-from admin) Date: Mon, 27 May 2002 13:12:14 +0300 From: "Vladislav V. Zhuk" To: freebsd-stable@freebsd.org Subject: problem with sound Message-ID: <20020527101214.GB81448@dru.dn.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi! After upgrading fbsd from 4.1.1 to 4.5 appears problem with sound: some times after reboot sound work properly, but later device dsp locks: $ play -d /dev/dsp0.2 -v 4 /usr/ftp/pub/wav/TEST.WAV sox: Can't open output file '/dev/dsp0.2': Device busy $ fstat /dev/dsp USER CMD PID FD MOUNT INUM MODE SZ|DV R/W NAME lsof don't found who lock /dev/dsp too. PS: 4.6-PRERELEASE FreeBSD 4.6-PRERELEASE #0: Thu May 9 10:01:54 from dmesg.boot about my sound card (aureal vortex 2 CARD=8830): pci0: (vendor=0x12eb, dev=0x0002) at 17.0 irq 7 driver from ports/audio/aureal-kmod: $ kldstat Id Refs Address Size Name 1 5 0xc0100000 1da330 kernel 2 1 0xc1329000 21000 bump_saver.ko 3 1 0xc1434000 14000 linux.ko 4 1 0xc1485000 34000 snd_au8830.ko 5 1 0xc14b9000 14000 snd_pcm.ko With freebsd 4.1.1 sound works good What can I do ?? Who lock /dev/dsp?? -- Vladislav V. Zhuk (06267)3-60-03 admin@dru.dn.ua 2:465/197@FidoNet.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 3:43:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by hub.freebsd.org (Postfix) with ESMTP id BB61A37B403 for ; Mon, 27 May 2002 03:43:23 -0700 (PDT) Received: from pc-02 (pc02.ekahuna.com [198.144.200.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Mon, 27 May 2002 03:43:23 -0700 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: stable@FreeBSD.ORG Date: Mon, 27 May 2002 03:43:23 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Sendmail, smmsp, and pid file Reply-To: pjklist@ekahuna.com X-mailer: Pegasus Mail for Win32 (v3.12c) Message-ID: <20020527104323228.AAA458@empty1.ekahuna.com@pc02.ekahuna.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Any particular reason why the sendmail with 4.6-RC is writing sm- client.pid into /var/spool/clientmqueue instead of /var/run? Is this because it needs to be in a world-writable directory because it's not run as root? Bind doesn't seem to have this problem, perhaps because it starts as root and then 'downgrades' itself? -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 3:47:36 2002 Delivered-To: freebsd-stable@freebsd.org Received: from badger.imedia.ru (badger.imedia.ru [195.34.60.206]) by hub.freebsd.org (Postfix) with ESMTP id 798CA37B404 for ; Mon, 27 May 2002 03:47:32 -0700 (PDT) Received: (from eugene@localhost) by badger.imedia.ru (8.11.6/8.11.6) id g4RAlTu05811 for stable@freebsd.org; Mon, 27 May 2002 14:47:29 +0400 (MSD) (envelope-from eugene) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 27 May 2002 14:47:29 +0400 (MSD) Reply-To: Eugene Mitrofanov Organization: Independent Media / Systems From: Eugene Mitrofanov To: stable@freebsd.org Subject: vinum raid0 == system crash Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi I have 2 raid0 volumes on my server. Some time ago one hard disk died and I removed it from the server. Now the system reboots suddenly every 1..5 days. I recompiled kernel with debuging info and located the place of the error: #5 0xc025efc7 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = -1023868912, tf_edi = 1, tf_esi = -1019600896, tf_ebp = -588665332, tf_isp = -588665372, tf_ebx = -1018645472, tf_edx = -1, tf_ecx = 153, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip =-1072268915, tf_cs=8, tf_eflags = 66182, tf_esp = -1023729664, tf_ss = -1023727616}) at ../../i386/i386/trap.c:448 #6 0xc016798d in launch_requests (rq=0xc4868f40, reviveok=0) at ../../dev/vinum/vinumrequest.c:396 #7 0xc01677a2 in vinumstart (bp=0xcf732be4, reviveok=0) at ../../dev/vinum/vinumrequest.c:291 What shall I do now? Can you help me? System is 4.4-stable. I can give other info. What do you need? P.S. Sorry for my English, now I'm trying to learn it :) - - - - 8< - - - - - - - - - - - - - - - - - - - - - - - - - 8< - - - - Eugene V. Mitrofanov | EMIT-RIPN Independent Media System Administrator | EVM7-RIPE http://www.eStart.ru http://www.business.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 6: 3: 3 2002 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id DB60B37B403 for ; Mon, 27 May 2002 06:02:57 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id GAA02388; Mon, 27 May 2002 06:02:44 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda02386; Mon May 27 06:02:33 2002 Received: from cwsys.cwsent.com (cwsys2 [10.1.2.1]) by passer.osg.gov.bc.ca (8.12.3/8.12.3) with ESMTP id g4RD2OLS005773; Mon, 27 May 2002 06:02:24 -0700 (PDT) (envelope-from cy@cwsent.com) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.12.3/8.12.3) with ESMTP id g4RD2Nr1099239; Mon, 27 May 2002 06:02:23 -0700 (PDT) (envelope-from cy@cwsys.cwsent.com) Message-Id: <200205271302.g4RD2Nr1099239@cwsys.cwsent.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - CITS Open Systems Group From: Cy Schubert - CITS Open Systems Group X-os: FreeBSD X-Sender: cy@cwsent.com To: Kirk Strauser Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum In-Reply-To: Message from Kirk Strauser of "26 May 2002 22:52:33 CDT." <87r8jy9ri6.fsf@pooh.int> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 May 2002 06:02:23 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <87r8jy9ri6.fsf@pooh.int>, Kirk Strauser writes: > > At 2002-05-27T03:41:39Z, "Phil Rosenthal" writes: > > > Is there any reason why a hardware raid would be better, am I missing out > > on anything? > > In theory, a hardware RAID should give you better CPU utilization. After > all, a seperate processor (or DSP, etc.) would be doing all of the work that > your main CPU is currently doing. Furthermore, your CPU would be able to > forget about all of the extra abstractions of Vinum, such as plexes, > subdisks, and so on - the RAID could look like one single harddrive. > > In reality, I don't think that the RAID controllers would protect the CPU > from nearly so much work, and I'm almost positive that your CPU will be > orders of magnitude faster than the processor on the controllers. I beg to differ. I don't have any experience with vinum, however I do have experience with other products such as VxVM (Veritas Volume Manager) and ODS (Online Disk Suite). About three years ago a rumor was floating around the building that "NT was faster than Solaris." The customer in this case had a Sparc Ultra 2 system using RAID 5 on ODS (software RAID 5). The application people and the NT folks managed to prove that when the Oracle application was run on an NT system using hardware RAID 5 (of course they didn't mention the hardware RAID 5 part), it ran 37 times faster than on the Sun system. Sun found out and quickly shipped an Ultra 2 with an A3500 array to prove that Sun was no slouch. It turned out that moving the application to hardware RAID improved performance by 40 times. (In the end the customer was not willing to spend the money on an A3500 array so to this day the application still uses software RAID 5, but we've not installed software RAID since then.) Did we see a difference in CPU utilization? No. However ODS and VxVM run below the kernel and cannot be measured by vmstat or sar, which is different to how vinum works because it is part of the kernel. The moral of the story: You get better mileage out of a hardware RAID controller. -- Cheers, Phone: 250-387-8437 Cy Schubert Fax: 250-387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, CITS Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 6:16:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsidian.sentex.ca (obsidian.sentex.ca [64.7.128.101]) by hub.freebsd.org (Postfix) with ESMTP id 1F0BC37B400 for ; Mon, 27 May 2002 06:16:13 -0700 (PDT) Received: from simoen.sentex.net (pyroxene.sentex.ca [199.212.134.18]) by obsidian.sentex.ca (8.12.2/8.12.2) with ESMTP id g4RDGB7U049533; Mon, 27 May 2002 09:16:11 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20020527091240.03ab9ba8@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 27 May 2002 09:18:19 -0400 To: Cy.Schubert@uumail.gov.bc.ca, Kirk Strauser From: Mike Tancsa Subject: Re: Hardware RAID vs vinum Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <200205271302.g4RD2Nr1099239@cwsys.cwsent.com> References: <87r8jy9ri6.fsf@pooh.int> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: By Sentex Communications (obsidian/20020220) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 06:02 AM 27/05/2002 -0700, Cy Schubert - CITS Open Systems Group wrote: >The moral of the story: You get better mileage out of a hardware RAID >controller. But there are a number of factors that mitigate this. a) is the hardware on the card adequate. e.g. an old DAC-960 will not be as fast as vinum running on a P4. b) are the drivers any good c) how good is the software implementation of RAID. I posted to STABLE a while back comparing a couple of benchmarks that showed this not to always be the case. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 6:32:59 2002 Delivered-To: freebsd-stable@freebsd.org Received: from klima.physik.uni-mainz.de (klima.Physik.Uni-Mainz.DE [134.93.180.162]) by hub.freebsd.org (Postfix) with ESMTP id 2BD7637B400; Mon, 27 May 2002 06:32:46 -0700 (PDT) Received: from klima.Physik.Uni-Mainz.DE (Sturm@klima.Physik.Uni-Mainz.DE [134.93.180.162]) by klima.physik.uni-mainz.de (8.12.3/8.12.3) with ESMTP id g4RDWjM7057449; Mon, 27 May 2002 15:32:45 +0200 (CEST) (envelope-from ohartman@klima.physik.uni-mainz.de) Date: Mon, 27 May 2002 15:32:40 +0200 (CEST) From: "Hartmann, O." To: freebsd-stable@freebsd.org Cc: freebsd-questions@freebsd.org Subject: NFS mounts secured by KERBEROS/HEIMDAL, possible in FBSD 4.6? Message-ID: <20020527151740.L56945-100000@klima.physik.uni-mainz.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello. In our environment we use NFS and NIS/YP for distributing and managing a shared environment. Within the last period the structure of this environment growth a little bit complicated and several clients machines running FreeBSD have their own root, but they need to mount centralized shared filesystems from our NFS server. NIS/YP is a bad solution for this purpose, AFS is not a core part of FreeBSD and so I played with (maybe a very naive) the idea to 'kerberize' everything. At this moment we build up a KDC. My intention is to autheticate each machine and each user against a 'heimdalized' or 'kerberized' user database and each NFS export should be exported as a kerberized export. I need to prevent each NFS export to be compromised by an extern client's root, so a extern machine should be able to mount a NFS export - but no root access is gained for no centralized root. Example: the NFS export 'homes' contains all the home directories for our users. Within the NIS/YP domain it is no problem to export them to clients which are under control of a small supervisor group. But within our workgroup of scientists we have an ongrowing group of clients which are not managed centralized, means they have their own root. Problem with NIS/YP and NFS is, that root on those extern clients can gain access to each user by 'su -' when they are member of the NIS/YP domain and have their own local root. You can understand, that this is not a nice and secure solution. My question is: is their a solution with native FreeBSD tools to restrict 'extern' root's access to a NFS share within a NIS/YP domain? My idea is to have a bunch of servers under central control (also NFS and NIS/YP server) and a bunch of local managed clients with their own local root. These machines should be able to mount a NFS export and being member of the NIS/YP domain, but root on those machines must not have access to any root-shares or shares of other users. I saw several mount options for kerberos/heimdal in FreeBSD's manual for mount and I thought this could be a solution. Are their any other working solutions for those problems for FreeBSD 4.6/4.5? Those solutions should work in a environment with a lot of traffic and must be stable like NFS and NIS/YP under FreeBSD 4.6. I would like to welcome each hint, tip or discussion of this problem, my knowledge is rather limited. Thanks a lot. oliver -- MfG O. Hartmann ohartman@klima.physik.uni-mainz.de ------------------------------------------------------------------ IT-Administration des Institutes fuer Physik der Atmosphaere (IPA) ------------------------------------------------------------------ Johannes Gutenberg Universitaet Mainz Becherweg 21 55099 Mainz Tel: +496131/3924662 (Maschinenraum) Tel: +496131/3924144 (Buero) FAX: +496131/3923532 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 6:36: 8 2002 Delivered-To: freebsd-stable@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 7966237B401 for ; Mon, 27 May 2002 06:36:00 -0700 (PDT) Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by energyhq.homeip.net (Postfix) with ESMTP id 42A3E3FCA0; Mon, 27 May 2002 15:35:55 +0200 (CEST) Received: (from flynn@localhost) by energyhq.homeip.net (8.12.3/8.12.3/Submit) id g4RDZqCq072686; Mon, 27 May 2002 15:35:53 +0200 (CEST) Date: Mon, 27 May 2002 15:35:52 +0200 From: Miguel Mendez To: Cy Schubert - CITS Open Systems Group Cc: Kirk Strauser , freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020527153552.A72342@energyhq.homeip.net> Mail-Followup-To: Cy Schubert - CITS Open Systems Group , Kirk Strauser , freebsd-stable@FreeBSD.ORG References: <200205271302.g4RD2Nr1099239@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="0OAP2g/MAC+5xKAE" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200205271302.g4RD2Nr1099239@cwsys.cwsent.com>; from Cy.Schubert@uumail.gov.bc.ca on Mon, May 27, 2002 at 06:02:23AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --0OAP2g/MAC+5xKAE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 27, 2002 at 06:02:23AM -0700, Cy Schubert - CITS Open Systems G= roup wrote: Hi, > Did we see a difference in CPU utilization? No. However ODS and VxVM=20 > run below the kernel and cannot be measured by vmstat or sar, which is=20 > different to how vinum works because it is part of the kernel. I feel curious about this. Both ODS and VxVM are just kernel modules that sit between hardware and the VFS layer if I'm not mistaken. What makes them different than vinum? I think vinum is, essentially, a Volume Manager clone, with it's own enhancements, so I'd expect a simillar behaviour of both programs. OTOH, and don't quote me on this because it's been almost 2 years since I last used VxVM, there's a way to gather cpu/system resources usage with some tools that come with Volume Manager. I agree that having hardware RAID in a box that is running a Database will improve performance noticeably. OTOH, if the box is just a NAS, you'll probably be fine with some sort of software RAID system (be it vinum/raidframe or whatever your OS uses). Sorry for getting a bit off-topic. Cheers, --=20 Miguel Mendez - flynn@energyhq.homeip.net GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! --0OAP2g/MAC+5xKAE Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE88jY4nLctrNyFFPERAg6dAJ0UVL1UbnTy6U3WIBJGGCofGwcuZACghWId WpBGwb/yPKc2f0R3cz4XULo= =usUu -----END PGP SIGNATURE----- --0OAP2g/MAC+5xKAE-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 6:40:28 2002 Delivered-To: freebsd-stable@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 9C3E037B404 for ; Mon, 27 May 2002 06:40:17 -0700 (PDT) Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by energyhq.homeip.net (Postfix) with ESMTP id 31F273FCA0; Mon, 27 May 2002 15:40:19 +0200 (CEST) Received: (from flynn@localhost) by energyhq.homeip.net (8.12.3/8.12.3/Submit) id g4RDeJbq072742; Mon, 27 May 2002 15:40:19 +0200 (CEST) Date: Mon, 27 May 2002 15:40:19 +0200 From: Miguel Mendez To: Cy Schubert - CITS Open Systems Group Cc: Kirk Strauser , freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020527154019.B72342@energyhq.homeip.net> Mail-Followup-To: Cy Schubert - CITS Open Systems Group , Kirk Strauser , freebsd-stable@FreeBSD.ORG References: <200205271302.g4RD2Nr1099239@cwsys.cwsent.com> <20020527153552.A72342@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="JP+T4n/bALQSJXh8" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020527153552.A72342@energyhq.homeip.net>; from flynn@energyhq.homeip.net on Mon, May 27, 2002 at 03:35:52PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --JP+T4n/bALQSJXh8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 27, 2002 at 03:35:52PM +0200, Miguel Mendez wrote: Hi, hate to quote myself... > I feel curious about this. Both ODS and VxVM are just kernel modules > that sit between hardware and the VFS layer if I'm not mistaken. What ^^^^^^^^^^ What I meant there is between real hardware and the device level, as they provide a 'faked' disk that you then access. /me loads more coffee Cheers, --=20 Miguel Mendez - flynn@energyhq.homeip.net GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! --JP+T4n/bALQSJXh8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE88jdCnLctrNyFFPERAv04AKCaE1wk7IwNcF6PDlLN/LvL+a5UcQCfWdR/ 8l3Y0AH5kvqaoriAB60J8+E= =XC7o -----END PGP SIGNATURE----- --JP+T4n/bALQSJXh8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 6:50:30 2002 Delivered-To: freebsd-stable@freebsd.org Received: from glass.dnsart.com (203.141.139.231.user.ad.il24.net [203.141.139.231]) by hub.freebsd.org (Postfix) with ESMTP id 8BE7B37B403 for ; Mon, 27 May 2002 06:50:25 -0700 (PDT) Received: from localhost ([127.0.0.1]) by glass.dnsart.com with esmtp (Exim 3.36 #1) id 17CKrw-0004Jq-00; Mon, 27 May 2002 22:49:04 +0900 Date: Mon, 27 May 2002 22:48:54 +0900 (JST) From: Tod McQuillin X-X-Sender: devin@glass.pun-pun.prv To: Miguel Mendez Cc: Cy Schubert - CITS Open Systems Group , Kirk Strauser , Subject: Re: Hardware RAID vs vinum In-Reply-To: <20020527153552.A72342@energyhq.homeip.net> Message-ID: <20020527224614.V424-100000@glass.pun-pun.prv> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 27 May 2002, Miguel Mendez wrote: > On Mon, May 27, 2002 at 06:02:23AM -0700, Cy Schubert - CITS Open Systems Group wrote: > > > Did we see a difference in CPU utilization? No. However ODS and VxVM > > run below the kernel and cannot be measured by vmstat or sar, which is > > different to how vinum works because it is part of the kernel. > > I feel curious about this. Both ODS and VxVM are just kernel modules > that sit between hardware and the VFS layer if I'm not mistaken. What > makes them different than vinum? I don't have experience with vinum, but we also experienced terrible performance with Sun's ODS and software RAID-5. We didn't notice similar problams with Veritas volume manager. I'm beginning to think it's peculiar to ODS, and that other software RAID-5 implementations probably work a lot better. -- Tod McQuillin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 8:11:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from zardoc.esmtp.org (adsl-63-195-85-27.dsl.snfc21.pacbell.net [63.195.85.27]) by hub.freebsd.org (Postfix) with ESMTP id 5E26B37B407 for ; Mon, 27 May 2002 08:11:50 -0700 (PDT) Received: from zardoc.esmtp.org (localhost [127.0.0.1]) by zardoc.esmtp.org (8.12.4.Beta0/8.12.3) with ESMTP id g4RFARj3018753 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 27 May 2002 08:10:27 -0700 (PDT) Received: (from ca@localhost) by zardoc.esmtp.org (8.12.4.Beta0/8.12.3/Submit) id g4RFAQn1030457; Mon, 27 May 2002 08:10:26 -0700 (PDT) Date: Mon, 27 May 2002 08:10:26 -0700 From: Claus Assmann To: "Philip J. Koenig" Cc: stable@FreeBSD.ORG Subject: Re: Sendmail, smmsp, and pid file Message-ID: <20020527081026.B29438@zardoc.esmtp.org> References: <20020527104323228.AAA458@empty1.ekahuna.com@pc02.ekahuna.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20020527104323228.AAA458@empty1.ekahuna.com@pc02.ekahuna.com>; from pjklist@ekahuna.com on Mon, May 27, 2002 at 03:43:23AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, May 27, 2002, Philip J. Koenig wrote: > Any particular reason why the sendmail with 4.6-RC is writing sm- > client.pid into /var/spool/clientmqueue instead of /var/run? Permissions. > Is this because it needs to be in a world-writable directory because > it's not run as root? /var/spool/clientmqueue is hopefully not "a world-writable directory". However, it is group-writable and sendmail is set-group-ID to that group (smmsp by default). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 8:38:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail017.syd.optusnet.com.au (mail017.syd.optusnet.com.au [210.49.20.175]) by hub.freebsd.org (Postfix) with ESMTP id F107C37B400 for ; Mon, 27 May 2002 08:38:37 -0700 (PDT) Received: from coren (c16973.brasd1.vic.optusnet.com.au [210.49.154.86]) by mail017.syd.optusnet.com.au (8.11.1/8.11.1) with SMTP id g4RFcaX31417 for ; Tue, 28 May 2002 01:38:36 +1000 Message-ID: <005a01c20594$96c4be10$0100a8c0@coren> From: "Emil Mikulic" To: Subject: subscribe Date: Tue, 28 May 2002 01:38:45 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 8:39:39 2002 Delivered-To: freebsd-stable@freebsd.org Received: from empty1.ekahuna.com (empty1.ekahuna.com [198.144.200.196]) by hub.freebsd.org (Postfix) with ESMTP id 5F6CE37B404 for ; Mon, 27 May 2002 08:39:33 -0700 (PDT) Received: from pc-02 (pc02.ekahuna.com [198.144.200.197]) by empty1.ekahuna.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com; Mon, 27 May 2002 08:39:32 -0700 From: "Philip J. Koenig" Organization: The Electric Kahuna Organization To: stable@FreeBSD.ORG Date: Mon, 27 May 2002 08:39:33 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Sendmail, smmsp, and pid file Reply-To: pjklist@ekahuna.com Cc: Claus Assmann In-reply-to: <20020527081026.B29438@zardoc.esmtp.org> References: <20020527104323228.AAA458@empty1.ekahuna.com@pc02.ekahuna.com>; from pjklist@ekahuna.com on Mon, May 27, 2002 at 03:43:23AM -0700 X-mailer: Pegasus Mail for Win32 (v3.12c) Message-ID: <20020527153932631.AAA450@empty1.ekahuna.com@pc02.ekahuna.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 27 May 2002, at 8:10, Claus Assmann boldly uttered: > On Mon, May 27, 2002, Philip J. Koenig wrote: > > Any particular reason why the sendmail with 4.6-RC is writing sm- > > client.pid into /var/spool/clientmqueue instead of /var/run? > > Permissions. > > > Is this because it needs to be in a world-writable directory because > > it's not run as root? > > /var/spool/clientmqueue is hopefully not "a world-writable directory". > However, it is group-writable and sendmail is set-group-ID to that > group (smmsp by default). Thanks for the clarifications Claus. -- Philip J. Koenig pjklist@ekahuna.com Electric Kahuna Systems -- Computers & Communications for the New Millenium To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 9:30:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from lexus.isprime.com (lexus.isprime.com [66.230.130.130]) by hub.freebsd.org (Postfix) with ESMTP id 707B237B401 for ; Mon, 27 May 2002 09:30:50 -0700 (PDT) Received: from zoom (winter@localhost [127.0.0.1]) by lexus.isprime.com (8.11.6/8.11.6) with SMTP id g4RGUlj38327; Mon, 27 May 2002 12:30:47 -0400 (EDT) (envelope-from pr@isprime.com) Message-ID: <00c301c2059b$44313320$0700a8c0@zoom> From: "Phil Rosenthal" To: Cc: , References: <004701c20530$68e98a20$0700a8c0@zoom> <20020527084348.GA9774@myhakas.estpak.ee> Subject: Re: Hardware RAID vs vinum Date: Mon, 27 May 2002 12:26:33 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Disposition-Notification-To: "Phil Rosenthal" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yes I have, but I dont remember exactely how. I believe you switch the drive, and then use the command to star the drive you just inserted. --Phil ----- Original Message ----- From: "Vallo Kallaste" To: "Phil Rosenthal" Cc: ; Sent: Monday, May 27, 2002 4:43 AM Subject: Re: Hardware RAID vs vinum > On Sun, May 26, 2002 at 11:41:39PM -0400, Phil Rosenthal > wrote: > > > I've been using vinum for about a year now, and have been using it on some > > pretty large, heavily accessed RAID5 file system (500GB & 70MBits/sec > > constantly ). > > Have you had dying disk in your vinum R5 configuration? If yes can > you please tell me how you rebuilt new disk? I have had no luck > rebuilding failed disk while filesystem on the degraded array is > mounted and user I/O going on. The disk will be rebuilt and > filesystem will be corrupted. I'm able to reproduce it at will with > either SCSI or ATA disks, no matter on what system I try it. > -- > > Vallo Kallaste > kalts@estpak.ee > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 9:36:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mta7.srv.hcvlny.cv.net (mta7.srv.hcvlny.cv.net [167.206.5.22]) by hub.freebsd.org (Postfix) with ESMTP id DD02037B401 for ; Mon, 27 May 2002 09:36:15 -0700 (PDT) Received: from holden.nerdlabs.com (ool-18bb75de.dyn.optonline.net [24.187.117.222]) by mta7.srv.hcvlny.cv.net (iPlanet Messaging Server 5.0 Patch 2 (built Dec 14 2000)) with ESMTP id <0GWS0039Y3GK42@mta7.srv.hcvlny.cv.net> for freebsd-stable@freebsd.org; Mon, 27 May 2002 12:36:21 -0400 (EDT) Received: by holden.nerdlabs.com (Postfix, from userid 1001) id 2386D1E9; Mon, 27 May 2002 12:31:29 +0000 (GMT) Date: Mon, 27 May 2002 12:31:29 +0000 From: Paul Dlug Subject: fxp0 timeout errors To: freebsd-stable@freebsd.org Message-id: <200205271231.29155.paul@nerdlabs.com> MIME-version: 1.0 X-Mailer: KMail [version 1.4] Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I posted this a while back but didn't get much of an answer beyond (use a 3com card instead). I have a bunch of Dell 1550's with on board Intel NIC's. I received the following messages on the console (below), any attempt to ping results in the message "No buffer space available." May 14 16:03:12 web5 /kernel: fxp0: DMA timeout May 14 16:03:12 web5 /kernel: fxp0: DMA timeout May 14 16:03:12 web5 /kernel: fxp0: SCB timeout: 0x10 0x0 0x80 0x0 May 14 16:03:12 web5 /kernel: fxp0: DMA timeout The first box this happened on I chalked it up to a bad NIC or PCI bridge and had Dell replace the motherboard, the problem hasn't occured since. A week after the same thing happend on another box. This, combined with a number of other posts about these fxp problems makes me suspect this is an OS level problem rather than hardware. This occured under a cvsup'd version of 4.5-STABLE, I then upgraded to 4.6-PRERELEASE as of a few days ago and the problem persisted. The box will be up anywhere from 15min to an hour before the above messages appear and send it out of service. pciconf -l: chip0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x00081166 rev=0x23 hdr=0x00 chip1@pci0:0:1: class=0x060000 card=0x00000000 chip=0x00081166 rev=0x01 hdr=0x00 chip2@pci0:0:2: class=0x060000 card=0x00000000 chip=0x00061166 rev=0x01 hdr=0x00 chip3@pci0:0:3: class=0x060000 card=0x00000000 chip=0x00061166 rev=0x01 hdr=0x00 fxp0@pci0:1:0: class=0x020000 card=0x00da1028 chip=0x12298086 rev=0x08 hdr=0x00 fxp1@pci0:2:0: class=0x020000 card=0x00da1028 chip=0x12298086 rev=0x08 hdr=0x00 none0@pci0:3:0: class=0x030000 card=0x00df1028 chip=0x47521002 rev=0x27 hdr=0x00 isab0@pci0:15:0: class=0x060100 card=0x02001166 chip=0x02001166 rev=0x50 hdr=0x00 atapci0@pci0:15:1: class=0x01018a card=0x00000000 chip=0x02111166 rev=0x00 hdr=0x00 ahc0@pci2:5:0: class=0x010000 card=0x00df1028 chip=0x00cf9005 rev=0x01 hdr=0x00 ahc1@pci2:5:1: class=0x010000 card=0x00df1028 chip=0x00cf9005 rev=0x01 hdr=0x00 It looks like quite a few people are having similiar problems with the fxp cards, is anyone close to a fix? Please let me know if there's anything I can do to assist in debugging this issue. Thanks, Paul P.S. The motherboard is SMP capable but only has one processor installed, SMP is turned off in the kernel configuration. Disks are on an adaptec aic7899 SCSI controller. Server is an NFS client using TCP mounts. Network is 100mbps, switched, fxp0 properly autonegiotates to 100mbps/full duplex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 9:50:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from MX2.estpak.ee (ld1.estpak.ee [194.126.101.98]) by hub.freebsd.org (Postfix) with ESMTP id 1A89737B400 for ; Mon, 27 May 2002 09:50:16 -0700 (PDT) Received: from myhakas.estpak.ee (myhakas.estpak.ee [194.126.115.54]) by MX2.estpak.ee (Postfix) with ESMTP id 342F673844; Mon, 27 May 2002 19:49:55 +0300 (EEST) Received: from myhakas.estpak.ee (localhost [127.0.0.1]) by myhakas.estpak.ee (8.12.3/8.12.3) with ESMTP id g4RGoCHS014035; Mon, 27 May 2002 19:50:12 +0300 (EEST) (envelope-from vallo@myhakas.estpak.ee) Received: (from vallo@localhost) by myhakas.estpak.ee (8.12.3/8.12.3/Submit) id g4RGoBg2014034; Mon, 27 May 2002 19:50:11 +0300 (EEST) Date: Mon, 27 May 2002 19:50:11 +0300 From: Vallo Kallaste To: Phil Rosenthal Cc: kalts@estpak.ee, freebsd-stable@FreeBSD.ORG, grog@lemis.com Subject: Re: Hardware RAID vs vinum Message-ID: <20020527165011.GA14015@myhakas.estpak.ee> Reply-To: kalts@estpak.ee References: <004701c20530$68e98a20$0700a8c0@zoom> <20020527084348.GA9774@myhakas.estpak.ee> <00c301c2059b$44313320$0700a8c0@zoom> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00c301c2059b$44313320$0700a8c0@zoom> User-Agent: Mutt/1.5.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, May 27, 2002 at 12:26:33PM -0400, Phil Rosenthal wrote: > > Have you had dying disk in your vinum R5 configuration? If yes can > > you please tell me how you rebuilt new disk? I have had no luck > > rebuilding failed disk while filesystem on the degraded array is > > mounted and user I/O going on. The disk will be rebuilt and > > filesystem will be corrupted. I'm able to reproduce it at will with > > either SCSI or ATA disks, no matter on what system I try it. > > > Yes I have, but I dont remember exactely how. I believe you > switch the drive, and then use the command to star the drive you > just inserted. Exactly, you start the subdisk. Do you had the filesystem residing on R5 array mounted at the same time? I'm asking because Greg is unable to reproduce it, on the other side I'm able to reproduce at will, go figure. -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 9:55:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from lexus.isprime.com (lexus.isprime.com [66.230.130.130]) by hub.freebsd.org (Postfix) with ESMTP id 0F4E737B404 for ; Mon, 27 May 2002 09:55:10 -0700 (PDT) Received: from zoom (winter@localhost [127.0.0.1]) by lexus.isprime.com (8.11.6/8.11.6) with SMTP id g4RGt6j44335; Mon, 27 May 2002 12:55:06 -0400 (EDT) (envelope-from winter@villaweb.net) Message-ID: <010601c2059e$e1861e30$0700a8c0@zoom> From: "Phil Rosenthal" To: Cc: , , References: <004701c20530$68e98a20$0700a8c0@zoom> <20020527084348.GA9774@myhakas.estpak.ee> <00c301c2059b$44313320$0700a8c0@zoom> <20020527165011.GA14015@myhakas.estpak.ee> Subject: Re: Hardware RAID vs vinum Date: Mon, 27 May 2002 12:52:24 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Disposition-Notification-To: "Phil Rosenthal" X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I did it with the filesystem mounted. --Phil ----- Original Message ----- From: "Vallo Kallaste" To: "Phil Rosenthal" Cc: ; ; Sent: Monday, May 27, 2002 12:50 PM Subject: Re: Hardware RAID vs vinum > On Mon, May 27, 2002 at 12:26:33PM -0400, Phil Rosenthal wrote: > > > > Have you had dying disk in your vinum R5 configuration? If yes can > > > you please tell me how you rebuilt new disk? I have had no luck > > > rebuilding failed disk while filesystem on the degraded array is > > > mounted and user I/O going on. The disk will be rebuilt and > > > filesystem will be corrupted. I'm able to reproduce it at will with > > > either SCSI or ATA disks, no matter on what system I try it. > > > > > Yes I have, but I dont remember exactely how. I believe you > > switch the drive, and then use the command to star the drive you > > just inserted. > > Exactly, you start the subdisk. Do you had the filesystem residing > on R5 array mounted at the same time? I'm asking because Greg is > unable to reproduce it, on the other side I'm able to reproduce at > will, go figure. > -- > > Vallo Kallaste > kalts@estpak.ee > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 10:51: 5 2002 Delivered-To: freebsd-stable@freebsd.org Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by hub.freebsd.org (Postfix) with ESMTP id 5ABBF37B403 for ; Mon, 27 May 2002 10:51:01 -0700 (PDT) Received: from earth.hub.org (earth.hub.org [64.49.215.11]) by earth.hub.org (Postfix) with ESMTP id 5684B103BF1 for ; Mon, 27 May 2002 14:51:00 -0300 (ADT) Date: Mon, 27 May 2002 14:51:00 -0300 (ADT) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Subject: "Can't open pipe" ... but nothing in messages ... Message-ID: <20020527144636.C12810-100000@mail1.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG jupiter# pstat -T 31870/49152 files 1080M/3071M swap space jupiter# pstat -T | less Can't make pipe. jupiter# uname -a FreeBSD jupiter.hub.org 4.6-RC FreeBSD 4.6-RC #11: Sun May 19 14:01:38 CDT 2002 root@jupiter.hub.org:/usr/obj/usr/src/sys/kernel i386 jupiter# What else should I be looking at here? top shows: last pid: 89600; load averages: 80.03, 42.07, 55.81 up 7+22:24:02 12:48:48 2919 processes:3 running, 2916 sleeping CPU states: 11.9% user, 0.0% nice, 12.7% system, 0.5% interrupt, 74.8% idle Mem: 2772M Active, 404M Inact, 387M Wired, 83M Cache, 199M Buf, 98M Free Swap: 3072M Total, 1080M Used, 1991M Free, 35% Inuse and sysctl -a for the system maxproc shows: kern.maxproc: 4116 kern.maxfiles: 49152 so I appear to be well within the various limits that I can think to check ... help? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 11:25:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [216.123.203.186]) by hub.freebsd.org (Postfix) with ESMTP id 3B60D37B406; Mon, 27 May 2002 11:25:19 -0700 (PDT) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.12.3/8.12.3) with ESMTP id g4RIOutI008910; Mon, 27 May 2002 12:24:56 -0600 (MDT) (envelope-from lyndon@orthanc.ab.ca) Message-Id: <200205271824.g4RIOutI008910@orthanc.ab.ca> From: Lyndon Nerenberg Organization: The Frobozz Magic Homing Pigeon Company To: Claus Assmann Cc: "Philip J. Koenig" , stable@FreeBSD.ORG, hackers@FreeBSD.ORG Reply-To: freebsd-hackers@FreeBSD.ORG Subject: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) In-reply-to: Your message of "Mon, 27 May 2002 08:10:26 PDT." <20020527081026.B29438@zardoc.esmtp.org> X-Mailer: mh-e 5.0.92; MH 6.8.4; Emacs 21.2 Date: Mon, 27 May 2002 12:24:56 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Redirecting to the hackers list -- please respect the reply-to header] >>>>> "Claus" == Claus Assmann writes: Claus> On Mon, May 27, 2002, Philip J. Koenig wrote: >> Any particular reason why the sendmail with 4.6-RC is writing sm- >> client.pid into /var/spool/clientmqueue instead of /var/run? Claus> Permissions. This points out a short-fall in the /var/run scheme: it can only be used by processes running with an euid of 0 at the time they create the file. If we have a /var/run/sendmail directory owned by the smmsp user then sendmail can create its pid files there. Likewise for bind. The purgedir function in /etc/rc (used to clean /var/run) will preserve the existing directory structure under /var/run, so the sub-directory tree will survive reboots. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 11:47:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (adsl-66.218.45.239.dslextreme.com [66.218.45.239]) by hub.freebsd.org (Postfix) with SMTP id 6194237B40A for ; Mon, 27 May 2002 11:47:23 -0700 (PDT) Received: (qmail 5678 invoked by uid 1000); 27 May 2002 18:47:44 -0000 Date: Mon, 27 May 2002 11:47:22 -0700 From: Jos Backus To: stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) Message-ID: <20020527184744.GD1724@lizzy.catnook.com> Reply-To: jos@catnook.com Mail-Followup-To: stable@FreeBSD.ORG, hackers@FreeBSD.ORG References: <20020527081026.B29438@zardoc.esmtp.org> <200205271824.g4RIOutI008910@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200205271824.g4RIOutI008910@orthanc.ab.ca> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As this thread once more suggests, the whole concept of pidfiles is broken. The proper way is to use a service control manager which keeps track of processes, allowing them to be stopped/restarted etc. through a single API. (I am not going to mention AIX's System Resource Controller again because some people on this list don't seem to like AIX.) Last time the discussion about daemontools seemed to end in it being a good idea but djb's license being unsuitable, iIrc. So on the 22nd I sent an e-mail to -hackers saying that I have found a BSD-licensed service control manager suitable for import into the base OS, in the hope of restarting this discussion. init(8) doesn't cut it for various reasons: single config file, runs as root, critical to system startup, etc. But it appears I am in a minority because so far I have only received one private response. Mnsho, of course. Jos On Mon, May 27, 2002 at 12:24:56PM -0600, Lyndon Nerenberg wrote: > [Redirecting to the hackers list -- please respect the reply-to header] > > >>>>> "Claus" == Claus Assmann writes: > > Claus> On Mon, May 27, 2002, Philip J. Koenig wrote: > >> Any particular reason why the sendmail with 4.6-RC is writing sm- > >> client.pid into /var/spool/clientmqueue instead of /var/run? > > Claus> Permissions. > > This points out a short-fall in the /var/run scheme: it can only be used > by processes running with an euid of 0 at the time they create the file. > > If we have a /var/run/sendmail directory owned by the smmsp user then > sendmail can create its pid files there. Likewise for bind. The purgedir > function in /etc/rc (used to clean /var/run) will preserve the existing > directory structure under /var/run, so the sub-directory tree will > survive reboots. -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos@catnook.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 11:49:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cicero1.cybercity.dk (cicero1.cybercity.dk [212.242.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 9985D37B400 for ; Mon, 27 May 2002 11:49:21 -0700 (PDT) Received: from user3.cybercity.dk (fxp0.user3.ip.cybercity.dk [212.242.41.36]) by cicero1.cybercity.dk (Postfix) with ESMTP id 5B63D15FC95 for ; Mon, 27 May 2002 20:49:20 +0200 (CEST) Received: from thrawn.birch.se (port320.cvx3-mal.ppp.netlink.se [62.66.14.67]) by user3.cybercity.dk (Postfix) with ESMTP id 3E8C7121 for ; Mon, 27 May 2002 20:49:15 +0200 (CEST) Date: Mon, 27 May 2002 20:49:19 +0200 (CEST) From: =?iso8859-1?Q?Mattias_Bj=F6rk?= X-X-Sender: thrawn@thrawn.birch.se To: stable@FreeBSD.ORG Message-ID: <20020527203834.G11844-200000@thrawn.birch.se> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1790541393-1022525359=:11844" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1790541393-1022525359=:11844 Content-Type: TEXT/PLAIN; charset=iso8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Hi, I have one dual celeron 400 MHz that i runed a make buildworld. And then i export /usr/src and /usr/obj with nfs to my box that I world like to upgrade. Its an p90 laptop, so that is why Im doing the build on my dual 400. :) Any way when I run make installworld on the laptop, I get goes for about 30 sec to one minute and then /usr/bin/install crashes with this error message: mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p /usr/include cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h /usr/include/cam Illegal instruction - core dumped *** Error code 132 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Any clues? I have attched the hole make installworld log. It seems that there is something wrong with my install file or? I copyied it from another machine that is a p120, but that did not help. Same problem, first I thought that It hade something to do with that I was runing make installworld in multiuser mode. But i rebooted and runed it with boot -s but that did not help either. Any clues/tips/flames welcome, as you can see it is no fun at all (TM) to run a make world on a p90. I have done it before and it worked but i rather not do that... :) Perhaps you need more info, then do not hasitate to ask for it. Might take some time to answer this mail because I have some mails to catch up in my mbox... Sorry if i typ to mutch... I will do better next time... Mvh Mattias Bj=F6rk Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN. --0-1790541393-1022525359=:11844 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="installworld.log" Content-Transfer-Encoding: BASE64 Content-ID: <20020527204919.O11844@thrawn.birch.se> Content-Description: Content-Disposition: attachment; filename="installworld.log" U2NyaXB0IHN0YXJ0ZWQgb24gTW9uIE1heSAyNyAyMjozNjoxOCAyMDAyDQoj IG1ha2UgaW5zdGFsbHdvcmxkDQ0KbWtkaXIgLXAgL3RtcC9pbnN0YWxsLjI0 NzQNDQpmb3IgcHJvZyBpbiBbIGF3ayBjYXQgY2hmbGFncyBjaG1vZCBjaG93 biBkYXRlIGVjaG8gZWdyZXAgZmluZCBncmVwICBsbiBtYWtlIG1ha2V3aGF0 aXMgbXRyZWUgbXYgcGVybCBybSBzZWQgc2ggc3lzY3RsICB0ZXN0IHRydWUg dW5hbWUgd2MgemljOyBkbyAgY3AgYHdoaWNoICRwcm9nYCAvdG1wL2luc3Rh bGwuMjQ3NDsgIGRvbmUNDQpjZCAvdXNyL3NyYzsgTUFLRU9CSkRJUlBSRUZJ WD0vdXNyL29iaiAgTUFDSElORV9BUkNIPWkzODYgIE1BQ0hJTkU9aTM4NiAg T0JKRk9STUFUX1BBVEg9L3Vzci9vYmovdXNyL3NyYy9pMzg2L3Vzci9saWJl eGVjICBQRVJMNUxJQj0vdXNyL29iai91c3Ivc3JjL2kzODYvdXNyL2xpYmRh dGEvcGVybC81LjAwNTAzICBHUk9GRl9CSU5fUEFUSD0vdXNyL29iai91c3Iv c3JjL2kzODYvdXNyL2JpbiAgR1JPRkZfRk9OVF9QQVRIPS91c3Ivb2JqL3Vz ci9zcmMvaTM4Ni91c3Ivc2hhcmUvZ3JvZmZfZm9udCAgR1JPRkZfVE1BQ19Q QVRIPS91c3Ivb2JqL3Vzci9zcmMvaTM4Ni91c3Ivc2hhcmUvdG1hYyAgUEFU SD0vdXNyL29iai91c3Ivc3JjL2kzODYvdXNyL3NiaW46L3Vzci9vYmovdXNy L3NyYy9pMzg2L3Vzci9iaW46L3Vzci9vYmovdXNyL3NyYy9pMzg2L3Vzci9n YW1lczovdG1wL2luc3RhbGwuMjQ3NCBtYWtlIC1mIE1ha2VmaWxlLmluYzEg cmVpbnN0YWxsDQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NDQo+Pj4gTWFraW5nIGhp ZXJhcmNoeQ0NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQ0KY2QgL3Vzci9zcmM7IG1h a2UgLWYgTWFrZWZpbGUuaW5jMSBoaWVyYXJjaHkNDQpjZCAvdXNyL3NyYy9l dGM7CQltYWtlIGRpc3RyaWItZGlycw0NCnNldCAtIGBncmVwICJeW2EtekEt Wl0iIC91c3Ivc3JjL2V0Yy9sb2NhbGUuZGVwcmVjYXRlZGA7ICB3aGlsZSBb ICQjIC1ndCAwIF0gOyAgZG8gIGZvciBkaXIgaW4gL3Vzci9zaGFyZS9sb2Nh bGUgIC91c3Ivc2hhcmUvbmxzICAvdXNyL2xvY2FsL3NoYXJlL25sczsgIGRv ICB0ZXN0IC1kIC8ke2Rpcn0gJiYgY2QgLyR7ZGlyfTsgIHRlc3QgLUwgIiQy IiAmJiBybSAtcmYgIiQyIjsgIHRlc3QgXCEgLUwgIiQxIiAmJiB0ZXN0IC1k ICIkMSIgJiYgbXYgIiQxIiAiJDIiOyAgZG9uZTsgIHNoaWZ0OyBzaGlmdDsg IGRvbmUNDQptdHJlZSAtZGVVIC1mIC91c3Ivc3JjL2V0Yy9tdHJlZS9CU0Qu cm9vdC5kaXN0IC1wIC8NDQptdHJlZSAtZGVVIC1mIC91c3Ivc3JjL2V0Yy9t dHJlZS9CU0QudmFyLmRpc3QgLXAgL3Zhcg0NCm10cmVlIC1kZVUgLWYgL3Vz ci9zcmMvZXRjL210cmVlL0JTRC51c3IuZGlzdCAtcCAvdXNyDQ0KbXRyZWUg LWRlVSAtZiAvdXNyL3NyYy9ldGMvbXRyZWUvQlNELmluY2x1ZGUuZGlzdCAg LXAgL3Vzci9pbmNsdWRlDQ0KbXRyZWUgLWRlVSAtZiAvdXNyL3NyYy9ldGMv bXRyZWUvQlNELmluY2x1ZGUuZGlzdCAgLXAgL3Vzci9saWJkYXRhL3Blcmwv NS4wMDUwMy9tYWNoDQ0KY2QgLzsgcm0gLWYgL3N5czsgbG4gLXMgdXNyL3Ny Yy9zeXMgc3lzDQ0KY2QgL3Vzci9zaGFyZS9tYW4vZW4uSVNPODg1OS0xOyBs biAtc2YgLi4vbWFuKiAuDQ0KY2QgL3Vzci9zaGFyZS9tYW47ICBzZXQgLSBg Z3JlcCAiXlthLXpBLVpdIiAvdXNyL3NyYy9ldGMvbWFuLmFsaWFzYDsgIHdo aWxlIFsgJCMgLWd0IDAgXSA7ICBkbyAgcm0gLXJmICIkMSI7ICBsbiAtcyAi JDIiICIkMSI7ICBzaGlmdDsgc2hpZnQ7ICBkb25lDQ0KY2QgL3Vzci9zaGFy ZS9sb2NhbGU7ICBzZXQgLSBgZ3JlcCAiXlthLXpBLVpdIiAvdXNyL3NyYy9l dGMvbG9jYWxlLmFsaWFzYDsgIHdoaWxlIFsgJCMgLWd0IDAgXSA7ICBkbyAg cm0gLXJmICIkMSI7ICBsbiAtcyAiJDIiICIkMSI7ICBzaGlmdDsgc2hpZnQ7 ICBkb25lDQ0KY2QgL3Vzci9zaGFyZS9ubHM7ICBzZXQgLSBgZ3JlcCAiXlth LXpBLVpdIiAvdXNyL3NyYy9ldGMvbmxzLmFsaWFzYDsgIHdoaWxlIFsgJCMg LWd0IDAgXSA7ICBkbyAgcm0gLXJmICIkMSI7ICBsbiAtcyAiJDIiICIkMSI7 ICBzaGlmdDsgc2hpZnQ7ICBkb25lDQ0KDQ0KLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N DQo+Pj4gSW5zdGFsbGluZyBldmVyeXRoaW5nLi4NDQotLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLQ0NCmNkIC91c3Ivc3JjOyBtYWtlIC1mIE1ha2VmaWxlLmluYzEgaW5z dGFsbA0NCj09PT4gc2hhcmUvaW5mbw0NCj09PT4gaW5jbHVkZQ0NCmlmIFsg LWggL3Vzci9pbmNsdWRlL2NhbSBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1 ZGUvY2FtOyAgZmkNDQppZiBbIC1oIC91c3IvaW5jbHVkZS9tc2Rvc2ZzIF07 IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9tc2Rvc2ZzOyAgZmkNDQppZiBb IC1oIC91c3IvaW5jbHVkZS9uZXQgXTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNs dWRlL25ldDsgIGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUvbmV0YXRhbGsg XTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNsdWRlL25ldGF0YWxrOyAgZmkNDQpp ZiBbIC1oIC91c3IvaW5jbHVkZS9uZXRhdG0gXTsgdGhlbiAgcm0gLWYgL3Vz ci9pbmNsdWRlL25ldGF0bTsgIGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUv bmV0Z3JhcGggXTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNsdWRlL25ldGdyYXBo OyAgZmkNDQppZiBbIC1oIC91c3IvaW5jbHVkZS9uZXRpbmV0IF07IHRoZW4g IHJtIC1mIC91c3IvaW5jbHVkZS9uZXRpbmV0OyAgZmkNDQppZiBbIC1oIC91 c3IvaW5jbHVkZS9uZXRpbmV0NiBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1 ZGUvbmV0aW5ldDY7ICBmaQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL25ldGlw eCBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvbmV0aXB4OyAgZmkNDQpp ZiBbIC1oIC91c3IvaW5jbHVkZS9uZXRrZXkgXTsgdGhlbiAgcm0gLWYgL3Vz ci9pbmNsdWRlL25ldGtleTsgIGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUv bmV0bmF0bSBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvbmV0bmF0bTsg IGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUvbmV0bmNwIF07IHRoZW4gIHJt IC1mIC91c3IvaW5jbHVkZS9uZXRuY3A7ICBmaQ0NCmlmIFsgLWggL3Vzci9p bmNsdWRlL25ldG5zIF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9uZXRu czsgIGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUvbmV0c21iIF07IHRoZW4g IHJtIC1mIC91c3IvaW5jbHVkZS9uZXRzbWI7ICBmaQ0NCmlmIFsgLWggL3Vz ci9pbmNsdWRlL25mcyBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvbmZz OyAgZmkNDQppZiBbIC1oIC91c3IvaW5jbHVkZS9udGZzIF07IHRoZW4gIHJt IC1mIC91c3IvaW5jbHVkZS9udGZzOyAgZmkNDQppZiBbIC1oIC91c3IvaW5j bHVkZS9ud2ZzIF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9ud2ZzOyAg ZmkNDQppZiBbIC1oIC91c3IvaW5jbHVkZS9wY2NhcmQgXTsgdGhlbiAgcm0g LWYgL3Vzci9pbmNsdWRlL3BjY2FyZDsgIGZpDQ0KaWYgWyAtaCAvdXNyL2lu Y2x1ZGUvcG9zaXg0IF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9wb3Np eDQ7ICBmaQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL3N5cyBdOyB0aGVuICBy bSAtZiAvdXNyL2luY2x1ZGUvc3lzOyAgZmkNDQppZiBbIC1oIC91c3IvaW5j bHVkZS92bSBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvdm07ICBmaQ0N CmlmIFsgLWggL3Vzci9pbmNsdWRlL2ZzL3NtYmZzIF07IHRoZW4gIHJtIC1m IC91c3IvaW5jbHVkZS9mcy9zbWJmczsgIGZpDQ0KaWYgWyAtaCAvdXNyL2lu Y2x1ZGUvaXNvZnMvY2Q5NjYwIF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVk ZS9pc29mcy9jZDk2NjA7ICBmaQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL3Vm cy9mZnMgXTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNsdWRlL3Vmcy9mZnM7ICBm aQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL3Vmcy9tZnMgXTsgdGhlbiAgcm0g LWYgL3Vzci9pbmNsdWRlL3Vmcy9tZnM7ICBmaQ0NCmlmIFsgLWggL3Vzci9p bmNsdWRlL3Vmcy91ZnMgXTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNsdWRlL3Vm cy91ZnM7ICBmaQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL2Rldi9wcGJ1cyBd OyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvZGV2L3BwYnVzOyAgZmkNDQpp ZiBbIC1oIC91c3IvaW5jbHVkZS9kZXYvdXNiIF07IHRoZW4gIHJtIC1mIC91 c3IvaW5jbHVkZS9kZXYvdXNiOyAgZmkNDQppZiBbIC1oIC91c3IvaW5jbHVk ZS9tYWNoaW5lIF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9tYWNoaW5l OyAgZmkNDQptdHJlZSAtZGVVIC1mIC91c3Ivc3JjL2luY2x1ZGUvLi4vZXRj L210cmVlL0JTRC5pbmNsdWRlLmRpc3QgIC1wIC91c3IvaW5jbHVkZQ0NCmNk IC91c3Ivc3JjL2luY2x1ZGUvLi4vc3lzOyAgaW5zdGFsbCAtQyAtbyByb290 IC1nIHdoZWVsIC1tIDQ0NCBjYW0vKi5oICAvdXNyL2luY2x1ZGUvY2FtDQ0K SWxsZWdhbCBpbnN0cnVjdGlvbiAtIGNvcmUgZHVtcGVkDQ0KKioqIEVycm9y IGNvZGUgMTMyDQ0KDQ0KU3RvcCBpbiAvdXNyL3NyYy9pbmNsdWRlLg0NCioq KiBFcnJvciBjb2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3JjLg0NCioqKiBF cnJvciBjb2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3JjLg0NCioqKiBFcnJv ciBjb2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3JjLg0NCioqKiBFcnJvciBj b2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3JjLg0NCiMgZAggCA== --0-1790541393-1022525359=:11844-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 12:19:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tamu-relay.tamu.edu (smtp-relay-2.tamu.edu [128.194.103.91]) by hub.freebsd.org (Postfix) with ESMTP id B68AE37B403 for ; Mon, 27 May 2002 12:19:43 -0700 (PDT) Received: from localhost (wolf.tamu.edu [128.194.177.13]) by tamu-relay.tamu.edu (8.11.4/8.11.4) with ESMTP id g4RJJgF14742; Mon, 27 May 2002 14:19:43 -0500 (CDT) Date: Mon, 27 May 2002 14:19:42 -0500 Subject: Re: Hardware RAID vs vinum Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v481) Cc: freebsd-stable@FreeBSD.ORG To: kalts@estpak.ee From: David J Duchscher In-Reply-To: <20020527084348.GA9774@myhakas.estpak.ee> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.481) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, May 27, 2002, at 03:43 AM, Vallo Kallaste wrote: > On Sun, May 26, 2002 at 11:41:39PM -0400, Phil Rosenthal > wrote: > >> I've been using vinum for about a year now, and have been using it on >> some >> pretty large, heavily accessed RAID5 file system (500GB & 70MBits/sec >> constantly ). > > Have you had dying disk in your vinum R5 configuration? If yes can > you please tell me how you rebuilt new disk? I have had no luck > rebuilding failed disk while filesystem on the degraded array is > mounted and user I/O going on. The disk will be rebuilt and > filesystem will be corrupted. I'm able to reproduce it at will with > either SCSI or ATA disks, no matter on what system I try it. Have you tried these instructions: http://www.vinumvm.org/vinum/replacing-drive.html -- DaveD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 12:34:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 2F97F37B401 for ; Mon, 27 May 2002 12:34:23 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.11.3/8.10.1) with ESMTP id g4RJXt019983; Mon, 27 May 2002 12:33:55 -0700 (PDT) Date: Mon, 27 May 2002 12:33:55 -0700 (PDT) From: Doug White To: =?iso8859-1?Q?Mattias_Bj=F6rk?= Cc: stable@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <20020527203834.G11844-200000@thrawn.birch.se> Message-ID: <20020527123319.J19516-100000@resnet.uoregon.edu> X-All-Your-Base: are belong to us MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 27 May 2002, [iso8859-1] Mattias Björk wrote: > mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p > /usr/include > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h > /usr/include/cam > Illegal instruction - core dumped If you are migrating from -STABLE to -CURRENT, please read /usr/src/UPDATING for instructions. Hint: It's not the normal -CURRENT to -CURRENT upgrade procedure. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 12:41:49 2002 Delivered-To: freebsd-stable@freebsd.org Received: from dragon.realtime.net (dragon.realtime.net [205.238.128.89]) by hub.freebsd.org (Postfix) with SMTP id ACF5037B407 for ; Mon, 27 May 2002 12:41:44 -0700 (PDT) Received: from tigerfish2.my.domain ([66.25.223.20]) by dragon.realtime.net ; Mon, 27 May 2002 14:40:47 -0600 Received: (from brucegb@localhost) by tigerfish2.my.domain (8.11.6/8.11.6) id g4RJejQ48934; Mon, 27 May 2002 14:40:45 -0500 (CDT) (envelope-from brucegb) Date: Mon, 27 May 2002 14:40:45 -0500 From: Bruce Burden To: =?iso-8859-1?Q?Mattias_Bj=F6rk?= Cc: freebsd-stable@freebsd.org Subject: installworld failure Message-ID: <20020527144045.J248@tigerfish2.my.domain> References: <20020527203834.G11844-200000@thrawn.birch.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020527203834.G11844-200000@thrawn.birch.se>; from thrawn@linux.nu on Mon, May 27, 2002 at 08:49:19PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi Mattias, > > I have one dual celeron 400 MHz that i runed a make buildworld. And then i > export /usr/src and /usr/obj with nfs to my box that I world like to > upgrade. Its an p90 laptop, so that is why Im doing the build on my dual > 400. :) > Did you set your CPUTYPE in the /etc/make.conf to i586? The instruction set the Celeron uses (PII/i686) is different from the instruction set your P90 (P1/i586) uses. Bruce -- ------------------------------------------------------------------------ "I like bad!" Bruce Burden Austin, TX. - Thuganlitha The Power and the Prophet Robert Don Hughes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 12:46:14 2002 Delivered-To: freebsd-stable@freebsd.org Received: from MX1.estpak.ee (ld1.estpak.ee [194.126.101.98]) by hub.freebsd.org (Postfix) with ESMTP id 2FF8337B40B for ; Mon, 27 May 2002 12:46:10 -0700 (PDT) Received: from myhakas.estpak.ee (myhakas.estpak.ee [194.126.115.54]) by MX1.estpak.ee (Postfix) with ESMTP id 81E80887F4; Mon, 27 May 2002 22:45:54 +0300 (EEST) Received: from myhakas.estpak.ee (localhost [127.0.0.1]) by myhakas.estpak.ee (8.12.3/8.12.3) with ESMTP id g4RJk8HS014708; Mon, 27 May 2002 22:46:08 +0300 (EEST) (envelope-from vallo@myhakas.estpak.ee) Received: (from vallo@localhost) by myhakas.estpak.ee (8.12.3/8.12.3/Submit) id g4RJk7Ad014707; Mon, 27 May 2002 22:46:07 +0300 (EEST) Date: Mon, 27 May 2002 22:46:07 +0300 From: Vallo Kallaste To: David J Duchscher Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020527194607.GA14628@myhakas.estpak.ee> Reply-To: kalts@estpak.ee References: <20020527084348.GA9774@myhakas.estpak.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, May 27, 2002 at 02:19:42PM -0500, David J Duchscher wrote: > >Have you had dying disk in your vinum R5 configuration? If yes can > >you please tell me how you rebuilt new disk? I have had no luck > >rebuilding failed disk while filesystem on the degraded array is > >mounted and user I/O going on. The disk will be rebuilt and > >filesystem will be corrupted. I'm able to reproduce it at will with > >either SCSI or ATA disks, no matter on what system I try it. > > Have you tried these instructions: > > http://www.vinumvm.org/vinum/replacing-drive.html Yes I'm aware of these, no I'm not in need of them because of failure simulation only. While testing (simulating) replace and rebuild of failed drive there's no need to physically remove nor repartition disk. You'll place load on filesystem residing on R5 array, then simply force stop (stop -f) one subdisk. After a while running in degraded mode will simply start the subdisk again and reviving process starts. At the end you can be sure that newfs and restore of data is in order. Haven't had any other experience. Smells like FUD but isn't. -- Vallo Kallaste kalts@estpak.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 13:52:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cicero1.cybercity.dk (cicero1.cybercity.dk [212.242.40.4]) by hub.freebsd.org (Postfix) with ESMTP id 13B8E37B405 for ; Mon, 27 May 2002 13:52:23 -0700 (PDT) Received: from user5.cybercity.dk (fxp0.user5.ip.cybercity.dk [212.242.41.51]) by cicero1.cybercity.dk (Postfix) with ESMTP id C0D0715FC3C for ; Mon, 27 May 2002 22:52:21 +0200 (CEST) Received: from thrawn.birch.se (port320.cvx3-mal.ppp.netlink.se [62.66.14.67]) by user5.cybercity.dk (Postfix) with ESMTP id 93CA4F5 for ; Mon, 27 May 2002 22:52:18 +0200 (CEST) Date: Mon, 27 May 2002 22:52:23 +0200 (CEST) From: =?iso8859-1?Q?Mattias_Bj=F6rk?= X-X-Sender: thrawn@thrawn.birch.se To: stable@FreeBSD.ORG Subject: Problems when runing make installworld. In-Reply-To: <20020527203834.G11844-200000@thrawn.birch.se> Message-ID: <20020527224930.K18138-200000@thrawn.birch.se> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-854405875-1022532743=:18138" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-854405875-1022532743=:18138 Content-Type: TEXT/PLAIN; charset=iso8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Hi, Im sorry... I did forget to set a Subject... sorry. The file is also attached here. Mvh Mattias Bj=F6rk Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN. On Mon, 27 May 2002, Mattias Bj=F6rk wrote: > Hi, > > I have one dual celeron 400 MHz that i runed a make buildworld. And then = i > export /usr/src and /usr/obj with nfs to my box that I world like to > upgrade. Its an p90 laptop, so that is why Im doing the build on my dual > 400. :) > > Any way when I run make installworld on the laptop, I get goes for about > 30 sec to one minute and then /usr/bin/install crashes with this error > message: > > mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p > /usr/include > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h > /usr/include/cam > Illegal instruction - core dumped > *** Error code 132 > > Stop in /usr/src/include. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > Any clues? I have attched the hole make installworld log. It seems that > there is something wrong with my install file or? I copyied it from > another machine that is a p120, but that did not help. Same problem, firs= t > I thought that It hade something to do with that I was runing make > installworld in multiuser mode. But i rebooted and runed it with boot -s > but that did not help either. > > Any clues/tips/flames welcome, as you can see it is no fun at all (TM) to > run a make world on a p90. I have done it before and it worked but i > rather not do that... :) > > Perhaps you need more info, then do not hasitate to ask for it. Might tak= e > some time to answer this mail because I have some mails to catch up in > my mbox... > > Sorry if i typ to mutch... I will do better next time... > > Mvh Mattias Bj=F6rk > > Real Programmers don't write in PL/I. PL/I is for programmers who > can't decide whether to write in COBOL or FORTRAN. > --0-854405875-1022532743=:18138 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="installworld.log" Content-Transfer-Encoding: BASE64 Content-ID: <20020527225223.D18138@thrawn.birch.se> Content-Description: Content-Disposition: attachment; filename="installworld.log" U2NyaXB0IHN0YXJ0ZWQgb24gTW9uIE1heSAyNyAyMjozNjoxOCAyMDAyDQoj IG1ha2UgaW5zdGFsbHdvcmxkDQ0KbWtkaXIgLXAgL3RtcC9pbnN0YWxsLjI0 NzQNDQpmb3IgcHJvZyBpbiBbIGF3ayBjYXQgY2hmbGFncyBjaG1vZCBjaG93 biBkYXRlIGVjaG8gZWdyZXAgZmluZCBncmVwICBsbiBtYWtlIG1ha2V3aGF0 aXMgbXRyZWUgbXYgcGVybCBybSBzZWQgc2ggc3lzY3RsICB0ZXN0IHRydWUg dW5hbWUgd2MgemljOyBkbyAgY3AgYHdoaWNoICRwcm9nYCAvdG1wL2luc3Rh bGwuMjQ3NDsgIGRvbmUNDQpjZCAvdXNyL3NyYzsgTUFLRU9CSkRJUlBSRUZJ WD0vdXNyL29iaiAgTUFDSElORV9BUkNIPWkzODYgIE1BQ0hJTkU9aTM4NiAg T0JKRk9STUFUX1BBVEg9L3Vzci9vYmovdXNyL3NyYy9pMzg2L3Vzci9saWJl eGVjICBQRVJMNUxJQj0vdXNyL29iai91c3Ivc3JjL2kzODYvdXNyL2xpYmRh dGEvcGVybC81LjAwNTAzICBHUk9GRl9CSU5fUEFUSD0vdXNyL29iai91c3Iv c3JjL2kzODYvdXNyL2JpbiAgR1JPRkZfRk9OVF9QQVRIPS91c3Ivb2JqL3Vz ci9zcmMvaTM4Ni91c3Ivc2hhcmUvZ3JvZmZfZm9udCAgR1JPRkZfVE1BQ19Q QVRIPS91c3Ivb2JqL3Vzci9zcmMvaTM4Ni91c3Ivc2hhcmUvdG1hYyAgUEFU SD0vdXNyL29iai91c3Ivc3JjL2kzODYvdXNyL3NiaW46L3Vzci9vYmovdXNy L3NyYy9pMzg2L3Vzci9iaW46L3Vzci9vYmovdXNyL3NyYy9pMzg2L3Vzci9n YW1lczovdG1wL2luc3RhbGwuMjQ3NCBtYWtlIC1mIE1ha2VmaWxlLmluYzEg cmVpbnN0YWxsDQ0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NDQo+Pj4gTWFraW5nIGhp ZXJhcmNoeQ0NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQ0KY2QgL3Vzci9zcmM7IG1h a2UgLWYgTWFrZWZpbGUuaW5jMSBoaWVyYXJjaHkNDQpjZCAvdXNyL3NyYy9l dGM7CQltYWtlIGRpc3RyaWItZGlycw0NCnNldCAtIGBncmVwICJeW2EtekEt Wl0iIC91c3Ivc3JjL2V0Yy9sb2NhbGUuZGVwcmVjYXRlZGA7ICB3aGlsZSBb ICQjIC1ndCAwIF0gOyAgZG8gIGZvciBkaXIgaW4gL3Vzci9zaGFyZS9sb2Nh bGUgIC91c3Ivc2hhcmUvbmxzICAvdXNyL2xvY2FsL3NoYXJlL25sczsgIGRv ICB0ZXN0IC1kIC8ke2Rpcn0gJiYgY2QgLyR7ZGlyfTsgIHRlc3QgLUwgIiQy IiAmJiBybSAtcmYgIiQyIjsgIHRlc3QgXCEgLUwgIiQxIiAmJiB0ZXN0IC1k ICIkMSIgJiYgbXYgIiQxIiAiJDIiOyAgZG9uZTsgIHNoaWZ0OyBzaGlmdDsg IGRvbmUNDQptdHJlZSAtZGVVIC1mIC91c3Ivc3JjL2V0Yy9tdHJlZS9CU0Qu cm9vdC5kaXN0IC1wIC8NDQptdHJlZSAtZGVVIC1mIC91c3Ivc3JjL2V0Yy9t dHJlZS9CU0QudmFyLmRpc3QgLXAgL3Zhcg0NCm10cmVlIC1kZVUgLWYgL3Vz ci9zcmMvZXRjL210cmVlL0JTRC51c3IuZGlzdCAtcCAvdXNyDQ0KbXRyZWUg LWRlVSAtZiAvdXNyL3NyYy9ldGMvbXRyZWUvQlNELmluY2x1ZGUuZGlzdCAg LXAgL3Vzci9pbmNsdWRlDQ0KbXRyZWUgLWRlVSAtZiAvdXNyL3NyYy9ldGMv bXRyZWUvQlNELmluY2x1ZGUuZGlzdCAgLXAgL3Vzci9saWJkYXRhL3Blcmwv NS4wMDUwMy9tYWNoDQ0KY2QgLzsgcm0gLWYgL3N5czsgbG4gLXMgdXNyL3Ny Yy9zeXMgc3lzDQ0KY2QgL3Vzci9zaGFyZS9tYW4vZW4uSVNPODg1OS0xOyBs biAtc2YgLi4vbWFuKiAuDQ0KY2QgL3Vzci9zaGFyZS9tYW47ICBzZXQgLSBg Z3JlcCAiXlthLXpBLVpdIiAvdXNyL3NyYy9ldGMvbWFuLmFsaWFzYDsgIHdo aWxlIFsgJCMgLWd0IDAgXSA7ICBkbyAgcm0gLXJmICIkMSI7ICBsbiAtcyAi JDIiICIkMSI7ICBzaGlmdDsgc2hpZnQ7ICBkb25lDQ0KY2QgL3Vzci9zaGFy ZS9sb2NhbGU7ICBzZXQgLSBgZ3JlcCAiXlthLXpBLVpdIiAvdXNyL3NyYy9l dGMvbG9jYWxlLmFsaWFzYDsgIHdoaWxlIFsgJCMgLWd0IDAgXSA7ICBkbyAg cm0gLXJmICIkMSI7ICBsbiAtcyAiJDIiICIkMSI7ICBzaGlmdDsgc2hpZnQ7 ICBkb25lDQ0KY2QgL3Vzci9zaGFyZS9ubHM7ICBzZXQgLSBgZ3JlcCAiXlth LXpBLVpdIiAvdXNyL3NyYy9ldGMvbmxzLmFsaWFzYDsgIHdoaWxlIFsgJCMg LWd0IDAgXSA7ICBkbyAgcm0gLXJmICIkMSI7ICBsbiAtcyAiJDIiICIkMSI7 ICBzaGlmdDsgc2hpZnQ7ICBkb25lDQ0KDQ0KLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0N DQo+Pj4gSW5zdGFsbGluZyBldmVyeXRoaW5nLi4NDQotLS0tLS0tLS0tLS0t LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLQ0NCmNkIC91c3Ivc3JjOyBtYWtlIC1mIE1ha2VmaWxlLmluYzEgaW5z dGFsbA0NCj09PT4gc2hhcmUvaW5mbw0NCj09PT4gaW5jbHVkZQ0NCmlmIFsg LWggL3Vzci9pbmNsdWRlL2NhbSBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1 ZGUvY2FtOyAgZmkNDQppZiBbIC1oIC91c3IvaW5jbHVkZS9tc2Rvc2ZzIF07 IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9tc2Rvc2ZzOyAgZmkNDQppZiBb IC1oIC91c3IvaW5jbHVkZS9uZXQgXTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNs dWRlL25ldDsgIGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUvbmV0YXRhbGsg XTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNsdWRlL25ldGF0YWxrOyAgZmkNDQpp ZiBbIC1oIC91c3IvaW5jbHVkZS9uZXRhdG0gXTsgdGhlbiAgcm0gLWYgL3Vz ci9pbmNsdWRlL25ldGF0bTsgIGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUv bmV0Z3JhcGggXTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNsdWRlL25ldGdyYXBo OyAgZmkNDQppZiBbIC1oIC91c3IvaW5jbHVkZS9uZXRpbmV0IF07IHRoZW4g IHJtIC1mIC91c3IvaW5jbHVkZS9uZXRpbmV0OyAgZmkNDQppZiBbIC1oIC91 c3IvaW5jbHVkZS9uZXRpbmV0NiBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1 ZGUvbmV0aW5ldDY7ICBmaQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL25ldGlw eCBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvbmV0aXB4OyAgZmkNDQpp ZiBbIC1oIC91c3IvaW5jbHVkZS9uZXRrZXkgXTsgdGhlbiAgcm0gLWYgL3Vz ci9pbmNsdWRlL25ldGtleTsgIGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUv bmV0bmF0bSBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvbmV0bmF0bTsg IGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUvbmV0bmNwIF07IHRoZW4gIHJt IC1mIC91c3IvaW5jbHVkZS9uZXRuY3A7ICBmaQ0NCmlmIFsgLWggL3Vzci9p bmNsdWRlL25ldG5zIF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9uZXRu czsgIGZpDQ0KaWYgWyAtaCAvdXNyL2luY2x1ZGUvbmV0c21iIF07IHRoZW4g IHJtIC1mIC91c3IvaW5jbHVkZS9uZXRzbWI7ICBmaQ0NCmlmIFsgLWggL3Vz ci9pbmNsdWRlL25mcyBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvbmZz OyAgZmkNDQppZiBbIC1oIC91c3IvaW5jbHVkZS9udGZzIF07IHRoZW4gIHJt IC1mIC91c3IvaW5jbHVkZS9udGZzOyAgZmkNDQppZiBbIC1oIC91c3IvaW5j bHVkZS9ud2ZzIF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9ud2ZzOyAg ZmkNDQppZiBbIC1oIC91c3IvaW5jbHVkZS9wY2NhcmQgXTsgdGhlbiAgcm0g LWYgL3Vzci9pbmNsdWRlL3BjY2FyZDsgIGZpDQ0KaWYgWyAtaCAvdXNyL2lu Y2x1ZGUvcG9zaXg0IF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9wb3Np eDQ7ICBmaQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL3N5cyBdOyB0aGVuICBy bSAtZiAvdXNyL2luY2x1ZGUvc3lzOyAgZmkNDQppZiBbIC1oIC91c3IvaW5j bHVkZS92bSBdOyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvdm07ICBmaQ0N CmlmIFsgLWggL3Vzci9pbmNsdWRlL2ZzL3NtYmZzIF07IHRoZW4gIHJtIC1m IC91c3IvaW5jbHVkZS9mcy9zbWJmczsgIGZpDQ0KaWYgWyAtaCAvdXNyL2lu Y2x1ZGUvaXNvZnMvY2Q5NjYwIF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVk ZS9pc29mcy9jZDk2NjA7ICBmaQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL3Vm cy9mZnMgXTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNsdWRlL3Vmcy9mZnM7ICBm aQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL3Vmcy9tZnMgXTsgdGhlbiAgcm0g LWYgL3Vzci9pbmNsdWRlL3Vmcy9tZnM7ICBmaQ0NCmlmIFsgLWggL3Vzci9p bmNsdWRlL3Vmcy91ZnMgXTsgdGhlbiAgcm0gLWYgL3Vzci9pbmNsdWRlL3Vm cy91ZnM7ICBmaQ0NCmlmIFsgLWggL3Vzci9pbmNsdWRlL2Rldi9wcGJ1cyBd OyB0aGVuICBybSAtZiAvdXNyL2luY2x1ZGUvZGV2L3BwYnVzOyAgZmkNDQpp ZiBbIC1oIC91c3IvaW5jbHVkZS9kZXYvdXNiIF07IHRoZW4gIHJtIC1mIC91 c3IvaW5jbHVkZS9kZXYvdXNiOyAgZmkNDQppZiBbIC1oIC91c3IvaW5jbHVk ZS9tYWNoaW5lIF07IHRoZW4gIHJtIC1mIC91c3IvaW5jbHVkZS9tYWNoaW5l OyAgZmkNDQptdHJlZSAtZGVVIC1mIC91c3Ivc3JjL2luY2x1ZGUvLi4vZXRj L210cmVlL0JTRC5pbmNsdWRlLmRpc3QgIC1wIC91c3IvaW5jbHVkZQ0NCmNk IC91c3Ivc3JjL2luY2x1ZGUvLi4vc3lzOyAgaW5zdGFsbCAtQyAtbyByb290 IC1nIHdoZWVsIC1tIDQ0NCBjYW0vKi5oICAvdXNyL2luY2x1ZGUvY2FtDQ0K SWxsZWdhbCBpbnN0cnVjdGlvbiAtIGNvcmUgZHVtcGVkDQ0KKioqIEVycm9y IGNvZGUgMTMyDQ0KDQ0KU3RvcCBpbiAvdXNyL3NyYy9pbmNsdWRlLg0NCioq KiBFcnJvciBjb2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3JjLg0NCioqKiBF cnJvciBjb2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3JjLg0NCioqKiBFcnJv ciBjb2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3JjLg0NCioqKiBFcnJvciBj b2RlIDENDQoNDQpTdG9wIGluIC91c3Ivc3JjLg0NCiMgZAggCA== --0-854405875-1022532743=:18138-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 14:36: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id EB15B37B407; Mon, 27 May 2002 14:35:47 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id BAA20122; Tue, 28 May 2002 01:36:00 +0400 (MSD) Message-Id: <200205272136.BAA20122@aaz.links.ru> Subject: Re: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) In-Reply-To: <20020527184744.GD1724@lizzy.catnook.com> from "Jos Backus" at "May 27, 2 11:47:22 am" To: jos@catnook.com Date: Tue, 28 May 2002 01:36:00 +0400 (MSD) Cc: stable@FreeBSD.ORG, hackers@FreeBSD.ORG From: "."@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jos Backus writes: > As this thread once more suggests, the whole concept of pidfiles is broken. > The proper way is to use a service control manager which keeps track of > processes, allowing them to be stopped/restarted etc. through a single API. (I I understand, but there no control manager now, and I suggest some tuning of rights --- etc/mtree/BSD.var.dist Mon Jan 14 14:23:15 2002 +++ etc/mtree/BSD.var.dist Sat Mar 9 20:32:38 2002 @@ -53,7 +53,7 @@ .. preserve .. - run + run gname=daemon mode=1775 ppp gname=network mode=0770 .. .. and every daemon in group 'daemon' while no better method > am not going to mention AIX's System Resource Controller again because some > people on this list don't seem to like AIX.) > > Last time the discussion about daemontools seemed to end in it being a good > idea but djb's license being unsuitable, iIrc. So on the 22nd I sent an > e-mail to -hackers saying that I have found a BSD-licensed service control > manager suitable for import into the base OS, in the hope of restarting this > discussion. init(8) doesn't cut it for various reasons: single config file, > runs as root, critical to system startup, etc. I have a lot of troubles with djb's tools in jail environment: they are unreliable. Are you sure that http://www.io.com/~manoj/file/mktool-0.0.7.tar.gz (are you mean this one?) is better? I do not find docs or mans and am not sure that it is worth-while to dig in thist code instead of simple shell scripts (as in ports/38593 - that is my way to service control manager) > But it appears I am in a minority because so far I have only received one > private response. > > Mnsho, of course. > > Jos > > On Mon, May 27, 2002 at 12:24:56PM -0600, Lyndon Nerenberg wrote: > > [Redirecting to the hackers list -- please respect the reply-to header] > > > > >>>>> "Claus" == Claus Assmann writes: > > > > Claus> On Mon, May 27, 2002, Philip J. Koenig wrote: > > >> Any particular reason why the sendmail with 4.6-RC is writing sm- > > >> client.pid into /var/spool/clientmqueue instead of /var/run? > > > > Claus> Permissions. > > > > This points out a short-fall in the /var/run scheme: it can only be used > > by processes running with an euid of 0 at the time they create the file. > > > > If we have a /var/run/sendmail directory owned by the smmsp user then > > sendmail can create its pid files there. Likewise for bind. The purgedir > > function in /etc/rc (used to clean /var/run) will preserve the existing > > directory structure under /var/run, so the sub-directory tree will > > survive reboots. > > -- > Jos Backus _/ _/_/_/ Santa Clara, CA > _/ _/ _/ > _/ _/_/_/ > _/ _/ _/ _/ > jos@catnook.com _/_/ _/_/_/ use Std::Disclaimer; > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 14:50:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (adsl-66.218.45.239.dslextreme.com [66.218.45.239]) by hub.freebsd.org (Postfix) with SMTP id 5A40C37B405 for ; Mon, 27 May 2002 14:50:10 -0700 (PDT) Received: (qmail 6456 invoked by uid 1000); 27 May 2002 21:50:31 -0000 Date: Mon, 27 May 2002 14:50:09 -0700 From: Jos Backus To: stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) Message-ID: <20020527215031.GA5934@lizzy.catnook.com> Reply-To: jos@catnook.com Mail-Followup-To: stable@FreeBSD.ORG, hackers@FreeBSD.ORG References: <20020527184744.GD1724@lizzy.catnook.com> <200205272136.BAA20122@aaz.links.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200205272136.BAA20122@aaz.links.ru> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, May 28, 2002 at 01:36:00AM +0400, "."@babolo.ru wrote: > I have a lot of troubles with djb's tools in jail environment: > they are unreliable. Huh? What is the problem? While the license causes plenty of problems I have yet to see the programs themselves cause any. Now they may not be a natural fit to what you are trying to do in this case but that doesn't invalidate the idea of a service control manager in general - only perhaps the daemontools implementation for your particular application. > Are you sure that http://www.io.com/~manoj/file/mktool-0.0.7.tar.gz > (are you mean this one?) is better? It's hackable, which compared to daemontools is a big plus. And the author has said he is willing to add some more improvements and documentation. > I do not find docs or mans and am not sure that > it is worth-while to dig in thist code instead of > simple shell scripts (as in ports/38593 - that is > my way to service control manager) Re: docs, see above. If there's sufficient interest I can prod the author or write some myself. The problem with all these homegrown solutions is that they are not portable and lack the necessary features to be of general use, among others. I think first there needs to be consensus that having some sort of service control manager in the base OS is a good idea. Then we can look into possible candidates. Given the long tradition that pidfiles have in UNIX this is probably an uphill battle, even though I think there are plenty of reasons to consider them the result of poor engineering. -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos@catnook.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 14:53:18 2002 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 727E337B405; Mon, 27 May 2002 14:53:09 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id OAA05122; Mon, 27 May 2002 14:53:02 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda05120; Mon May 27 14:52:45 2002 Received: from cwsys.cwsent.com (cwsys2 [10.1.2.1]) by passer.osg.gov.bc.ca (8.12.3/8.12.3) with ESMTP id g4RLqd6h029203; Mon, 27 May 2002 14:52:39 -0700 (PDT) (envelope-from cy@cwsent.com) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.12.3/8.12.3) with ESMTP id g4RLqcr1001386; Mon, 27 May 2002 14:52:38 -0700 (PDT) (envelope-from cy@cwsys.cwsent.com) Message-Id: <200205272152.g4RLqcr1001386@cwsys.cwsent.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - CITS Open Systems Group From: Cy Schubert - CITS Open Systems Group X-os: FreeBSD X-Sender: cy@cwsent.com To: freebsd-hackers@FreeBSD.ORG Cc: Claus Assmann , "Philip J. Koenig" , stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) In-Reply-To: Message from Lyndon Nerenberg of "Mon, 27 May 2002 12:24:56 MDT." <200205271824.g4RIOutI008910@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 May 2002 14:52:38 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <200205271824.g4RIOutI008910@orthanc.ab.ca>, Lyndon Nerenberg writes : > [Redirecting to the hackers list -- please respect the reply-to header] > > >>>>> "Claus" == Claus Assmann writes: > > Claus> On Mon, May 27, 2002, Philip J. Koenig wrote: > >> Any particular reason why the sendmail with 4.6-RC is writing sm- > >> client.pid into /var/spool/clientmqueue instead of /var/run? > > Claus> Permissions. > > This points out a short-fall in the /var/run scheme: it can only be used > by processes running with an euid of 0 at the time they create the file. > > If we have a /var/run/sendmail directory owned by the smmsp user then > sendmail can create its pid files there. Likewise for bind. The purgedir > function in /etc/rc (used to clean /var/run) will preserve the existing > directory structure under /var/run, so the sub-directory tree will > survive reboots. Maybe not for named because you're better off using the -t option. -- Cheers, Phone: 250-387-8437 Cy Schubert Fax: 250-387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, CITS Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 16: 8:20 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id AD11D37B43F for ; Mon, 27 May 2002 16:07:58 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 7107381430; Tue, 28 May 2002 08:37:56 +0930 (CST) Date: Tue, 28 May 2002 08:37:56 +0930 From: Greg 'groggy' Lehey To: Eugene Mitrofanov Cc: stable@freebsd.org Subject: Re: vinum raid0 == system crash Message-ID: <20020528083756.A29491@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 27 May 2002 at 14:47:29 +0400, Eugene Mitrofanov wrote: > Hi > > I have 2 raid0 volumes on my server. Some time ago one hard disk died > and I removed it from the server. Now the system reboots suddenly every > 1..5 days. I recompiled kernel with debuging info and located the place of > the error: > > #5 0xc025efc7 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = -1023868912, > tf_edi = 1, tf_esi = -1019600896, tf_ebp = -588665332, > tf_isp = -588665372, tf_ebx = -1018645472, tf_edx = -1, tf_ecx = 153, > tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip =-1072268915, tf_cs=8, > tf_eflags = 66182, tf_esp = -1023729664, tf_ss = -1023727616}) > at ../../i386/i386/trap.c:448 > #6 0xc016798d in launch_requests (rq=0xc4868f40, reviveok=0) > at ../../dev/vinum/vinumrequest.c:396 > #7 0xc01677a2 in vinumstart (bp=0xcf732be4, reviveok=0) > at ../../dev/vinum/vinumrequest.c:291 > > What shall I do now? Can you help me? > > System is 4.4-stable. I can give other info. What do you need? Read the manual or http://www.vinumvm.org/vinum/replacing-drive.html. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 16:42: 4 2002 Delivered-To: freebsd-stable@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 3042337B403; Mon, 27 May 2002 16:41:58 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id DAA22488; Tue, 28 May 2002 03:42:31 +0400 (MSD) Message-Id: <200205272342.DAA22488@aaz.links.ru> Subject: Re: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) In-Reply-To: <20020527215031.GA5934@lizzy.catnook.com> from "Jos Backus" at "May 27, 2 02:50:09 pm" To: jos@catnook.com Date: Tue, 28 May 2002 03:42:31 +0400 (MSD) Cc: stable@FreeBSD.ORG, hackers@FreeBSD.ORG From: "."@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Jos Backus writes: > On Tue, May 28, 2002 at 01:36:00AM +0400, "."@babolo.ru wrote: > > I have a lot of troubles with djb's tools in jail environment: > > they are unreliable. > Huh? What is the problem? While the license causes plenty of problems I have > yet to see the programs themselves cause any. Now they may not be a natural > fit to what you are trying to do in this case but that doesn't invalidate the > idea of a service control manager in general - only perhaps the daemontools > implementation for your particular application. There are usual retrieval errors in jail+nullfs on startup I never see without jail+nullfs. May be it is the reason for daemontools not to work reliable when nonexpected errors occur - but I am not shure because a lack of time. > > Are you sure that http://www.io.com/~manoj/file/mktool-0.0.7.tar.gz > > (are you mean this one?) is better? > It's hackable, which compared to daemontools is a big plus. And the author > has said he is willing to add some more improvements and documentation. And it is simple. And not terrible disturb usual agreements. Good candidate for ports? as first step to your aim. > > I do not find docs or mans and am not sure that > > it is worth-while to dig in thist code instead of > > simple shell scripts (as in ports/38593 - that is > > my way to service control manager) > Re: docs, see above. If there's sufficient interest I can prod the author or > write some myself. Begin with port. I am interested in particular. For my hundreds jailed services > The problem with all these homegrown solutions is that they are not portable jails not portable now. But it is most reliable way now. > and lack the necessary features to be of general use, among others. Yes. > I think first there needs to be consensus that having some sort of service > control manager in the base OS is a good idea. Then we can look into possible > candidates. Given the long tradition that pidfiles have in UNIX this is > probably an uphill battle, even though I think there are plenty of reasons to > consider them the result of poor engineering. The way: - make a port of service control manager(s) which writes down own pid as usual but handles controled processes himself - give a control step by step (service by service) - may be at FreeBSD 6..8 time it will be accepted in base -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 17:19: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from doom-labs.net (lilith.doom-labs.net [212.66.1.55]) by hub.freebsd.org (Postfix) with ESMTP id 7775137B406 for ; Mon, 27 May 2002 17:18:57 -0700 (PDT) Received: from ceto.doom-labs.net (port-213-20-155-67.reverse.qdsl-home.de [213.20.155.67]) (authenticated) by doom-labs.net (8.11.1/8.11.6) with ESMTP id g4S0GqF02929 for ; Tue, 28 May 2002 02:16:53 +0200 (MET DST) (envelope-from cyberratz@doom-labs.net) Message-Id: <5.1.0.14.0.20020528022254.00ab11e8@mail.doom-labs.net> X-Sender: ekki@mail.doom-labs.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 28 May 2002 02:23:11 +0200 To: freebsd-stable@FreeBSD.org From: "Ekki 'CyberRatz' Gehm" Subject: subscribe freebsd-stable Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 17:26:56 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 6CFD237B403 for ; Mon, 27 May 2002 17:26:51 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 9CE3E8148E; Tue, 28 May 2002 09:56:49 +0930 (CST) Date: Tue, 28 May 2002 09:56:49 +0930 From: Greg 'groggy' Lehey To: Miguel Mendez Cc: Cy Schubert - CITS Open Systems Group , Kirk Strauser , freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020528095649.B16567@wantadilla.lemis.com> References: <200205271302.g4RD2Nr1099239@cwsys.cwsent.com> <20020527153552.A72342@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020527153552.A72342@energyhq.homeip.net> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 27 May 2002 at 15:35:52 +0200, Miguel Mendez wrote: > On Mon, May 27, 2002 at 06:02:23AM -0700, Cy Schubert - CITS Open Systems Group wrote: > >> Did we see a difference in CPU utilization? No. However ODS and VxVM >> run below the kernel and cannot be measured by vmstat or sar, which is >> different to how vinum works because it is part of the kernel. > > I feel curious about this. Both ODS and VxVM are just kernel modules > that sit between hardware and the VFS layer if I'm not mistaken. What > makes them different than vinum? I think vinum is, essentially, a Volume > Manager clone, with it's own enhancements, so I'd expect a simillar > behaviour of both programs. Agreed. I have trouble with this statement too. > OTOH, and don't quote me on this because it's been almost 2 years > since I last used VxVM, there's a way to gather cpu/system resources > usage with some tools that come with Volume Manager. > > I agree that having hardware RAID in a box that is running a > Database will improve performance noticeably. I don't think you can say that in all cases. It depends a lot on what you're comparing. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 17:27:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 015EF37B403 for ; Mon, 27 May 2002 17:27:36 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id F3CC581473; Tue, 28 May 2002 09:57:33 +0930 (CST) Date: Tue, 28 May 2002 09:57:33 +0930 From: Greg 'groggy' Lehey To: Tod McQuillin Cc: Miguel Mendez , Cy Schubert - CITS Open Systems Group , Kirk Strauser , freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020528095733.C16567@wantadilla.lemis.com> References: <20020527153552.A72342@energyhq.homeip.net> <20020527224614.V424-100000@glass.pun-pun.prv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020527224614.V424-100000@glass.pun-pun.prv> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 27 May 2002 at 22:48:54 +0900, Tod McQuillin wrote: > On Mon, 27 May 2002, Miguel Mendez wrote: > >> On Mon, May 27, 2002 at 06:02:23AM -0700, Cy Schubert - CITS Open Systems Group wrote: >> >>> Did we see a difference in CPU utilization? No. However ODS and VxVM >>> run below the kernel and cannot be measured by vmstat or sar, which is >>> different to how vinum works because it is part of the kernel. >> >> I feel curious about this. Both ODS and VxVM are just kernel modules >> that sit between hardware and the VFS layer if I'm not mistaken. What >> makes them different than vinum? > > I don't have experience with vinum, but we also experienced terrible > performance with Sun's ODS and software RAID-5. We didn't notice similar > problams with Veritas volume manager. > > I'm beginning to think it's peculiar to ODS, and that other software > RAID-5 implementations probably work a lot better. This makes more sense to me. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 17:29:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id D7F3937B404 for ; Mon, 27 May 2002 17:29:49 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 20FFC81473; Tue, 28 May 2002 09:59:48 +0930 (CST) Date: Tue, 28 May 2002 09:59:48 +0930 From: Greg 'groggy' Lehey To: Cy Schubert - CITS Open Systems Group Cc: Kirk Strauser , freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020528095948.D16567@wantadilla.lemis.com> References: <87r8jy9ri6.fsf@pooh.int> <200205271302.g4RD2Nr1099239@cwsys.cwsent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200205271302.g4RD2Nr1099239@cwsys.cwsent.com> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 27 May 2002 at 6:02:23 -0700, Cy Schubert - CITS Open Systems Group wrote: > > It turned out that moving the application to hardware RAID improved > performance by 40 times. This can only happen if there's something very wrong with the software RAID-5, either the implementation or the configuration. One thing that springs to mind is too small a stripe size. There's a myth going around that this improves performance, when in fact it seriously degrades it. I believe that some hardware RAID controllers may require it because of the algorithms the firmware uses, but that doesn't make it a good idea. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 18: 7: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (adsl-66.218.45.239.dslextreme.com [66.218.45.239]) by hub.freebsd.org (Postfix) with SMTP id DDFC637B401 for ; Mon, 27 May 2002 18:06:47 -0700 (PDT) Received: (qmail 7203 invoked by uid 1000); 28 May 2002 01:07:08 -0000 Date: Mon, 27 May 2002 18:06:46 -0701 From: Jos Backus To: stable@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) Message-ID: <20020528010708.GB5934@lizzy.catnook.com> Reply-To: jos@catnook.com Mail-Followup-To: stable@FreeBSD.ORG, hackers@FreeBSD.ORG References: <20020527215031.GA5934@lizzy.catnook.com> <200205272342.DAA22488@aaz.links.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200205272342.DAA22488@aaz.links.ru> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, May 28, 2002 at 03:42:31AM +0400, "."@babolo.ru wrote: > There are usual retrieval errors in jail+nullfs > on startup I never see without jail+nullfs. > May be it is the reason for daemontools not to work > reliable when nonexpected errors occur - but > I am not shure because a lack of time. Possibly, yes. > And it is simple. And not terrible disturb usual > agreements. Good candidate for ports? > as first step to your aim. I would like to see this integrated into the base OS (a la inetd) to manage the daemons that are already part of the base OS and are currently not being managed. First, people have to agree that having some kind of generic service control manager is a good idea. After all, inetd was written so people would not have to duplicate its functionality every time. inetd could be run under this manager btw. If people think this is a bad idea (and consequently think that pidfiles are the right solution for this type of problem instead of fork()/wait()) I suppose I (or somebody else) could create a port but my main goal would have been lost at that point. I would really like some more discussion on the pros and cons of the basic idea. > Begin with port. > I am interested in particular. > For my hundreds jailed services See above... > > The problem with all these homegrown solutions is that they are not portable > jails not portable now. > But it is most reliable way now. Yes, some OS constructs such as jails are non-portable but service monitoring should not be one of them. The SysV rc.d mechanism, while standardized, doesn't provide for any kind of monitoring facility. This software fills that gap, and it would be nice to see the *BSDs at least to incorporate this functionality. > The way: > - make a port of service control manager(s) which writes down > own pid as usual but handles controled processes himself I will look into creating a port since you insist :-) > - give a control step by step (service by service) I'm not sure what you mean by this? > - may be at FreeBSD 6..8 time it will be accepted in base I will have given up long before if it looks like it is going to take that long to get such basic functionality into FreeBSD. Thanks for your feedback. -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos@catnook.com _/_/ _/_/_/ use Std::Disclaimer; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 19:19:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.quantified.com (ns2.quantified.com [63.212.171.3]) by hub.freebsd.org (Postfix) with ESMTP id 0621237B406 for ; Mon, 27 May 2002 19:19:42 -0700 (PDT) Received: from danzig.sd.quantified.net (web.quantified.com [63.212.171.5]) by mail.quantified.com (8.12.1/8.12.1) with ESMTP id g4S2JTlg087446 for ; Mon, 27 May 2002 19:19:33 -0700 (PDT) (envelope-from dsilver@urchin.com) Date: Mon, 27 May 2002 19:19:33 -0700 (PDT) From: Doug Silver X-Sender: dsilver@danzig.sd.quantified.net To: stable@freebsd.org Subject: Clarification using cvsup-> 4.x-stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Filter-Version: 1.7 (mail.quantified.com) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just want to make sure the sources I just got are correct as originally I wanted to get 4.5-stable, so I put this in my cvsup file: *default release=cvs tag=RELENG_4 did the buildworld/buildkernel fine, but upon reboot I see this: # uname -rs FreeBSD 4.6-RC Is this really 4.5-stable? Should I just wait until June 1 for 4.6-stable? TIA -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Doug Silver Network Manager Urchin Corporation http://www.urchin.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 19:20:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from doom-labs.net (lilith.doom-labs.net [212.66.1.55]) by hub.freebsd.org (Postfix) with ESMTP id DBB7E37B401 for ; Mon, 27 May 2002 19:20:43 -0700 (PDT) Received: (from ekki@localhost) by doom-labs.net (8.11.1/8.11.6) id g4S2Iek04105 for freebsd-stable@freebsd.org; Tue, 28 May 2002 04:18:40 +0200 (MET DST) (envelope-from cyberratz@doom-labs.net) X-Authentication-Warning: lilith.securitas.net: ekki set sender to cyberratz@doom-labs.net using -f Date: Tue, 28 May 2002 04:18:40 +0200 From: Cyberratz To: freebsd-stable@freebsd.org Subject: subscribe Message-ID: <20020528041840.B4061@mail.doom-labs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Arbitrary-Number-Of-The-Day: 42 X-URL: http://www.doom-labs.net X-Disclaimer: Nothing is like it seems to be... Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe -- [yberR@tz * mailto:cyberratz@doom-labs.net DOOM-LABS Inc. * http://www.doom-labs.net Frag Content * ICQ: 19711450 Experience is what you get when you were expecting something else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 19:24: 2 2002 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id 5B2A037B404 for ; Mon, 27 May 2002 19:23:59 -0700 (PDT) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id 60D633198D4; Mon, 27 May 2002 21:23:59 -0500 (CDT) Date: Mon, 27 May 2002 21:23:59 -0500 From: "David W. Chapman Jr." To: Doug Silver Cc: stable@freebsd.org Subject: Re: Clarification using cvsup-> 4.x-stable Message-ID: <20020528022359.GG93060@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: Doug Silver , stable@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.99i X-Operating-System: FreeBSD 4.5-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, May 27, 2002 at 07:19:33PM -0700, Doug Silver wrote: > I just want to make sure the sources I just got are correct as originally > I wanted to get 4.5-stable, so I put this in my cvsup file: > > *default release=cvs tag=RELENG_4 > > did the buildworld/buildkernel fine, but upon reboot I see this: > > # uname -rs > FreeBSD 4.6-RC 4.6-RC is the -stable branch during a certain period of time preceding 4.6-STABLE I think its documented somewhere, but we really need to make it readily available because this question is asked quite often. Does anyone know a url that describes this? -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 19:39: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tombstone.b.org.nz (tombstone.paradise.gen.nz [202.49.254.2]) by hub.freebsd.org (Postfix) with ESMTP id 7D16137B401 for ; Mon, 27 May 2002 19:39:00 -0700 (PDT) Received: (qmail 7374 invoked by uid 1002); 28 May 2002 02:38:59 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 May 2002 02:38:59 -0000 Date: Tue, 28 May 2002 14:38:59 +1200 (NZST) From: silver@where.else.net.nz X-Sender: silver@tombstone.paradise.gen.nz To: Cyberratz Cc: freebsd-stable@freebsd.org Subject: Re: subscribe In-Reply-To: <20020528041840.B4061@mail.doom-labs.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 28 May 2002, Cyberratz wrote: >subscribe That's not going to work. You need to email "majordomo@freebsd.org" and put "subscribe freebsd-stable" in the body of the message to subscribe to the list. Sending messages to "freebsd-stable@freebsd.org" just sends messages to the list with "subscribe" in them, which probably isn't what you want :) See: http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 19:39:57 2002 Delivered-To: freebsd-stable@freebsd.org Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 4B3EE37B403 for ; Mon, 27 May 2002 19:39:53 -0700 (PDT) Received: from localhost (localhost [::1]) by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet6 id g4S2dpv37451 for ; Tue, 28 May 2002 11:39:51 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <20020528022359.GG93060@leviathan.inethouston.net> References: <20020528022359.GG93060@leviathan.inethouston.net> X-User-Agent: Mew/1.94.2 XEmacs/21.5 (bamboo) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 9 From: Makoto Matsushita To: stable@freebsd.org Subject: Re: Clarification using cvsup-> 4.x-stable Date: Tue, 28 May 2002 11:39:49 +0900 Message-Id: <20020528113949W.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG dwcjr> I think its documented somewhere, but we really need to make it dwcjr> readily available because this question is asked quite often. dwcjr> Does anyone know a url that describes this? -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 19:42:34 2002 Delivered-To: freebsd-stable@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id 6534337B404 for ; Mon, 27 May 2002 19:42:30 -0700 (PDT) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id C8FBE3198D4; Mon, 27 May 2002 21:42:35 -0500 (CDT) Date: Mon, 27 May 2002 21:42:35 -0500 From: "David W. Chapman Jr." To: Makoto Matsushita Cc: stable@freebsd.org Subject: Re: Clarification using cvsup-> 4.x-stable Message-ID: <20020528024235.GJ93060@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: Makoto Matsushita , stable@freebsd.org References: <20020528022359.GG93060@leviathan.inethouston.net> <20020528113949W.matusita@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020528113949W.matusita@jp.FreeBSD.org> User-Agent: Mutt/1.3.99i X-Operating-System: FreeBSD 4.5-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, May 28, 2002 at 11:39:49AM +0900, Makoto Matsushita wrote: > > dwcjr> I think its documented somewhere, but we really need to make it > dwcjr> readily available because this question is asked quite often. > dwcjr> Does anyone know a url that describes this? > > Thanks! I knew we must have had something somewhere, should we stick it on the handbook under the cvsup section as a note? -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 19:46: 5 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc54.attbi.com (rwcrmhc54.attbi.com [216.148.227.87]) by hub.freebsd.org (Postfix) with ESMTP id 20C2B37B404 for ; Mon, 27 May 2002 19:46:01 -0700 (PDT) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc54.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020528024600.JNT13253.rwcrmhc54.attbi.com@bmah.dyndns.org>; Tue, 28 May 2002 02:46:00 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.3/8.12.3) with ESMTP id g4S2k0Xu074322; Mon, 27 May 2002 19:46:00 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.3/8.12.3/Submit) id g4S2k02E074321; Mon, 27 May 2002 19:46:00 -0700 (PDT) Message-Id: <200205280246.g4S2k02E074321@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20020506 with nmh-1.0.4 To: "David W. Chapman Jr." Cc: Doug Silver , stable@FreeBSD.ORG Subject: Re: Clarification using cvsup-> 4.x-stable In-reply-to: <20020528022359.GG93060@leviathan.inethouston.net> References: <20020528022359.GG93060@leviathan.inethouston.net> Comments: In-reply-to "David W. Chapman Jr." message dated "Mon, 27 May 2002 21:23:59 -0500." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 27 May 2002 19:46:00 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If memory serves me right, "David W. Chapman Jr." wrote: > On Mon, May 27, 2002 at 07:19:33PM -0700, Doug Silver wrote: > > I just want to make sure the sources I just got are correct as originally > > I wanted to get 4.5-stable, so I put this in my cvsup file: > > > > *default release=cvs tag=RELENG_4 > > > > did the buildworld/buildkernel fine, but upon reboot I see this: > > > > # uname -rs > > FreeBSD 4.6-RC > > 4.6-RC is the -stable branch during a certain period of time > preceding 4.6-STABLE > > I think its documented somewhere, but we really need to make it > readily available because this question is asked quite often. Does > anyone know a url that describes this? http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RELEASE-CANDIDATE Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 19:55:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from lakemtao07.cox.net (lakemtao07.cox.net [68.1.17.114]) by hub.freebsd.org (Postfix) with ESMTP id E93FD37B400 for ; Mon, 27 May 2002 19:55:51 -0700 (PDT) Received: from mmcable.com ([68.97.112.30]) by lakemtao07.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20020528025549.ELLA1131.lakemtao07.cox.net@mmcable.com> for ; Mon, 27 May 2002 22:55:49 -0400 Message-ID: <3CF2F1A7.86E26EB3@mmcable.com> Date: Mon, 27 May 2002 21:55:35 -0500 From: Fuzzy Buffalo Organization: Yepper X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: subscribe freebsd-stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 20:26:30 2002 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.pwhsnet.com (adsl-64-172-148-54.dsl.scrm01.pacbell.net [64.172.148.54]) by hub.freebsd.org (Postfix) with ESMTP id B64D137B408 for ; Mon, 27 May 2002 20:26:12 -0700 (PDT) Received: from zeus (patrick@zeus.pwhsnet.com [192.168.0.3]) by apollo.pwhsnet.com (8.11.6/8.11.6) with SMTP id g4S3R7f75825; Mon, 27 May 2002 20:27:07 -0700 (PDT) (envelope-from patrick@pwhsnet.com) Message-ID: <01d001c205f6$e04fb910$0300a8c0@zeus> From: "Patrick O. Fish" To: Cc: Subject: Fw: subscribe Date: Mon, 27 May 2002 20:22:20 -0700 Organization: PWHS Networks MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: To: "Cyberratz" Cc: Sent: Monday, May 27, 2002 7:38 PM Subject: Re: subscribe > On Tue, 28 May 2002, Cyberratz wrote: > > >subscribe > > That's not going to work. You need to email "majordomo@freebsd.org" and > put "subscribe freebsd-stable" in the body of the message to subscribe to > the list. Sending messages to "freebsd-stable@freebsd.org" just sends > messages to the list with "subscribe" in them, which probably isn't what > you want :) > > See: http://www.freebsd.org/handbook/eresources.html#ERESOURCES-MAIL > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 21:16:13 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id 2D0FA37B401 for ; Mon, 27 May 2002 21:16:07 -0700 (PDT) Received: (qmail 17697 invoked by uid 0); 28 May 2002 04:16:05 -0000 Received: from p50910887.dip0.t-ipconnect.de (HELO mail.gsinet.sittig.org) (80.145.8.135) by mail.gmx.net (mp011-rz3) with SMTP; 28 May 2002 04:16:05 -0000 Received: (qmail 91466 invoked from network); 27 May 2002 21:57:43 -0000 Received: from shell.gsinet.sittig.org (192.168.11.153) by mail.gsinet.sittig.org with SMTP; 27 May 2002 21:57:43 -0000 Received: (from sittig@localhost) by shell.gsinet.sittig.org (8.11.3/8.11.3) id g4RLvaY91453 for stable@freebsd.org; Mon, 27 May 2002 23:57:36 +0200 (CEST) (envelope-from sittig) Date: Mon, 27 May 2002 23:57:36 +0200 From: Gerhard Sittig To: stable@freebsd.org Subject: Re: 4.6-PRERELASE fxp alias woes Message-ID: <20020527235736.S1494@shell.gsinet.sittig.org> Mail-Followup-To: stable@freebsd.org References: <20020526105404.Q1494@shell.gsinet.sittig.org> <19769.1022443789@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <19769.1022443789@verdi.nethelp.no>; from sthaug@nethelp.no on Sun, May 26, 2002 at 10:09:49PM +0200 Organization: System Defenestrators Inc. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [ can you *please* leave the attribution intact? it's hard to recognize after your reply who said what when. this can cause bad blood, but at least easily leads to misunderstandings after a few turnarounds or should more people be involved than two. ] On Sun, May 26, 2002 at 22:09 +0200, sthaug@nethelp.no wrote: > > > [ ... ifconfig(8) enforces correct netmasks for aliases ... ] > > > > Well, right after sending my first reply I felt that I should > > have put an example in it. :) Imagine the following setup: > > > > ifconfig_fxp0=" inet 192.168.20.120 netmask 255.255.255.0" > > ifconfig_fxp0_alias0="inet 192.168.30.130 netmask 255.255.255.255" > > > > Of course a program can detect that these values "don't fit". But > > how do you determine if the alias entry's address is wrong or the > > netmask? Only an admin can, looking at the local topology. Not > > even human spectators can decide which of the parameters needs > > correction. > > *Why* should the program try to guess anything at all? Only if the > configuration lines are in conflict should the program try to do > something - otherwise it should assume that the values are correct. > > In this case, 192.168.20.120/24 as the primary address and > 192.168.30.130/32 as an alias are perfectly fine. No conflict, no > reason for ifconfig (or the kernel) to try to guess anything. Excuse me? 192.168.30.130/32 is _not_ inside the 192.168.20.120/24 subnet and thus "something" is wrong here. And a machine (as well as any human spectator not familiar with the local topology) has a rather hard time to see which of the two parameters -- address and netmask -- is wrongly specified. > [ ... ] > > How do the rules I proposed prevent this example? I wrote: > > > Very simple. Allow the same netmask as the primary address, *and* /32. > > Nothing else. > ... > > For other subnets (not on the same subnet as the primary address): Let > > the first alias decide the netmask, complain if further aliases within > > the same subnet (as specified by the alias of the first netmask) use a > > different netmask (but allow /32). But isn't this exactly what the program currently enforces and what makes people wonder why their previously already broken setup "suddenly" gets rejected? BTW do I understand it to be a little wider: The primary config wants aliases within the same subnet to have a /32 netmask. Plus should further aliases introduce more subnets all subsequent aliases inside these subnets should have a /32 netmask, too. ISTR that the manpage words it this way that one has to provide "non conflicting netmasks" for the aliases. [ I get the feeling we both expect the same thing from a machine and the ifconfig(8) behaviour is fine to most of us and the "discussion" in this thread is simply a misunderstanding or too quick reading ... ] > [ ... ] > > A further point is that having addresses on the same subnet all use the > same netmask is more natural than using /32 for the aliases, if you've > never used an alias before. Having to use /32 breaks POLA. Yes, I believed this before, too. :) But as long as the current status is consistent in itself and well documented (I found references on my 4.3-STABLE system in the ifconfig(8) and rc.conf(5) manpages as well as /etc/defaults/rc.conf examples, all within one minute by using the pager's search facility) I don't have a problem with it. Actually a well defined and known behaviour is better than any "would be nice to have". :] I don't know if anybody is keen enough on non /32 netmasks for the aliases to produce a patch. And no, I have a hard time to come up with any more complex or "more intelligent" algorithm than what is currently implemented. Neither would I like to. Any kind of DWIM makes me dizzy when I communicate to computers (actually: try to control them). I'd rather get an error message and a chance to correct things than have a fuzzy method jump in and try to interpret what I wanted to do. That's why I keep away from DOS machines. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" Gerhard.Sittig@gmx.net -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon May 27 23:55:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by hub.freebsd.org (Postfix) with ESMTP id 4438737B405 for ; Mon, 27 May 2002 23:55:39 -0700 (PDT) Received: from P1200N (203-79-82-182.adsl-wns.paradise.net.nz [203.79.82.182]) by deborah.paradise.net.nz (Postfix) with SMTP id E9919D2640 for ; Tue, 28 May 2002 18:55:37 +1200 (NZST) Message-ID: <018d01c20614$884a2bb0$0900a8c0@P1200N> From: "Dr David Hingston" To: References: <20020528022359.GG93060@leviathan.inethouston.net> <200205280246.g4S2k02E074321@intruder.bmah.org> Subject: Re: Clarification using cvsup-> 4.x-stable Date: Tue, 28 May 2002 18:54:37 +1200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kewl So if we want to limit the update to 4.5 stable and not 4.6-RC how do we do that? With thanks in advance David Hingston ----- Original Message ----- From: "Bruce A. Mah" To: "David W. Chapman Jr." Cc: "Doug Silver" ; Sent: Tuesday, May 28, 2002 2:46 PM Subject: Re: Clarification using cvsup-> 4.x-stable > If memory serves me right, "David W. Chapman Jr." wrote: > > On Mon, May 27, 2002 at 07:19:33PM -0700, Doug Silver wrote: > > > I just want to make sure the sources I just got are correct as originally > > > I wanted to get 4.5-stable, so I put this in my cvsup file: > > > > > > *default release=cvs tag=RELENG_4 > > > > > > did the buildworld/buildkernel fine, but upon reboot I see this: > > > > > > # uname -rs > > > FreeBSD 4.6-RC > > > > 4.6-RC is the -stable branch during a certain period of time > > preceding 4.6-STABLE > > > > I think its documented somewhere, but we really need to make it > > readily available because this question is asked quite often. Does > > anyone know a url that describes this? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RELEASE-CAND IDATE > > Bruce. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 0: 4:32 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtp.sw.oz.au (smtp.sw.oz.au [203.31.96.1]) by hub.freebsd.org (Postfix) with ESMTP id D4D4D37B408 for ; Tue, 28 May 2002 00:04:27 -0700 (PDT) Received: (from vance@localhost) by smtp.sw.oz.au (8.8.8+Sun/8.8.8) id RAA29299; Tue, 28 May 2002 17:04:15 +1000 (EST) Date: Tue, 28 May 2002 17:04:15 +1000 From: Christopher Vance To: Dr David Hingston Cc: stable@FreeBSD.ORG Subject: Re: Clarification using cvsup-> 4.x-stable Message-ID: <20020528170415.B2433@aurema.com> References: <20020528022359.GG93060@leviathan.inethouston.net> <200205280246.g4S2k02E074321@intruder.bmah.org> <018d01c20614$884a2bb0$0900a8c0@P1200N> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <018d01c20614$884a2bb0$0900a8c0@P1200N>; from tortise@paradise.net.nz on Tue, May 28, 2002 at 06:54:37PM +1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, May 28, 2002 at 06:54:37PM +1200, Dr David Hingston wrote: : So if we want to limit the update to 4.5 stable and not 4.6-RC how do we do : that? 4.6-RC *is* 4-STABLE. If you don't want to go beyond 4.5-STABLE, stop updating. -- Christopher Vance To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 0:11:24 2002 Delivered-To: freebsd-stable@freebsd.org Received: from deborah.paradise.net.nz (deborah.paradise.net.nz [203.96.152.32]) by hub.freebsd.org (Postfix) with ESMTP id AAAAD37B401 for ; Tue, 28 May 2002 00:11:19 -0700 (PDT) Received: from P1200N (203-79-82-182.adsl-wns.paradise.net.nz [203.79.82.182]) by deborah.paradise.net.nz (Postfix) with SMTP id 33DCFD2153; Tue, 28 May 2002 19:11:16 +1200 (NZST) Message-ID: <01bd01c20616$b7cc6c70$0900a8c0@P1200N> From: "Dr David Hingston" To: "Christopher Vance" Cc: References: <20020528022359.GG93060@leviathan.inethouston.net> <200205280246.g4S2k02E074321@intruder.bmah.org> <018d01c20614$884a2bb0$0900a8c0@P1200N> <20020528170415.B2433@aurema.com> Subject: Re: Clarification using cvsup-> 4.x-stable Date: Tue, 28 May 2002 19:10:15 +1200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am looking to update to 4.5 also, being currently only on 4.0 (stable)....so that is not quite useful for me. David ----- Original Message ----- From: "Christopher Vance" To: "Dr David Hingston" Cc: Sent: Tuesday, May 28, 2002 7:04 PM Subject: Re: Clarification using cvsup-> 4.x-stable > On Tue, May 28, 2002 at 06:54:37PM +1200, Dr David Hingston wrote: > : So if we want to limit the update to 4.5 stable and not 4.6-RC how do we do > : that? > > 4.6-RC *is* 4-STABLE. > > If you don't want to go beyond 4.5-STABLE, stop updating. > > -- > Christopher Vance > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 0:12:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from fed1mtao01.cox.net (fed1mtao01.cox.net [68.6.19.244]) by hub.freebsd.org (Postfix) with ESMTP id AEBA537B403 for ; Tue, 28 May 2002 00:12:20 -0700 (PDT) Received: from ip24_56_31_67.ph.cox.net ([24.56.31.67]) by fed1mtao01.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with ESMTP id <20020528071210.RJZX25007.fed1mtao01.cox.net@ip24_56_31_67.ph.cox.net> for ; Tue, 28 May 2002 03:12:10 -0400 Content-Type: text/plain; charset="iso-8859-1" From: Brett Rogers Reply-To: loki_bsd@cox.net To: freebsd-stable@FreeBSD.org Subject: Re: Clarification using cvsup-> 4.x-stable Date: Tue, 28 May 2002 00:12:18 -0700 X-Mailer: KMail [version 1.4] References: <200205280246.g4S2k02E074321@intruder.bmah.org> <018d01c20614$884a2bb0$0900a8c0@P1200N> In-Reply-To: <018d01c20614$884a2bb0$0900a8c0@P1200N> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200205280012.18904.loki_bsd@cox.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wouldn't changing the tag to: *default release=3Dcvs tag=3DRELENG_4_5 work? > Kewl > So if we want to limit the update to 4.5 stable and not 4.6-RC how do w= e do > that? > With thanks in advance > David Hingston > > ----- Original Message ----- > From: "Bruce A. Mah" > To: "David W. Chapman Jr." > Cc: "Doug Silver" ; > Sent: Tuesday, May 28, 2002 2:46 PM > Subject: Re: Clarification using cvsup-> 4.x-stable > > > If memory serves me right, "David W. Chapman Jr." wrote: > > > On Mon, May 27, 2002 at 07:19:33PM -0700, Doug Silver wrote: > > > > I just want to make sure the sources I just got are correct as > > originally > > > > > I wanted to get 4.5-stable, so I put this in my cvsup file: > > > > > > > > *default release=3Dcvs tag=3DRELENG_4 > > > > > > > > did the buildworld/buildkernel fine, but upon reboot I see this: > > > > > > > > # uname -rs > > > > FreeBSD 4.6-RC > > > > > > 4.6-RC is the -stable branch during a certain period of time > > > preceding 4.6-STABLE > > > > > > I think its documented somewhere, but we really need to make it > > > readily available because this question is asked quite often. Does > > > anyone know a url that describes this? > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/admin.html#RELEASE= -CAN >D IDATE > > > Bruce. > _______________________________________________ > Freebsd-stable mailing list > Freebsd-stable@spitfire.velocet.net > http://spitfire.velocet.net/mailman/listinfo/freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 0:19:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from omen.e-lated.org (omen.e-lated.org [63.231.29.50]) by hub.freebsd.org (Postfix) with ESMTP id 2ED2837B405 for ; Tue, 28 May 2002 00:19:51 -0700 (PDT) Received: from e-lated.org (danger@sttlnas64poolB145.sttl.uswest.net [63.228.105.145]) by omen.e-lated.org (8.11.6/8.11.6) with ESMTP id g4S7ITh00283 for ; Tue, 28 May 2002 00:18:29 -0700 (PDT) (envelope-from danger@e-lated.org) Message-ID: <3CF32F99.8030205@e-lated.org> Date: Tue, 28 May 2002 00:19:53 -0700 From: Jeff Seeman User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.0rc2) Gecko/20020522 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: ASUS p4s533 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hiya, Ok I got this newest MoBo from ASUS P4S533 and freebsd 4.x works quite well, however there is a new southbridge chip SIS 961B that freebsd recognizes the ata controller as: atapci0: port 0xd800-0xd80f at device 2.5 on pci0 thios is really a ATA133. Any help would be great Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 0:20:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 9064337B404 for ; Tue, 28 May 2002 00:20:24 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g4S7JZB57058; Tue, 28 May 2002 10:19:35 +0300 (EEST) (envelope-from ru) Date: Tue, 28 May 2002 10:19:35 +0300 From: Ruslan Ermilov To: Mattias Bj?rk Cc: stable@FreeBSD.ORG Subject: Re: Problems when runing make installworld. Message-ID: <20020528071935.GD53736@sunbay.com> References: <20020527203834.G11844-200000@thrawn.birch.se> <20020527224930.K18138-200000@thrawn.birch.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="llIrKcgUOe3dCx0c" Content-Disposition: inline In-Reply-To: <20020527224930.K18138-200000@thrawn.birch.se> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --llIrKcgUOe3dCx0c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This is a known issue, for which there's no a quick solution. Please see PR 30276 for details. On Mon, May 27, 2002 at 10:52:23PM +0200, Mattias Bj?rk wrote: > On Mon, 27 May 2002, Mattias Bj?rk wrote: >=20 > > Hi, > > > > I have one dual celeron 400 MHz that i runed a make buildworld. And the= n i > > export /usr/src and /usr/obj with nfs to my box that I world like to > > upgrade. Its an p90 laptop, so that is why Im doing the build on my dual > > 400. :) > > > > Any way when I run make installworld on the laptop, I get goes for about > > 30 sec to one minute and then /usr/bin/install crashes with this error > > message: > > > > mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p > > /usr/include > > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h > > /usr/include/cam > > Illegal instruction - core dumped > > *** Error code 132 > > > > Stop in /usr/src/include. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > > > Any clues? I have attched the hole make installworld log. It seems that > > there is something wrong with my install file or? I copyied it from > > another machine that is a p120, but that did not help. Same problem, fi= rst > > I thought that It hade something to do with that I was runing make > > installworld in multiuser mode. But i rebooted and runed it with boot -s > > but that did not help either. > > > > Any clues/tips/flames welcome, as you can see it is no fun at all (TM) = to > > run a make world on a p90. I have done it before and it worked but i > > rather not do that... :) > > > > Perhaps you need more info, then do not hasitate to ask for it. Might t= ake > > some time to answer this mail because I have some mails to catch up in > > my mbox... > > > > Sorry if i typ to mutch... I will do better next time... > > > > Mvh Mattias Bj?rk > > > > Real Programmers don't write in PL/I. PL/I is for programmers who > > can't decide whether to write in COBOL or FORTRAN. > > > Script started on Mon May 27 22:36:18 2002 > # make installworld=0D > mkdir -p /tmp/install.2474=0D > for prog in [ awk cat chflags chmod chown date echo egrep find grep ln m= ake makewhatis mtree mv perl rm sed sh sysctl test true uname wc zic; do = cp `which $prog` /tmp/install.2474; done=0D > cd /usr/src; MAKEOBJDIRPREFIX=3D/usr/obj MACHINE_ARCH=3Di386 MACHINE=3D= i386 OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec PERL5LIB=3D/usr/o= bj/usr/src/i386/usr/libdata/perl/5.00503 GROFF_BIN_PATH=3D/usr/obj/usr/src= /i386/usr/bin GROFF_FONT_PATH=3D/usr/obj/usr/src/i386/usr/share/groff_font= GROFF_TMAC_PATH=3D/usr/obj/usr/src/i386/usr/share/tmac PATH=3D/usr/obj/u= sr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/us= r/games:/tmp/install.2474 make -f Makefile.inc1 reinstall=0D > --------------------------------------------------------------=0D > >>> Making hierarchy=0D > --------------------------------------------------------------=0D > cd /usr/src; make -f Makefile.inc1 hierarchy=0D > cd /usr/src/etc; make distrib-dirs=0D > set - `grep "^[a-zA-Z]" /usr/src/etc/locale.deprecated`; while [ $# -gt = 0 ] ; do for dir in /usr/share/locale /usr/share/nls /usr/local/share/n= ls; do test -d /${dir} && cd /${dir}; test -L "$2" && rm -rf "$2"; test= \! -L "$1" && test -d "$1" && mv "$1" "$2"; done; shift; shift; done=0D > mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p /=0D > mtree -deU -f /usr/src/etc/mtree/BSD.var.dist -p /var=0D > mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr=0D > mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include=0D > mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/libdata/perl/5= .00503/mach=0D > cd /; rm -f /sys; ln -s usr/src/sys sys=0D > cd /usr/share/man/en.ISO8859-1; ln -sf ../man* .=0D > cd /usr/share/man; set - `grep "^[a-zA-Z]" /usr/src/etc/man.alias`; whi= le [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done= =0D > cd /usr/share/locale; set - `grep "^[a-zA-Z]" /usr/src/etc/locale.alias`= ; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; = done=0D > cd /usr/share/nls; set - `grep "^[a-zA-Z]" /usr/src/etc/nls.alias`; whi= le [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; done= =0D > =0D > --------------------------------------------------------------=0D > >>> Installing everything..=0D > --------------------------------------------------------------=0D > cd /usr/src; make -f Makefile.inc1 install=0D > =3D=3D=3D> share/info=0D > =3D=3D=3D> include=0D > if [ -h /usr/include/cam ]; then rm -f /usr/include/cam; fi=0D > if [ -h /usr/include/msdosfs ]; then rm -f /usr/include/msdosfs; fi=0D > if [ -h /usr/include/net ]; then rm -f /usr/include/net; fi=0D > if [ -h /usr/include/netatalk ]; then rm -f /usr/include/netatalk; fi=0D > if [ -h /usr/include/netatm ]; then rm -f /usr/include/netatm; fi=0D > if [ -h /usr/include/netgraph ]; then rm -f /usr/include/netgraph; fi=0D > if [ -h /usr/include/netinet ]; then rm -f /usr/include/netinet; fi=0D > if [ -h /usr/include/netinet6 ]; then rm -f /usr/include/netinet6; fi=0D > if [ -h /usr/include/netipx ]; then rm -f /usr/include/netipx; fi=0D > if [ -h /usr/include/netkey ]; then rm -f /usr/include/netkey; fi=0D > if [ -h /usr/include/netnatm ]; then rm -f /usr/include/netnatm; fi=0D > if [ -h /usr/include/netncp ]; then rm -f /usr/include/netncp; fi=0D > if [ -h /usr/include/netns ]; then rm -f /usr/include/netns; fi=0D > if [ -h /usr/include/netsmb ]; then rm -f /usr/include/netsmb; fi=0D > if [ -h /usr/include/nfs ]; then rm -f /usr/include/nfs; fi=0D > if [ -h /usr/include/ntfs ]; then rm -f /usr/include/ntfs; fi=0D > if [ -h /usr/include/nwfs ]; then rm -f /usr/include/nwfs; fi=0D > if [ -h /usr/include/pccard ]; then rm -f /usr/include/pccard; fi=0D > if [ -h /usr/include/posix4 ]; then rm -f /usr/include/posix4; fi=0D > if [ -h /usr/include/sys ]; then rm -f /usr/include/sys; fi=0D > if [ -h /usr/include/vm ]; then rm -f /usr/include/vm; fi=0D > if [ -h /usr/include/fs/smbfs ]; then rm -f /usr/include/fs/smbfs; fi=0D > if [ -h /usr/include/isofs/cd9660 ]; then rm -f /usr/include/isofs/cd966= 0; fi=0D > if [ -h /usr/include/ufs/ffs ]; then rm -f /usr/include/ufs/ffs; fi=0D > if [ -h /usr/include/ufs/mfs ]; then rm -f /usr/include/ufs/mfs; fi=0D > if [ -h /usr/include/ufs/ufs ]; then rm -f /usr/include/ufs/ufs; fi=0D > if [ -h /usr/include/dev/ppbus ]; then rm -f /usr/include/dev/ppbus; fi= =0D > if [ -h /usr/include/dev/usb ]; then rm -f /usr/include/dev/usb; fi=0D > if [ -h /usr/include/machine ]; then rm -f /usr/include/machine; fi=0D > mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p /usr/inc= lude=0D > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h = /usr/include/cam=0D > Illegal instruction - core dumped=0D > *** Error code 132=0D > =0D > Stop in /usr/src/include.=0D > *** Error code 1=0D > =0D > Stop in /usr/src.=0D > *** Error code 1=0D > =0D > Stop in /usr/src.=0D > *** Error code 1=0D > =0D > Stop in /usr/src.=0D > *** Error code 1=0D > =0D > Stop in /usr/src.=0D > # d=08 =08 --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --llIrKcgUOe3dCx0c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE88y+HUkv4P6juNwoRAo9rAJ9rj6800j4vFsGYRqc2KCLKSw0u6QCeOLZw uwFoo9YOS37zhZVHJywQcDc= =r/Hm -----END PGP SIGNATURE----- --llIrKcgUOe3dCx0c-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 0:26:49 2002 Delivered-To: freebsd-stable@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id D938237B404; Tue, 28 May 2002 00:26:43 -0700 (PDT) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id 036AB62D1A; Tue, 28 May 2002 00:26:42 -0700 (PDT) Date: Tue, 28 May 2002 00:30:35 -0700 (PDT) From: Lamont Granquist To: Greg 'groggy' Lehey Cc: Cy Schubert - CITS Open Systems Group , Kirk Strauser , Subject: Re: Hardware RAID vs vinum In-Reply-To: <20020528095948.D16567@wantadilla.lemis.com> Message-ID: <20020528002940.G449-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 28 May 2002, Greg 'groggy' Lehey wrote: > On Monday, 27 May 2002 at 6:02:23 -0700, Cy Schubert - CITS Open Systems Group wrote: > > > > It turned out that moving the application to hardware RAID improved > > performance by 40 times. > > This can only happen if there's something very wrong with the software > RAID-5, either the implementation or the configuration. My first thought was cache on the hardware RAID array. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 0:31:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id D26C037B40A for ; Tue, 28 May 2002 00:31:27 -0700 (PDT) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 6660D814A1; Tue, 28 May 2002 17:01:25 +0930 (CST) Date: Tue, 28 May 2002 17:01:25 +0930 From: Greg 'groggy' Lehey To: Lamont Granquist Cc: Cy Schubert - CITS Open Systems Group , Kirk Strauser , freebsd-stable@FreeBSD.ORG Subject: Re: Hardware RAID vs vinum Message-ID: <20020528170125.S16567@wantadilla.lemis.com> References: <20020528095948.D16567@wantadilla.lemis.com> <20020528002940.G449-100000@coredump.scriptkiddie.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020528002940.G449-100000@coredump.scriptkiddie.org> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tuesday, 28 May 2002 at 0:30:35 -0700, Lamont Granquist wrote: > > > On Tue, 28 May 2002, Greg 'groggy' Lehey wrote: >> On Monday, 27 May 2002 at 6:02:23 -0700, Cy Schubert - CITS Open Systems Group wrote: >>> >>> It turned out that moving the application to hardware RAID improved >>> performance by 40 times. >> >> This can only happen if there's something very wrong with the software >> RAID-5, either the implementation or the configuration. > > My first thought was cache on the hardware RAID array. Mine too. But that wouldn't normally give that much of on improvement. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 0:43:20 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mta02bw.bigpond.com (mta02bw.bigpond.com [139.134.6.34]) by hub.freebsd.org (Postfix) with ESMTP id 5876937B405 for ; Tue, 28 May 2002 00:43:06 -0700 (PDT) Received: from areilly.bpc-users.org ([144.135.24.69]) by mta02bw.bigpond.com (Netscape Messaging Server 4.15 mta02bw Apr 29 2002 13:22:02) with SMTP id GWT9FN00.IM1 for ; Tue, 28 May 2002 17:42:59 +1000 Received: from CPE-144-132-243-222.nsw.bigpond.net.au ([144.132.243.222]) by bwmam01.mailsvc.email.bigpond.com(MailRouter V3.0m 2/15862280); 28 May 2002 17:42:55 Received: (qmail 4950 invoked from network); 28 May 2002 07:42:55 -0000 Received: from localhost (andrew@127.0.0.1) by localhost with SMTP; 28 May 2002 07:42:55 -0000 Subject: Re: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) From: Andrew Reilly To: jos@catnook.com Cc: stable@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: <20020528010708.GB5934@lizzy.catnook.com> References: <20020527215031.GA5934@lizzy.catnook.com> <200205272342.DAA22488@aaz.links.ru> <20020528010708.GB5934@lizzy.catnook.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 28 May 2002 17:42:54 +1000 Message-Id: <1022571775.692.45.camel@gurney.reilly.home> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just fwiw (probably nothing), I'd like to express a strong "yes please" vote for a move in this direction. I currently use djb's daemontools to manage qmail and dnsserver+tinydns, and am pretty sure that I'm going to migrate the rest of my /usr/local/etc/rc.d services under there too, now that I have a reasonable understanding of how it works. None of these run as root, so .pid files wouldn't work well anyway. About the only thing that daemontools doesn't offer in this regard is the sort of dependency-directed start order being discussed for the new /etc/rc.d (and present in NetBSD). I'm not sure what to make of that. I suspect that djb just expects services that depend on other services to wait around until the other service is running (perhaps by exiting so that the service manager can start it again five seconds later). I'm not sure that I can see a problem with that, frankly: not being able to cope with unresponsiveness of some other service implies fragility in the face of restarting or failure of that other service. Maybe there are races or deadlocks that way? -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 1:34:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 8B84837B404 for ; Tue, 28 May 2002 01:34:15 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by cain.gsoft.com.au (8.12.2/8.12.2) with ESMTP id g4S8YBBh041952 for ; Tue, 28 May 2002 18:04:11 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Problems with PC-Partner motherboards? From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 28 May 2002 18:04:10 +0930 Message-Id: <1022574851.38850.59.camel@chowder.gsoft.com.au> Mime-Version: 1.0 X-Spam-Status: No, hits=0 required=5 X-Spam-Level: (0) X-Scanned-By: MIMEDefang 2.6 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Does anyone have a PC Partner K133AASA-220B ? If so, do they have either the latest BIOS update, or a version of FreeBSD with the VIA Southbridge fix? If yes, then do you notice it lock up? :) I have had several of these and they lock up hard (can't break in via the debugger) after working hard (running as a radar system, md5'ing files, and buildworlding repeatedly) If I use the older BIOS and a version of FreeBSD without the southbridge fix it doesn't appear to hang... Unfortunately the older BIOS doesn't support Athlon XP CPUs, and without the fix I get data corruption. Anyone have any input? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 2: 3: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by hub.freebsd.org (Postfix) with SMTP id 3CD9D37B408 for ; Tue, 28 May 2002 02:02:58 -0700 (PDT) Received: from unknown (HELO johncoop.MSHOME) (john?m?cooper@206.63.201.3 with plain) by smtp.mail.vip.sc5.yahoo.com with SMTP; 28 May 2002 09:02:57 -0000 Subject: Re: Problems with PC-Partner motherboards? From: John Merryweather Cooper Reply-To: john_m_cooper@yahoo.com To: Daniel O'Connor Cc: FreeBSD Stable In-Reply-To: <1022574851.38850.59.camel@chowder.gsoft.com.au> References: <1022574851.38850.59.camel@chowder.gsoft.com.au> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 28 May 2002 02:03:40 -0700 Message-Id: <1022576621.1708.14.camel@johncoop.MSHOME> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2002-05-28 at 01:34, Daniel O'Connor wrote: > Does anyone have a PC Partner K133AASA-220B ? > No, but my DFI AK74-EC board (which is a VIA KT133A motherboard) with an AMD Duron 1300 has been locking up like clockwork right around midnight. I thought this was amanda related (I've just finished installing a dedicated dump disk), but I stayed up tonight to watch things and it actually locks up without amanda doing anything (just running Evolution and looking at my mail while waiting for amanda to start on schedule and the mouse cursor froze--along with the rest of the system). After rebooting, amanda ran fine to completion. Amanda appears to work the system pretty hard as the CPU spikes up about 20 deg. C (from 65 deg. C to 85 deg. C--still within the operating limits of 90 deg. C from the documentation--but a tad toasty). After amanda completed (takes about 2 hours on my system to back up a 60 Gig set of partitions), the CPU temperature settles down again. As you've observed, the freeze is "hard"--getting in with a debugger appears futile and I need to hit the reset switch to get things moving again--CTRL-ALT-DEL has no effect. I'm also wondering if this has anything to do with the tagged queing going south early in 4.5-STABLE (the tagged sysctl is currently disabled in my loader.conf with a comment). No real reason to think so, just a generalized feeling that all is not quite right. > If so, do they have either the latest BIOS update, or a version of > FreeBSD with the VIA Southbridge fix? > > If yes, then do you notice it lock up? :) > > I have had several of these and they lock up hard (can't break in via > the debugger) after working hard (running as a radar system, md5'ing > files, and buildworlding repeatedly) > > If I use the older BIOS and a version of FreeBSD without the southbridge > fix it doesn't appear to hang... Unfortunately the older BIOS doesn't > support Athlon XP CPUs, and without the fix I get data corruption. > > Anyone have any input? > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5 -- _ | |V| / ' || MacroHard -- \ \_| | | \_, || the perfection of form over | ----------------------------------|| substance, marketing over | Web: http://www.borgsdemons.com || performance, and greed over | AIM: johnmcooper || design . . . | =====================================================================/ Public Key: http://www.borgsdemons.com/Personal/pgpkey.asc | =====================================================================\ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 4:37:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from moutvdom01.kundenserver.de (moutvdom01.kundenserver.de [195.20.224.200]) by hub.freebsd.org (Postfix) with ESMTP id B441137B40C for ; Tue, 28 May 2002 04:37:22 -0700 (PDT) Received: from [195.20.224.219] (helo=mrvdom03.kundenserver.de) by moutvdom01.kundenserver.de with esmtp (Exim 2.12 #3) id 17CfHz-0002kB-00 for freebsd-stable@freebsd.org; Tue, 28 May 2002 13:37:19 +0200 Received: from pd9011289.dip0.t-ipconnect.de ([217.1.18.137] helo=encephalon.de) by mrvdom03.kundenserver.de with esmtp (Exim 2.12 #3) id 17CfHy-0000Eb-00 for freebsd-stable@freebsd.org; Tue, 28 May 2002 13:37:19 +0200 Received: from chuckie.encephalon.de (localhost.encephalon.de [127.0.0.1]) by encephalon.de (8.12.3/8.11.6) with ESMTP id g4SBcoRY005785 for ; Tue, 28 May 2002 13:38:50 +0200 (CEST) (envelope-from plankalkuel@chuckie.encephalon.de) Received: (from plankalkuel@localhost) by chuckie.encephalon.de (8.12.3/8.12.3/Submit) id g4SBcmdI005784 for freebsd-stable@freebsd.org; Tue, 28 May 2002 13:38:48 +0200 (CEST) (envelope-from plankalkuel) Date: Tue, 28 May 2002 13:38:48 +0200 From: "a.s.gruner" To: freebsd-stable@freebsd.org Subject: atacontrol or sysctl ? who is the liar ? Message-ID: <20020528133847.A5745@encephalon.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Operating-System: FreeBSD 4.6-RC i386 X-Editor: vi Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi. I have a question about atacontrol and sysctl. I thought the write cache on my harddrives is off. sysctl hw.ata.wc tells me hw.ata.wc=0 So, write cache is disabled, i thought... But, if i check my first HD on the first IDE with the tool atacontrol (atacontrol cap 0 0), i will get a different message to that above with sysctl: Feature Support Enable write cache yes yes ... The harddrive is a old 9 GB Maxtor one: 91021U2 Firmware: FA520S60 So, how could this be ? Sysctl tells me write cache is off, atacontrol tells me it is on (first HD on first IDE). I habe switched write cache off in /boot/loader.conf. Could it be that the Maxtor HD has write cache enabled the whole time, and give a sh.. of trying to turning that off ? Thanks for information. asg P.S.: I dont have any problems, i am just wondering... -- Woher soll ich wissen was ich denke wo ich noch nichteinmal gehoert habe was ich sagte ? ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 6:55:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mile.nevermind.kiev.ua (office.netstyle.com.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id 9F15937B405 for ; Tue, 28 May 2002 06:55:42 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.3/8.12.3) with ESMTP id g4SDtRjj017629; Tue, 28 May 2002 16:55:27 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.3/8.12.3/Submit) id g4SDtQTb017623; Tue, 28 May 2002 16:55:26 +0300 (EEST) Date: Tue, 28 May 2002 16:55:25 +0300 From: Alexandr Kovalenko To: Brett Rogers Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Clarification using cvsup-> 4.x-stable Message-ID: <20020528135525.GA8056@nevermind.kiev.ua> References: <200205280246.g4S2k02E074321@intruder.bmah.org> <018d01c20614$884a2bb0$0900a8c0@P1200N> <200205280012.18904.loki_bsd@cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <200205280012.18904.loki_bsd@cox.net> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Brett Rogers! On Tue, May 28, 2002 at 12:12:18AM -0700, you wrote: > Wouldn't changing the tag to: > *default release=cvs tag=RELENG_4_5 > work? RELENG_4_5 is security branch which is 4.5-RELEASE (which is older than 4.5-STABLE) + security fixes. > > Kewl > > So if we want to limit the update to 4.5 stable and not 4.6-RC how do we do > > that? > > With thanks in advance -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 6:56:47 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mile.nevermind.kiev.ua (office.netstyle.com.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id B4ED337B401 for ; Tue, 28 May 2002 06:56:39 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.3/8.12.3) with ESMTP id g4SDuAjj017944; Tue, 28 May 2002 16:56:10 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.3/8.12.3/Submit) id g4SDu8ST017928; Tue, 28 May 2002 16:56:08 +0300 (EEST) Date: Tue, 28 May 2002 16:56:08 +0300 From: Alexandr Kovalenko To: Dr David Hingston Cc: Christopher Vance , stable@FreeBSD.ORG Subject: Re: Clarification using cvsup-> 4.x-stable Message-ID: <20020528135608.GB8056@nevermind.kiev.ua> References: <20020528022359.GG93060@leviathan.inethouston.net> <200205280246.g4S2k02E074321@intruder.bmah.org> <018d01c20614$884a2bb0$0900a8c0@P1200N> <20020528170415.B2433@aurema.com> <01bd01c20616$b7cc6c70$0900a8c0@P1200N> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <01bd01c20616$b7cc6c70$0900a8c0@P1200N> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Dr David Hingston! On Tue, May 28, 2002 at 07:10:15PM +1200, you wrote: > I am looking to update to 4.5 also, being currently only on 4.0 > (stable)....so that is not quite useful for me. 4.6-RC is 4.5-STABLE with different name. > > On Tue, May 28, 2002 at 06:54:37PM +1200, Dr David Hingston wrote: > > : So if we want to limit the update to 4.5 stable and not 4.6-RC how do we > do > > : that? > > > > 4.6-RC *is* 4-STABLE. > > > > If you don't want to go beyond 4.5-STABLE, stop updating. -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 7: 2:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mile.nevermind.kiev.ua (office.netstyle.com.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id 6F70937B404 for ; Tue, 28 May 2002 07:02:22 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.3/8.12.3) with ESMTP id g4SE22jj020768; Tue, 28 May 2002 17:02:02 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.3/8.12.3/Submit) id g4SE20t6020757; Tue, 28 May 2002 17:02:00 +0300 (EEST) Date: Tue, 28 May 2002 17:02:00 +0300 From: Alexandr Kovalenko To: Jeff Seeman Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ASUS p4s533 Message-ID: <20020528140159.GC8056@nevermind.kiev.ua> References: <3CF32F99.8030205@e-lated.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <3CF32F99.8030205@e-lated.org> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Jeff Seeman! On Tue, May 28, 2002 at 12:19:53AM -0700, you wrote: > Hiya, Ok I got this newest MoBo from ASUS P4S533 and freebsd 4.x works > quite well, however there is a new southbridge chip SIS 961B that > freebsd recognizes the ata controller as: > > atapci0: port 0xd800-0xd80f at device 2.5 on > pci0 > > thios is really a ATA133. > > Any help would be great In code it looks like if it is SiS 5591 and not ATA100 and not ATA66, it is ATA33. snippet of code from /sys/dev/ata/ata-pci.c: case 0x55131039: if (ata_find_dev(dev, 0x06301039, 0x30) || ata_find_dev(dev, 0x06331039, 0) || ata_find_dev(dev, 0x06351039, 0) || ata_find_dev(dev, 0x06401039, 0) || ata_find_dev(dev, 0x06451039, 0) || ata_find_dev(dev, 0x06501039, 0) || ata_find_dev(dev, 0x07301039, 0) || ata_find_dev(dev, 0x07331039, 0) || ata_find_dev(dev, 0x07351039, 0) || ata_find_dev(dev, 0x07401039, 0) || ata_find_dev(dev, 0x07451039, 0) || ata_find_dev(dev, 0x07501039, 0)) return "SiS 5591 ATA100 controller"; else if (ata_find_dev(dev, 0x05301039, 0) || ata_find_dev(dev, 0x05401039, 0) || ata_find_dev(dev, 0x06201039, 0) || ata_find_dev(dev, 0x06301039, 0)) return "SiS 5591 ATA66 controller"; else return "SiS 5591 ATA33 controller"; -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 7:14:37 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail19b.rapidsite.net (mail19b.rapidsite.net [161.58.134.134]) by hub.freebsd.org (Postfix) with SMTP id C9F0337B403 for ; Tue, 28 May 2002 07:14:31 -0700 (PDT) Received: from www.pythonemproject.com (198.104.176.109) by mail19b.rapidsite.net (RS ver 1.0.63s) with SMTP id 034496966 for ; Tue, 28 May 2002 10:20:59 -0400 (EDT) Message-ID: <3CF3905A.76098B89@pythonemproject.com> Date: Tue, 28 May 2002 07:12:42 -0700 From: rob X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: "stable@freebsd.org" Subject: Re: Clarification using cvsup-> 4.x-stable References: <20020528022359.GG93060@leviathan.inethouston.net> <20020528113949W.matusita@jp.FreeBSD.org> <20020528024235.GJ93060@leviathan.inethouston.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Loop-Detect: 1 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "David W. Chapman Jr." wrote: > > On Tue, May 28, 2002 at 11:39:49AM +0900, Makoto Matsushita wrote: > > > > dwcjr> I think its documented somewhere, but we really need to make it > > dwcjr> readily available because this question is asked quite often. > > dwcjr> Does anyone know a url that describes this? > > > > > > Thanks! I knew we must have had something somewhere, should we stick > it on the handbook under the cvsup section as a note? > > -- > David W. Chapman Jr. > dwcjr@inethouston.net Raintree Network Services, Inc. > dwcjr@freebsd.org FreeBSD Committer > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message Maybe it could be added to motd :) Rob. -- ----------------------------- The Numeric Python EM Project www.pythonemproject.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 9:50:36 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.flipdog.com (sundog.flipdog.com [63.173.191.2]) by hub.freebsd.org (Postfix) with ESMTP id 060AF37B403 for ; Tue, 28 May 2002 09:50:26 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.flipdog.com (Postfix) with ESMTP id 8DC37AC44F; Tue, 28 May 2002 10:50:20 -0600 (MDT) X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 From: "Jan L. Peterson" To: "Phil Rosenthal" Cc: freebsd-stable@freebsd.org Subject: Re: Hardware RAID vs vinum X-face: p=61=y<.Il$z+k*y~"j>%c[8R~8{j3WTnaSd-'RyC>t.Ub>AAm\zYA#5JF +W=G?EI+|EI);]=fs_MOfKN0n9`OlmB[1^0;L^64K5][nOb&gv/n}p@mm06|J|WNa asp7mMEw0w)e_6T~7v-\]yHKvI^1}[2k)] References: <004701c20530$68e98a20$0700a8c0@zoom> In-reply-to: Your message of "Sun, 26 May 2002 23:41:39 EDT." <004701c20530$68e98a20$0700a8c0@zoom> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 28 May 2002 10:50:20 -0600 Message-Id: <20020528165020.8DC37AC44F@mail.flipdog.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My experience may be contrary to others. My particular application got much much better performance with software RAID (vinum) than with hardware RAID (HP 3-Si card a.k.a. AMI MegaRAID). The application in question had about 16 Windows boxes accessing an SMB filesystem (Samba on the FBSD box). These clients would be all over the disk, accessing hundreds or thousands of different files at different locations on the filesystem every second. Mostly reading, but some writing as well. I got excellent performance out of the hardware raid with only about three or four clients running, but when all sixteen were pounding on the disk, throughput (measured with iostat/systat) was abysmal. Moving the disks to a Symetrics controller and vinum resulted in at least tripple the performance. I accredited it to the fact that the hardware controller had a small cache (32M) vs. the system main memory (1G), and that the system could better schedule reads and writes as it knew more about where the data was on the various disks. I guess what I'm saying is don't simply assume that hardware RAID is good or bad... it's very dependent on your application. We are very satisfied with the hardware RAID on a different box with different usage patterns. -jan- -- Jan L. Peterson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 10:23:13 2002 Delivered-To: freebsd-stable@freebsd.org Received: from relay.cigital.com (relay.cigital.com [64.80.176.5]) by hub.freebsd.org (Postfix) with ESMTP id 1AFA237B404; Tue, 28 May 2002 10:22:42 -0700 (PDT) Received: from exchange.cigital.com (exchange.cigital.com [10.1.20.3]) by relay.cigital.com (Postfix) with ESMTP id C6974BA44; Tue, 28 May 2002 13:22:40 -0400 (EDT) Received: by exchange.cigital.com with Internet Mail Service (5.5.2653.19) id <2VH4GXYS>; Tue, 28 May 2002 13:15:21 -0400 Message-ID: <51CC94132526754995E79DCF28C0C34D09B8A9@exchange.cigital.com> From: Yanek Korff To: "'freebsd-stable@freebsd.org'" Cc: "'scottl@freebsd.org'" Subject: mkisofs ... for DVD Date: Tue, 28 May 2002 13:15:21 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm now the proud owner of a DVD burner which I hope to use to back up some filesystems. Especially useful would be to create filesystem images, FTP them to the machine in which the DVD burner is located & burn (Using Roxio Easy CD Creator or NeoDVD). Been looking at UDF -- is this what I should be using? I don't need to mount or read DVD's, just create filesystem images that the aforementioned programs can BURN. Any info would be greatly appreciated. -Yanek. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 10:47: 5 2002 Delivered-To: freebsd-stable@freebsd.org Received: from w250.z064001178.sjc-ca.dsl.cnc.net (adsl-66.218.45.239.dslextreme.com [66.218.45.239]) by hub.freebsd.org (Postfix) with SMTP id 9818E37B40A for ; Tue, 28 May 2002 10:46:32 -0700 (PDT) Received: (qmail 19075 invoked by uid 1000); 28 May 2002 17:46:53 -0000 Date: Tue, 28 May 2002 10:46:31 -0700 From: Jos Backus To: stable@FreeBSD.ORG, hackers@FreeBSD.ORG Cc: Manoj Kasichainula Subject: Re: non-root /var/run files (was Re: Sendmail, smmsp, and pid file) Message-ID: <20020528174653.GC11876@lizzy.catnook.com> Reply-To: jos@catnook.com Mail-Followup-To: stable@FreeBSD.ORG, hackers@FreeBSD.ORG, Manoj Kasichainula References: <20020527215031.GA5934@lizzy.catnook.com> <200205272342.DAA22488@aaz.links.ru> <20020528010708.GB5934@lizzy.catnook.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <20020528010708.GB5934@lizzy.catnook.com> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, May 28, 2002 at 03:42:31AM +0400, "."@babolo.ru wrote: > Begin with port. Please find attached a port skeleton for mktool 0.0.7. Perhaps we can suggest a more descriptive name to the author (cc'ed)? Feedback welcome. -- Jos Backus _/ _/_/_/ Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos@catnook.com _/_/ _/_/_/ use Std::Disclaimer; --oyUTqETQ0mS9luUI Content-Type: application/x-shar Content-Disposition: attachment; filename="mktool.shar" Content-Transfer-Encoding: quoted-printable # This is a shell archive. Save it in a file, remove anything before=0A# t= his line, and then unpack it by entering "sh file". Note, it may=0A# creat= e directories; files and directories will be owned by you and=0A# have defa= ult permissions.=0A#=0A# This archive contains:=0A#=0A# mktool=0A# mktool/d= istinfo=0A# mktool/Makefile=0A# mktool/pkg-comment=0A# mktool/pkg-descr=0A#= mktool/pkg-plist=0A#=0Aecho c - mktool=0Amkdir -p mktool > /dev/null 2>&1= =0Aecho x - mktool/distinfo=0Ased 's/^X//' >mktool/distinfo << 'END-of-mkto= ol/distinfo'=0AXMD5 (mktool-0.0.7.tar.gz) =3D cb2d4c919dca5c0a9e4fbf1a1b91d= 736=0AEND-of-mktool/distinfo=0Aecho x - mktool/Makefile=0Ased 's/^X//' >mkt= ool/Makefile << 'END-of-mktool/Makefile'=0AX# ports collection makefile for= : mktool=0AX# Date created: 2002/05/28=0AX# = Whom: josb=0AX#=0AX# $FreeBSD$=0AX#=0AX=0AX= PORTNAME=3D mktool=0AXPORTVERSION=3D 0.0.7=0AXCATEGORIES=3D sysutils=0AXMAS= TER_SITES=3D http://www.io.com/~manoj/file/=0AX=0AXMAINTAINER=3D jos@catnoo= k.com=0AX=0AXWRKSRC=3D ${WRKDIR}/${PORTNAME}=0AX=0AXUSE_GMAKE=3D yes=0AXNO= MAN=3D true=0AX=0AXpost-extract:=0AX cd ${WRKSRC}; ${SED} -i ".orig" \=0AX= -e 's,^OPT=3D.*,OPT=3D${CFLAGS},' \=0AX -e 's,^bindir=3D.*,bindir=3D${PREF= IX}/bin,' \=0AX -e 's,cp -a,install -m ${BINMODE},' \=0AX Makefile=0AX=0AX.= include =0AEND-of-mktool/Makefile=0Aecho x - mktool/pkg-commen= t=0Ased 's/^X//' >mktool/pkg-comment << 'END-of-mktool/pkg-comment'=0AXSome= tools to manage processes and network services=0AEND-of-mktool/pkg-comment= =0Aecho x - mktool/pkg-descr=0Ased 's/^X//' >mktool/pkg-descr << 'END-of-mk= tool/pkg-descr'=0AXSome tools to manage processes and network services.=0AE= ND-of-mktool/pkg-descr=0Aecho x - mktool/pkg-plist=0Ased 's/^X//' >mktool/p= kg-plist << 'END-of-mktool/pkg-plist'=0AXbin/babysit=0AXbin/bsok=0AXbin/env= uidgid=0AXbin/execlp=0AXbin/setugid=0AXbin/tcpaccept=0AXbin/tcplisten=0AEND= -of-mktool/pkg-plist=0Aexit=0A=0A --oyUTqETQ0mS9luUI-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue May 28 11:16:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.inoc.net (mx1.inoc.net [64.246.131.30]) by hub.freebsd.org (Postfix) with ESMTP id 0468737BA59 for ; Tue, 28 May 2002 11:12:39 -0700 (PDT) Received: from nimbus (unverified [10.0.0.111]) by mx1.inoc.net (Vircom SMTPRS 5.2.204) with ESMTP id for ; Tue, 28 May 2002 14:12:24 -0400 From: "Robert Blayzor" To: Subject: Swap_pager error Date: Tue, 28 May 2002 14:12:23 -0400 Organization: INOC, LLC Message-ID: <008201c20673$37ac9c60$6f00000a@z0.inoc.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.3416 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG We have a Dell PowerEdge 2550 server. It's running FreeBSD4-stable (up'd just a couple of weeks ago). It's an SMP box, 1GB of RAM, two 3com Tigon2 Gigabit NIC cards and a PERC3/QC controller. We have two logical drives. One is a RAID1 set of two 9GB drives which holds the operating system only. The other is a 300GB RAID10 array. The box had been running fine for months when suddenly the box got hosed as we received tons of these errors on the console. (nothing logged to /var/log/messages) swap_pager: indefinite wait buffer: #amrd/0x20001, blkno:272, size:4096 The box only runs as an NFS/Samba server and nothing else. It eventually just became useless and we had to reset the box hard. We ran FSCK and it reported no errors and the box came up normally. We were considering running scanning on the OS disk containing the swap, but feel there really is no need to as the RAID controller is reporting no problems as well. Anyone have any suggestions on where to start looking for this problem? We've had this unit in service almost six months and this is the first time we've seen this. Is there a way to "test" swap space in production other than writing something to gobble up memory and forcing the box to swap? Kernel dmesg: Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-RELEASE-p4 #0: Mon Apr 22 21:37:02 EDT 2002 root@goliath:/usr/obj/src/sys/GOLIATH Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (997.46-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383fbff real memory = 1073676288 (1048512K bytes) avail memory = 1041707008 (1017292K bytes) Changing APIC ID for IO APIC #0 from 0 to 2 on chip Changing APIC ID for IO APIC #1 from 0 to 3 on chip Programming 16 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 16 pins in IOAPIC #1 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x000f0011, at 0xfec00000 io1 (APIC): apic id: 3, version: 0x000f0011, at 0xfec01000 Preloaded elf kernel "kernel" at 0xc0350000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 8 entries at 0xc00fc270 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard IOAPIC #1 intpin 6 -> irq 2 IOAPIC #1 intpin 2 -> irq 5 pci0: on pcib0 pcib2: at device 2.0 on pci0 IOAPIC #1 intpin 5 -> irq 10 pci1: on pcib2 pcib5: at device 0.0 on pci1 IOAPIC #1 intpin 4 -> irq 11 pci2: on pcib5 amr0: mem 0xf0000000-0xf7ffffff irq 11 at device 0.0 on pci2 amr0: Firmware 1.57, BIOS 3.13, 128MB RAM pci1: (vendor=0x1077, dev=0x1216) at 1.0 irq 10 pci1: (vendor=0x1077, dev=0x1216) at 2.0 irq 2 ti0: <3Com 3c985-SX Gigabit Ethernet> mem 0xfe404000-0xfe407fff irq 2 at device 4.0 on pci0 ti0: Ethernet address: 00:60:08:f6:f5:92 ti1: <3Com 3c985-SX Gigabit Ethernet> mem 0xfe400000-0xfe403fff irq 5 at device 8.0 on pci0 ti1: Ethernet address: 00:60:08:f6:f5:93 pci0: at 14.0 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x8b0-0x8bf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pcib4: on motherboard IOAPIC #1 intpin 0 -> irq 13 pci4: on pcib4 pcib6: at device 2.0 on pci4 IOAPIC #1 intpin 15 -> irq 16 IOAPIC #1 intpin 14 -> irq 17 pci5: on pcib6 ahc0: port 0xbc00-0xbcff mem 0xfe7ff000-0xfe7fffff irq 16 at device 4.0 on pci5 aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xb800-0xb8ff mem 0xfe7fe000-0xfe7fefff irq 17 at device 4.1 on pci5 aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/255 SCBs fxp0: port 0xacc0-0xacff mem 0xfe500000-0xfe5fffff,0xfe900000-0xfe900fff irq 13 at device 4.0 on pci4 fxp0: Ethernet address 00:06:5b:1a:5c:e9 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: on motherboard IOAPIC #1 intpin 1 -> irq 18 pci3: on pcib1 pci3: (vendor=0x14e4, dev=0x1644) at 8.0 irq 18 pcib3: on motherboard pci6: on pcib3 orm0:
Believe it! You have a secret admirer!

Just click to http://www.SomeoneLikesYou.com to find out who!

Email address: freebsd-stable@freebsd.org
Secret code: jeste2 (Note: This is NOT your password!)

See you soon!

Best wishes,

The SomeoneLikesYou Matchmaker



No Spam Policy:

Unlike some other sites, SomeoneLikesYou will never send you spam or junk email. You have received this notice at the request of someone you know who has told us they like you! If you would like to keep anyone from sending you such a notice, please go to http://www.SomeoneLikesYou.com/unsubscribe.html
--------------0AD116E438EE2EFDDFF7FFA7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 6:54: 3 2002 Delivered-To: freebsd-stable@freebsd.org Received: from skynet.stack.nl (insgate.stack.nl [131.155.140.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B54C37B41B for ; Thu, 30 May 2002 06:53:54 -0700 (PDT) Received: from dragon.stack.nl (dragon.stack.nl [2001:610:1108:5011:202:b3ff:fe17:a4cb]) by skynet.stack.nl (Postfix) with ESMTP id DF9FD9B17; Thu, 30 May 2002 15:54:29 +0200 (CEST) Received: by dragon.stack.nl (Postfix, from userid 1600) id 1723C988A; Thu, 30 May 2002 15:51:03 +0200 (CEST) Date: Thu, 30 May 2002 15:51:03 +0200 From: Dean Strik To: Vivek Khera Cc: freebsd-stable@freebsd.org Subject: Re: IPv6 and SSL Message-ID: <20020530135102.GA57195@dragon.stack.nl> References: <20020523182938.W10122-100000@root.nis.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.99i X-Editor: VIM Rulez! http://www.vim.org/ X-MUD: Outerspace - telnet://mud.stack.nl:3333 X-Really: Yes Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Vivek Khera wrote: > >>>>> "AG" == Aragon Gouveia writes: > > AG> There are some packages that I've tried compiling with IPv6 and SSL > AG> support. The Postfix port, for example, won't compile with both options > AG> checked. Other packages I've compiled manually compile and run, but ssl is > AG> broken. > > For the postfix port, the TLS/SSL support is from a patch to the > official postfix as is the IPv6 support. These two patch files > conflict (ie, try to patch some of the same things and both can't do > it). PLD.org.pl has an IPv6 patch that works on Lutz Jaenicke's TLS patch for postfix. A combined patch for IPv6+TLS can be downloaded at ftp://ftp.stack.nl/pub/postfix/ -- Dean C. Strik Eindhoven University of Technology dean@stack.nl | dean@ipnet6.org | http://www.ipnet6.org/ "This isn't right. This isn't even wrong." -- Wolfgang Pauli To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 7:23: 2 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tomts13-srv.bellnexxia.net (tomts13.bellnexxia.net [209.226.175.34]) by hub.freebsd.org (Postfix) with ESMTP id EF2C737B407 for ; Thu, 30 May 2002 07:22:56 -0700 (PDT) Received: from localhost ([65.95.160.142]) by tomts13-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20020530142256.YWRA16321.tomts13-srv.bellnexxia.net@localhost> for ; Thu, 30 May 2002 10:22:56 -0400 Date: Thu, 30 May 2002 10:22:55 -0400 Subject: Re: Server won't boot after recompile the kernel with ipfw support Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v481) From: Bryan Fullerton To: freebsd-stable Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: X-Mailer: Apple Mail (2.481) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday, May 30, 2002, at 02:44 AM, Ian wrote: > Look at rc.firewall, the * case in the switch checks to see if the > firewall_type is a file that can be read and if so it uses it. I think > the > comments are still valid. Certainly it still works that way for me, > and I'm > sync'd up with -STABLE as of about a week ago. Ah, right you are, I misread the * case. Works better for me to use a shell script, much like rc.firewall, to do variable substitution for IP addresses instead of generating explicit ruleset files. Thanks, Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 8: 4:22 2002 Delivered-To: freebsd-stable@freebsd.org Received: from dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (dclient80-218-17-199.hispeed.ch [80.218.17.199]) by hub.freebsd.org (Postfix) with ESMTP id 18ECC37B416 for ; Thu, 30 May 2002 08:04:02 -0700 (PDT) Received: from beerswilling.netscum.dyndns.dk ([2002:50da:11c7:0:200:c0ff:fefc:19aa]) by dastardly.newsbastards.org.72.27.172.IN-addr.ARPA.NetScum.dyndns.dk (8.11.6/8.11.6-SPAMMERS-DeLiGHt) with ESMTP id g4UF3wl15722 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified NO) for ; Thu, 30 May 2002 17:04:00 +0200 (CEST) (envelope-from bounce@cvsup.netscum.dyndns.dk) Received: (from root@localhost) by beerswilling.netscum.dyndns.dk (8.11.6/SMI-4.1-R00T0WNED) id g4UF3wT15721; Thu, 30 May 2002 17:03:58 +0200 (CEST) (envelope-from bounce@cvsup.netscum.dyndns.dk) Date: Thu, 30 May 2002 17:03:58 +0200 (CEST) Message-Id: <200205301503.g4UF3wT15721@beerswilling.netscum.dyndns.dk> From: BOUWSMA Beery Organization: Men not wearing any pants that dont shave To: freebsd-stable@freebsd.org Subject: Panic in IPv6... X-Hacked: via telnet to your port 25, what else? X-Internet-Access-Provided-By: Mountain Informatik AG X-NetScum: Yes X-One-And-Only-Real-True-Fluffy: No Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Howdy, I just saw a panic with 4.5-STABLE built around 10.March I have a DHCP-assigned address, from which I derive a 6to4 IPv6 address assigned to the stf0 interface. What happened this time was that the IPv4-assigned address from DHCP changed, and I wasn't paying attention (also, I hadn't hacked things to change everything as I should) Of course, the IPv6 network seemed to be down. So I brought up a gif tunnel, then did a `netstat -nr' command, and *POW* Here's the trace Fatal trap 12: page fault while in kernel mode fault virtual address = 0xef920220 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01e69cb stack pointer = 0x10:0xc7269b9c frame pointer = 0x10:0xc7269bb4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 338 (bplay) interrupt mask = trap number = 12 panic: page fault [...] #4 0xc028e97d in trap_pfault (frame=0xc7269b5c, usermode=0, eva=4019323424) at /usr/src/sys/i386/i386/trap.c:859 #5 0xc028e4f7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -275643904, tf_esi = -1053182208, tf_ebp = -953771084, tf_isp = -953771128, tf_ebx = -1053657088, tf_edx = -1053179624, tf_ecx = -1070262636, tf_eax = -1053657312, tf_trapno = 12, tf_err = 0, tf_eip = -1071748661, tf_cs = 8, tf_eflags = 66182, tf_esp = 0, tf_ss = -1071748756}) at /usr/src/sys/i386/i386/trap.c:458 #6 0xc01e69cb in nd6_timer (ignored_arg=0x0) at /usr/src/sys/netinet6/nd6.c:445 #7 0xc0173ead in softclock () at /usr/src/sys/kern/kern_timeout.c:131 #8 0xc0282f5f in doreti_swi () #9 0xc0177aa9 in diskstrategy (bp=0xc2886074) at /usr/src/sys/kern/subr_disk.c:251 #10 0xc01a6e58 in spec_strategy (ap=0xc7269ca4) at /usr/src/sys/miscfs/specfs/spec_vnops.c:479 #11 0xc01a6881 in spec_vnoperate (ap=0xc7269ca4) at /usr/src/sys/miscfs/specfs/spec_vnops.c:119 #12 0xc0214c01 in ufs_vnoperatespec (ap=0xc7269ca4) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2440 #13 0xc0214501 in ufs_strategy (ap=0xc7269ce8) at vnode_if.h:944 #14 0xc0214bd1 in ufs_vnoperate (ap=0xc7269ce8) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2422 #15 0xc0193966 in bwrite (bp=0xc2886074) at vnode_if.h:944 #16 0xc01990b6 in vop_stdbwrite (ap=0xc7269d24) at /usr/src/sys/kern/vfs_default.c:331 #17 0xc0198f11 in vop_defaultop (ap=0xc7269d24) at /usr/src/sys/kern/vfs_default.c:150 #18 0xc0214bd1 in ufs_vnoperate (ap=0xc7269d24) at /usr/src/sys/ufs/ufs/ufs_vnops.c:2422 #19 0xc0193cb6 in bawrite (bp=0xc2886074) at vnode_if.h:1193 #20 0xc019877f in cluster_wbuild (vp=0xc7254780, size=65536, start_lbn=89454, len=2) at /usr/src/sys/kern/vfs_cluster.c:945 #21 0xc01982a2 in cluster_write (bp=0xc28ce014, filesize=5862457344, seqcount=127) at /usr/src/sys/kern/vfs_cluster.c:576 #22 0xc020d876 in ffs_write (ap=0xc7269e64) at /usr/src/sys/ufs/ufs/ufs_readwrite.c:544 #23 0xc01a2dae in vn_write (fp=0xc150fac0, uio=0xc7269ed4, cred=0xc13f8480, flags=0, p=0xc6707520) at vnode_if.h:363 #24 0xc017cd8d in dofilewrite (p=0xc6707520, fp=0xc150fac0, fd=3, buf=0x30058000, nbyte=65536, offset=-1, flags=0) at /usr/src/sys/sys/file.h:162 ---Type to continue, or q to quit--- #25 0xc017cc46 in write (p=0xc6707520, uap=0xc7269f80) at /usr/src/sys/kern/sys_generic.c:329 #26 0xc028ef85 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 65536, tf_esi = 1, tf_ebp = -1077937404, tf_isp = -953770028, tf_ebx = 0, tf_edx = 3, tf_ecx = 805666816, tf_eax = 4, tf_trapno = 7, tf_err = 2, tf_eip = 672002840, tf_cs = 31, tf_eflags = 518, tf_esp = -1077937464, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1167 #27 0xc0281b45 in Xint0x80_syscall () #28 0x8049228 in ?? () #29 0x8048add in ?? () This is the IPv6-related line of interest #6 0xc01e69cb in nd6_timer (ignored_arg=0x0) at /usr/src/sys/netinet6/nd6.c:445 445 if ((ifp = rt->rt_ifp) == NULL) { date of source is nd6.c,v 1.2.2.10 2001/12/20 10:30:19 ru Anyone care to give a quick tutorial on what more I want to look at? I see that (kgdb) p ifp $6 = (struct ifnet *) 0xef920200 and (kgdb) p *rt $8 = {rt_nodes = {{rn_mklist = 0xc13b9c00, rn_parent = 0xa4, rn_bit = 1, [...] rt_flags = 2148269631, rt_ifp = 0xef920200, rt_ifa = 0x0, and (kgdb) p rt->rt_ifp $9 = (struct ifnet *) 0xef920200 but (kgdb) p *ifp Cannot access memory at address 0xef920200. (same for *rt->rt_ifp) if that means anything. Feel free to tell me to update; I need a good kick in the pants thanks barry bouwsma To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 9:10:24 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 14E8537B404 for ; Thu, 30 May 2002 09:10:10 -0700 (PDT) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g4UGA8p69225 for ; Thu, 30 May 2002 09:10:08 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.1 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 30 May 2002 09:10:08 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: stable@freebsd.org Subject: ssh + X11 forwarding = a hung ssh process Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been seeing a strange problem involving ssh's X11 forwarding on FreeBSD-stable systems. Here's the scenario. From my desktop machine I use ssh to run an X11 application on a different machine. The application appears on my desktop's screen as expected, and it works fine. Now I exit the application. But the ssh command does not exit; it remains hung until I kill it. For example: my desktop machine is "strings" and the other machine is "thin". I start an xterm like this: strings$ ssh thin xterm Now I exit the xterm by typing "logout" into it. The xterm goes away, but the ssh command does not exit. It just sits there until I kill it. The desktop machine (strings) is running 4.5-stable from around 2 Feb. 2002. It has XFree86-4.1.0_10 installed from ports. The other machine (thin) is running 4.6-RC1 from 18 May 2002. Is anybody else seeing this problem? I'll append the "ssh -v" output below. John strings$ ssh -v thin xterm OpenSSH_2.9 FreeBSD localisations 20011202, SSH protocols 1.5/2.0, OpenSSL 0x0090601f debug1: Reading configuration data /home/jdp/.ssh/config debug1: Applying options for thin debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Rhosts Authentication disabled, originating port will not be trusted. debug1: restore_uid debug1: ssh_connect: getuid 1001 geteuid 1001 anon 1 debug1: Connecting to thin.polstra.com [206.213.73.5] port 22. debug1: temporarily_use_uid: 1001/1001 (e=1001) debug1: restore_uid debug1: temporarily_use_uid: 1001/1001 (e=1001) debug1: restore_uid debug1: Connection established. debug1: identity file /home/jdp/.ssh/identity type 0 debug1: identity file /home/jdp/.ssh/id_rsa type 1 debug1: identity file /home/jdp/.ssh/id_dsa type 2 debug1: Remote protocol version 1.99, remote software version OpenSSH_2.9 FreeBSD localisations 20020307 debug1: match: OpenSSH_2.9 FreeBSD localisations 20020307 pat ^OpenSSH Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_2.9 FreeBSD localisations 20011202 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: dh_gen_key: priv key bits set: 139/256 debug1: bits set: 1036/2049 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'thin.polstra.com' is known and matches the DSA host key. debug1: Found key in /home/jdp/.ssh/known_hosts2:3 debug1: bits set: 1017/2049 debug1: len 55 datafellows 0 debug1: ssh_dss_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that can continue: publickey,password,keyboard-interactive debug1: next auth method to try is publickey debug1: userauth_pubkey_agent: testing agent key /home/jdp/.ssh/id_dsa debug1: input_userauth_pk_ok: pkalg ssh-dss blen 433 lastkey 0x808b370 hint -1 debug1: ssh-userauth2 successful: method publickey debug1: channel 0: new [client-session] debug1: channel_new: 0 debug1: send channel open 0 debug1: Entering interactive session. debug1: client_init id 0 arg 0 debug1: Requesting X11 forwarding with authentication spoofing. debug1: Requesting authentication agent forwarding. debug1: Sending command: xterm debug1: channel 0: open confirm rwindow 0 rmax 16384 debug1: client_input_channel_open: ctype x11 rchan 3 win 4096 max 2048 debug1: client_request_x11: request from 206.213.73.5 1094 debug1: fd 7 setting O_NONBLOCK debug1: fd 7 IS O_NONBLOCK debug1: channel 1: new [x11] debug1: confirm x11 [At this point the xterm is on the screen and I can use it. Now I quit the xterm by typing "logout".] debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: rcvd eof debug1: channel 0: output open -> drain debug1: channel 0: rcvd close debug1: channel 0: input open -> closed debug1: channel 0: close_read debug1: channel 1: rcvd eof debug1: channel 1: output open -> drain debug1: channel 0: obuf empty debug1: channel 0: output drain -> closed debug1: channel 0: close_write debug1: channel 0: send close debug1: channel 0: is dead debug1: channel_free: channel 0: status: The following connections are open: #0 client-session (t4 r0 i8/0 o128/0 fd -1/-1) #1 x11 (t4 r3 i1/0 o32/0 fd 7/7) debug1: channel_free: channel 0: dettaching channel user debug1: channel 1: obuf empty debug1: channel 1: output drain -> closed debug1: channel 1: close_write debug1: channel 1: read<=0 rfd 7 len 0 debug1: channel 1: read failed debug1: channel 1: input open -> drain debug1: channel 1: close_read debug1: channel 1: input: no drain shortcut debug1: channel 1: ibuf empty debug1: channel 1: input drain -> closed debug1: channel 1: send eof debug1: channel 1: send close debug1: channel 1: rcvd close debug1: channel 1: is dead debug1: channel_free: channel 1: status: The following connections are open: #1 x11 (t4 r3 i8/0 o128/0 fd 7/7) [Now the xterm window is gone from my screen. But the ssh process remains until I kill it manually.] ^CKilled by signal 2. debug1: Calling cleanup 0x805f450(0x0) debug1: Calling cleanup 0x805971c(0x0) strings$ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 9:19:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.robhughes.com (12-237-138-77.client.attbi.com [12.237.138.77]) by hub.freebsd.org (Postfix) with SMTP id 7A34737B40B for ; Thu, 30 May 2002 09:19:29 -0700 (PDT) Received: (qmail 35750 invoked from network); 30 May 2002 16:19:28 -0000 Received: from hexch01.robhughes.com (192.168.1.3) by ns2.robhughes.com with SMTP; 30 May 2002 16:19:28 -0000 MIME-Version: 1.0 Subject: RE: Error in make buildworld (cvs 5-29 @ 11:30 CDT) Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Thu, 30 May 2002 11:19:28 -0500 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Error in make buildworld (cvs 5-29 @ 11:30 CDT) Thread-Index: AcIHn45tqfT+AIGNRaSgvIq5dk3rJAAVhGRw From: "Robert D Hughes" To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yep, sure as shootin'. I took the system down and ran a drive diagnostics and found some bad clusters. Dumpfs correllated that to the /usr slice. Fortunately, I was able to allocate some clusters from the spares section to maintain the file system, but it looks like time to replace this drive. Thanks, Rob -----Original Message----- From: Kris Kennaway [mailto:kris@obsecurity.org] Sent: Thursday, May 30, 2002 1:02 AM To: Robert D Hughes Cc: stable@freebsd.org Subject: Re: Error in make buildworld (cvs 5-29 @ 11:30 CDT) On Wed, May 29, 2002 at 11:55:03PM -0500, Rob Hughes wrote: > /usr/libexec/elf/ld: k_cos.o: invalid string offset 27 >=3D 0 for section > `' > /usr/libexec/elf/ld: k_cos.o: invalid string offset 33 >=3D 0 for section > `' > /usr/libexec/elf/ld: k_cos.o: invalid string offset 43 >=3D 0 for section > `' > /usr/lib/libm.a(s_sin.o): In function `__generic_sin': > s_sin.o(.text+0xa3): undefined reference to `__kernel_cos' > s_sin.o(.text+0xdf): undefined reference to `__kernel_cos' Looks like your libm has become corrupted. Try recompiling/reinstalling it. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 9:40:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 10ABC37B401 for ; Thu, 30 May 2002 09:40:33 -0700 (PDT) Received: from v-ger.we.lc.ehu.es (v-ger.we.lc.ehu.es [158.227.6.51]) by polaris.we.lc.ehu.es (8.11.6/8.11.6) with ESMTP id g4UGeU518496; Thu, 30 May 2002 18:40:30 +0200 (MET DST) Received: (from jose@localhost) by v-ger.we.lc.ehu.es (8.11.6/8.11.6) id g4UGeVM02466; Thu, 30 May 2002 18:40:31 +0200 (CEST) (envelope-from jose) Date: Thu, 30 May 2002 18:40:31 +0200 From: "Jose M. Alcaide" To: John Polstra Cc: stable@FreeBSD.ORG Subject: Re: ssh + X11 forwarding = a hung ssh process Message-ID: <20020530184031.C229@v-ger.we.lc.ehu.es> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jdp@polstra.com on Thu, May 30, 2002 at 09:10:08AM -0700 X-Operating-System: FreeBSD 4.5-RELEASE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, May 30, 2002 at 09:10:08AM -0700, John Polstra wrote: > I've been seeing a strange problem involving ssh's X11 forwarding > on FreeBSD-stable systems. Here's the scenario. From my desktop > machine I use ssh to run an X11 application on a different machine. > The application appears on my desktop's screen as expected, and it > works fine. Now I exit the application. But the ssh command does not > exit; it remains hung until I kill it. > > [SNIP] Same here. I found that the problem only manifests itself when using the SSH2 protocol. When connecting from a machine running 4.5-RELEASE to another one running 4.5-RELEASE or 5.0-CURRENT, the ssh command remains hung just as you described. However, if the connection is established from a 5.0-CURRENT system, no message ("waiting for forwarded connections to terminate...") is displayed after closing the ssh session, but the ssh command *does* exit when the X11 client terminates. -- ****** Jose M. Alcaide // jose@we.lc.ehu.es // jmas@FreeBSD.org ****** ** "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein ** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 9:44:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id CF2C237B400 for ; Thu, 30 May 2002 09:44:36 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g4UGiVp69423; Thu, 30 May 2002 09:44:31 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g4UGiUL37957; Thu, 30 May 2002 09:44:30 -0700 (PDT) (envelope-from jdp) Date: Thu, 30 May 2002 09:44:30 -0700 (PDT) Message-Id: <200205301644.g4UGiUL37957@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: jose@we.lc.ehu.es Subject: Re: ssh + X11 forwarding = a hung ssh process In-Reply-To: <20020530184031.C229@v-ger.we.lc.ehu.es> References: <20020530184031.C229@v-ger.we.lc.ehu.es> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020530184031.C229@v-ger.we.lc.ehu.es>, Jose M. Alcaide wrote: > On Thu, May 30, 2002 at 09:10:08AM -0700, John Polstra wrote: > > I've been seeing a strange problem involving ssh's X11 forwarding > > on FreeBSD-stable systems. Here's the scenario. From my desktop > > machine I use ssh to run an X11 application on a different machine. > > The application appears on my desktop's screen as expected, and it > > works fine. Now I exit the application. But the ssh command does not > > exit; it remains hung until I kill it. > > > > [SNIP] > > Same here. I found that the problem only manifests itself when using the > SSH2 protocol. Aha, you are right! If I force version 1 of the protocol, the problem does not occur. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 10: 0:17 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mailtoaster1.pipeline.ch (mailtoaster1.pipeline.ch [62.48.0.70]) by hub.freebsd.org (Postfix) with SMTP id 13C2337B400 for ; Thu, 30 May 2002 09:59:48 -0700 (PDT) Received: (qmail 40396 invoked from network); 30 May 2002 16:59:27 -0000 Received: from unknown (HELO pipeline.ch) ([62.48.0.53]) (envelope-sender ) by mailtoaster1.pipeline.ch (qmail-ldap-1.03) with SMTP for ; 30 May 2002 16:59:27 -0000 Message-ID: <3CF65A3C.915493B8@pipeline.ch> Date: Thu, 30 May 2002 18:58:37 +0200 From: Andre Oppermann X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-net@freebsd.org Cc: freebsd-stable@freebsd.org Subject: FreeBSD kernel routing table, need statistics, please install this patch Content-Type: multipart/mixed; boundary="------------FF908FDE6605971918FB41DB" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------FF908FDE6605971918FB41DB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all, while working on a design overhaul of the kernel routing table I was inspecting the rt_metrics stuff a little bit closer. Then I checked with some busier web servers to see how much effect the rt_metric caching actually has. The result was not very clear. Some conntctions never got cached. The attached patch collects some statistics about the usage of the rt_metrics on a system. Specifically it counts how many time it a new tcp session has been established, how many times of those it found useful cached rt_metrics and then how many times it updated those metrics. The counters look like this (on a freshly booted system): # sysctl -a | grep tcp.rmx net.inet.tcp.rmxcachelookup: 3 net.inet.tcp.rmxcachehit: 1 net.inet.tcp.rmxcacheupdate: 2 net.inet.tcp.rmxcachenoupdate: 0 Please apply the attached patch (against 4-STABLE) and after a couple of hours/days please send me the output of: # uname -a # sysctl -a | grep tcp.rmx # netstat -m # netstat -ran | wc -l # decription main usage of your system (webserver/workstation/whatever) I don't want to nuke it but I'd like to see how much it helps overall. Then, because it's TCP specific, I'd like to move it out of the main routing table (only MTU remains) and transform it into a hash table. The rt_metrics are host specific so they only ever got used on host routes and are wasting an enormous amount of space in the main routing table. Also the strategy of the rt_metrics caching is probably inapropriate for todays world with many web servers. The problem is the rt_metrics only get updated when a tcp session to/from that host closes and a sufficient number of packets have been exchanged to make a mostly accurate messurement of those parameters. Unfortunatly in todays world the webbrowsers open a number of connections in very rapid succession so there is no chance to have any cached values for the connections after the first if not one of them closed already. The benefit is only being seen when the user loads the next page and opens new tcp seesions. Even that is being migitated by HTTP/1.1 keepalive and pipelining since sessions are not closed anymore. A possible solution is to update the rt_cache for the first time after a sufficient number of packets have been exchanged to make a mostly accurate measurement. And then update it after any n packets thereafter. The here collected statistics and numbers will greatly help to determin the best way how to adjust the rt_metrics to be most effective. The patch applies against /usr/src/sys/netinet/tcp_[input.c|subr.c]. "Profile, don't speculate" Many thanks for your cooperation! -- Andre --------------FF908FDE6605971918FB41DB Content-Type: text/plain; charset=us-ascii; name="tcp_input.c.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="tcp_input.c.patch" --- tcp_input.c Sun Apr 28 07:40:26 2002 +++ tcp_input.c.new Thu May 30 18:18:20 2002 @@ -31,7 +31,7 @@ * SUCH DAMAGE. * * @(#)tcp_input.c 8.12 (Berkeley) 5/24/95 - * $FreeBSD: src/sys/netinet/tcp_input.c,v 1.107.2.23 2002/04/28 05:40:26 suz Exp $ + * $FreeBSD: src/sys/netinet/tcp_input.c,v 1.107.2.23 2002/05/30 16:12:00 andre Exp $ */ #include "opt_ipfw.h" /* for ipfw_fwd */ @@ -126,6 +126,16 @@ &drop_synfin, 0, "Drop TCP packets with SYN+FIN set"); #endif + +int rmxcachelookup = 0; +SYSCTL_INT(_net_inet_tcp, OID_AUTO, rmxcachelookup, + CTLFLAG_RD, &rmxcachelookup, 0, "RMX cache lookups"); + +int rmxcachehit = 0; +SYSCTL_INT(_net_inet_tcp, OID_AUTO, rmxcachehit, + CTLFLAG_RD, &rmxcachehit, 0, "RMX cache hits"); + + struct inpcbhead tcb; #define tcb6 tcb /* for KAME src sync over BSD*'s */ struct inpcbinfo tcbinfo; @@ -2521,7 +2531,13 @@ * or rttvar. Convert from the route-table units * to scaled multiples of the slow timeout timer. */ + + ++rmxcachelookup; + if (tp->t_srtt == 0 && (rtt = rt->rt_rmx.rmx_rtt)) { + + ++rmxcachehit; + /* * XXX the lock bit for RTT indicates that the value * is also a minimum value; this is subject to time. --------------FF908FDE6605971918FB41DB Content-Type: text/plain; charset=us-ascii; name="tcp_subr.c.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="tcp_subr.c.patch" --- tcp_subr.c Sun Apr 14 06:02:30 2002 +++ tcp_subr.c.new Thu May 30 18:19:12 2002 @@ -31,7 +31,7 @@ * SUCH DAMAGE. * * @(#)tcp_subr.c 8.2 (Berkeley) 5/24/95 - * $FreeBSD: src/sys/netinet/tcp_subr.c,v 1.73.2.25 2002/04/14 04:02:30 silby Exp $ + * $FreeBSD: src/sys/netinet/tcp_subr.c,v 1.73.2.25 2002/05/30 16:12:00 andre Exp $ */ #include "opt_compat.h" @@ -144,6 +144,16 @@ SYSCTL_INT(_net_inet_tcp, OID_AUTO, isn_reseed_interval, CTLFLAG_RW, &tcp_isn_reseed_interval, 0, "Seconds between reseeding of ISN secret"); + +int rmxcacheupdate = 0; +SYSCTL_INT(_net_inet_tcp, OID_AUTO, rmxcacheupdate, + CTLFLAG_RD, &rmxcacheupdate, 0, "RMX cache update"); + +int rmxcachenoupdate = 0; +SYSCTL_INT(_net_inet_tcp, OID_AUTO, rmxcachenoupdate, + CTLFLAG_RD, &rmxcachenoupdate, 0, "RMX cache no update"); + + static void tcp_cleartaocache __P((void)); static void tcp_notify __P((struct inpcb *, int)); @@ -638,6 +648,8 @@ == INADDR_ANY) goto no_valid_rt; + ++rmxcacheupdate; + if ((rt->rt_rmx.rmx_locks & RTV_RTT) == 0) { i = tp->t_srtt * (RTM_RTTUNIT / (hz * TCP_RTT_SCALE)); @@ -710,7 +722,9 @@ rt->rt_rmx.rmx_ssthresh = i; tcpstat.tcps_cachedssthresh++; } - } + } else + ++rmxcachenoupdate; + no_valid_rt: /* free the reassembly queue, if any */ while((q = LIST_FIRST(&tp->t_segq)) != NULL) { --------------FF908FDE6605971918FB41DB-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 11:59:20 2002 Delivered-To: freebsd-stable@freebsd.org Received: from castle.jp.FreeBSD.org (castle.jp.FreeBSD.org [210.226.20.15]) by hub.freebsd.org (Postfix) with ESMTP id 46ECC37B405 for ; Thu, 30 May 2002 11:59:17 -0700 (PDT) Received: from localhost (localhost [::1]) by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet6 id g4UIxGv42268 for ; Fri, 31 May 2002 03:59:16 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) In-Reply-To: <5D90F2332B50D411BE8A00209412104C03850978@QHS63> References: <5D90F2332B50D411BE8A00209412104C03850978@QHS63> X-User-Agent: Mew/1.94.2 XEmacs/21.5 (bamboo) X-FaceAnim: (-O_O-)(O_O- )(_O- )(O- )(- -)( -O)( -O_)( -O_O)(-O_O-) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Dispatcher: imput version 20000228(IM140) Lines: 14 From: Makoto Matsushita To: stable@FreeBSD.ORG Subject: RE: VMware 3.1.1 for Windows and FreeBSD 4.6-RC2 Date: Fri, 31 May 2002 03:59:14 +0900 Message-Id: <20020531035914V.matusita@jp.FreeBSD.org> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG alan.edmonds> I was able to mount the CDROM just fine and access the alan.edmonds> files. However, the umount /cdrom command hung. I alan.edmonds> shutdown the system and it said '/dev/acd0c: device alan.edmonds> busy' Hmm, it seems that it is the same problem I hit. Thanks. Any other users of VMware 2.x, or VMware 3.0 (not upgraded to the latest 3.x) will see the same problem? If you have an environment, would you please try it out? -- - Makoto `MAR' Matsushita To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 14:41: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id 7FB8C37B401; Thu, 30 May 2002 14:40:52 -0700 (PDT) Received: (from jj@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id g4ULemP12475; Thu, 30 May 2002 14:40:48 -0700 (PDT) Date: Thu, 30 May 2002 14:40:48 -0700 From: JJ Behrens To: freebsd-stable@FreeBSD.ORG, Matthew Dillon , Irwan Hadi , Jeff Jirsa , freebsd-questions@FreeBSD.ORG Subject: Re: Server won't boot after recompile the kernel with ipfw support Message-ID: <20020530144048.A24912@alicia.nttmcl.com> Mail-Followup-To: JJ Behrens , freebsd-stable@FreeBSD.ORG, Matthew Dillon , Irwan Hadi , Jeff Jirsa , freebsd-questions@FreeBSD.ORG References: <20020528142640.A22370@phxby.com> <20020528133316.S16405-100000@boris.st.hmc.edu> <20020528150941.A24676@phxby.com> <200205282131.g4SLVmYZ024980@apollo.backplane.com> <3CF48FB4.E82525FE@alogis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3CF48FB4.E82525FE@alogis.com>; from holger.kipp@alogis.com on Wed, May 29, 2002 at 10:22:12AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > To point out the obvious: put the firewall rules in "/etc/ipfw.conf", > if firewall_type contains a filename. If firewall_type is the name > of a configuration, edit rc.firewall. Hmm, very interesting. I can't seem to find this (i.e. pre-made firewall_type's) documented in the handbook. Am I missing something, or should I submit a PR? Best Regards, -jj -- Users of C++ should consider hanging themselves rather than shooting their legs off--it's best not to use C++ simply as a better C. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 14:49:25 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.zer0.org (klapaucius.zer0.org [204.152.186.45]) by hub.freebsd.org (Postfix) with ESMTP id 2E0CC37B408 for ; Thu, 30 May 2002 14:49:14 -0700 (PDT) Received: by mail1.zer0.org (Postfix, from userid 1001) id E2DE5239A02; Thu, 30 May 2002 14:49:13 -0700 (PDT) Date: Thu, 30 May 2002 14:49:13 -0700 From: Gregory Sutter To: Scott Long Cc: freebsd-stable@freebsd.org Subject: Re: Hardware RAID vs vinum Message-ID: <20020530214913.GE92646@klapaucius.zer0.org> References: <2C7CBDC6EA58D6119E4A00065B3A24CB04636E@btcexc01.btc.adaptec.com> <20020529134211.L82424@wantadilla.lemis.com> <20020529141141.GC2262@hollin.btc.adaptec.com> <20020530090247.Y82424@wantadilla.lemis.com> <200205300016.g4U0GaBY064168@apollo.backplane.com> <010501c2079f$7b37bc80$64805718@cns> <20020530073031.GA3228@hollin.btc.adaptec.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wchHw8dVAp53YPj8" Content-Disposition: inline In-Reply-To: <20020530073031.GA3228@hollin.btc.adaptec.com> User-Agent: Mutt/1.3.28i Organization: Zer0 X-Purpose: For great justice! Mail-Copies-To: poster X-Message-Flag: Ditch this virus-ridden Outlook crap and get a real mailer! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --wchHw8dVAp53YPj8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2002-05-30 01:30 -0600, Scott Long wrote: >=20 > The big problem is that while most companies can be persuaded > to share the specs on how to talk to the card and the arrays, > few will share the specs on the management interface that allows > you to control and monitor the thing. Adaptec is the only > one that I know of that produces FreeBSD versions of their > management apps, and they would never dream of publishing the > source code to them (except the for the asr controllers, but=20 > that's a different story). 3ware makes FreeBSD versions of their 3dm management daemon, although they're not very vocal about it. http://people.freebsd.org/~msmith/RAID/ Greg --=20 Gregory S. Sutter Build a man a fire, and he'll be warm mailto:gsutter@zer0.org for a day. Set a man on fire, and he'll http://www.zer0.org/~gsutter/ be warm for the rest of his life.=20 hkp://wwwkeys.pgp.net/0x845DFEDD --wchHw8dVAp53YPj8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: '' iD8DBQE89p5ZIBUx1YRd/t0RAqA3AJ4+Kv75Fx7RS46n5DoJeKBRG/nK9gCeOYw9 X+c0r0HjqzCQgonYRKu8CRI= =IYlV -----END PGP SIGNATURE----- --wchHw8dVAp53YPj8-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 16:41:21 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-187.dsl.lsan03.pacbell.net [64.169.107.187]) by hub.freebsd.org (Postfix) with ESMTP id 891FC37B40A for ; Thu, 30 May 2002 16:41:15 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DF4BB66B8B; Thu, 30 May 2002 16:41:14 -0700 (PDT) Date: Thu, 30 May 2002 16:41:14 -0700 From: Kris Kennaway To: John Polstra Cc: stable@freebsd.org Subject: Re: ssh + X11 forwarding = a hung ssh process Message-ID: <20020530164114.A1623@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jdp@polstra.com on Thu, May 30, 2002 at 09:10:08AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 30, 2002 at 09:10:08AM -0700, John Polstra wrote: > I've been seeing a strange problem involving ssh's X11 forwarding > on FreeBSD-stable systems. Here's the scenario. From my desktop > machine I use ssh to run an X11 application on a different machine. > The application appears on my desktop's screen as expected, and it > works fine. Now I exit the application. But the ssh command does not > exit; it remains hung until I kill it. >=20 > For example: my desktop machine is "strings" and the other machine > is "thin". I start an xterm like this: >=20 > strings$ ssh thin xterm >=20 > Now I exit the xterm by typing "logout" into it. The xterm goes away, > but the ssh command does not exit. It just sits there until I kill > it. I think it's intentional; the ssh tunnel needs to stay open so it can do X11 connection forwarding. Kris --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE89riaWry0BWjoQKURAiQUAKDOg9+RYVowLgwX2MMrZG21FDluFACgxGpu mi3QfE3kfhObrOaXrvQVKUE= =ZX5q -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 17: 1:40 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 68F0937B401 for ; Thu, 30 May 2002 17:01:34 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g4V01Up71666; Thu, 30 May 2002 17:01:30 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g4V01UM38350; Thu, 30 May 2002 17:01:30 -0700 (PDT) (envelope-from jdp) Date: Thu, 30 May 2002 17:01:30 -0700 (PDT) Message-Id: <200205310001.g4V01UM38350@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: kris@obsecurity.org Subject: Re: ssh + X11 forwarding = a hung ssh process In-Reply-To: <20020530164114.A1623@xor.obsecurity.org> References: <20020530164114.A1623@xor.obsecurity.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020530164114.A1623@xor.obsecurity.org>, Kris Kennaway wrote: > On Thu, May 30, 2002 at 09:10:08AM -0700, John Polstra wrote: > > For example: my desktop machine is "strings" and the other machine > > is "thin". I start an xterm like this: > > > > strings$ ssh thin xterm > > > > Now I exit the xterm by typing "logout" into it. The xterm goes away, > > but the ssh command does not exit. It just sits there until I kill > > it. > > I think it's intentional; the ssh tunnel needs to stay open so it can > do X11 connection forwarding. Nah, I don't agree with that. The ssh process should stay around as long as there is an X11 connection open, but it should die when the last tunneled X11 connection is closed (i.e., when the remote xterm exits). That's what it's traditionally done, and that's the more useful behavior. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 17:25:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from snafu.adept.org (snafu.adept.org [63.201.63.44]) by hub.freebsd.org (Postfix) with ESMTP id 05DC737B40D for ; Thu, 30 May 2002 17:24:35 -0700 (PDT) Received: by snafu.adept.org (Postfix, from userid 1000) id C6CD29EE34; Thu, 30 May 2002 17:24:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by snafu.adept.org (Postfix) with ESMTP id C3DB09B001; Thu, 30 May 2002 17:24:23 -0700 (PDT) Date: Thu, 30 May 2002 17:24:23 -0700 (PDT) From: Mike Hoskins To: John Polstra Cc: , Subject: Re: ssh + X11 forwarding = a hung ssh process In-Reply-To: <200205310001.g4V01UM38350@vashon.polstra.com> Message-ID: <20020530170501.A37186-100000@snafu.adept.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 30 May 2002, John Polstra wrote: > Nah, I don't agree with that. The ssh process should stay around as > long as there is an X11 connection open, but it should die when the > last tunneled X11 connection is closed (i.e., when the remote xterm > exits). That's what it's traditionally done, and that's the more > useful behavior. I see what I've always observed, mike@mojo{mike}$ ssh -C -X snafu.adept.org xterm mike@snafu.adept.org's password: Waiting for forwarded connections to terminate... The following connections are open: #1 X11 connection from snafu.adept.org port 2758 (t4 r0 i4/0 o16/0 fd 8/8) If you try to close the tunnel while X sessions are active, you get alerted of the open sessions. Otherwise, as in this case, things close normally. This is as of, mike@mojo{mike}$ uname -a FreeBSD mojo.televoke.net 4.6-RC FreeBSD 4.6-RC #0: Tue May 21 13:06:49 PDT 2002 mike@mojo.televoke.net:/usr/src/sys/compile/MOJO i386 Haven't tried after last night's cvsup. It's probably not related, but this isn't somehow tied into the existing Linux/HP-UX bug in the FAQ is it? http://www.openssh.com/faq.html#3.10 Probably not, I just knew about this because some developers complained to me awhile back. I always thought it was interesting that under 'Why' they say 'ssh needs to hang, because it needs to wait ...'. So why does it only do it on certain OSs? ;) Later, -Mike -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." --Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 18:23: 5 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-187.dsl.lsan03.pacbell.net [64.169.107.187]) by hub.freebsd.org (Postfix) with ESMTP id 5D19037B400 for ; Thu, 30 May 2002 18:22:59 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id E916B66B8B; Thu, 30 May 2002 18:22:58 -0700 (PDT) Date: Thu, 30 May 2002 18:22:58 -0700 From: Kris Kennaway To: John Polstra Cc: stable@freebsd.org, kris@obsecurity.org Subject: Re: ssh + X11 forwarding = a hung ssh process Message-ID: <20020530182258.A4728@xor.obsecurity.org> References: <20020530164114.A1623@xor.obsecurity.org> <200205310001.g4V01UM38350@vashon.polstra.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200205310001.g4V01UM38350@vashon.polstra.com>; from jdp@polstra.com on Thu, May 30, 2002 at 05:01:30PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 30, 2002 at 05:01:30PM -0700, John Polstra wrote: > In article <20020530164114.A1623@xor.obsecurity.org>, > Kris Kennaway wrote: > > On Thu, May 30, 2002 at 09:10:08AM -0700, John Polstra wrote: > > > For example: my desktop machine is "strings" and the other machine > > > is "thin". I start an xterm like this: > > > > > > strings$ ssh thin xterm > > > > > > Now I exit the xterm by typing "logout" into it. The xterm goes away, > > > but the ssh command does not exit. It just sits there until I kill > > > it. > >=20 > > I think it's intentional; the ssh tunnel needs to stay open so it can > > do X11 connection forwarding. >=20 > Nah, I don't agree with that. The ssh process should stay around as > long as there is an X11 connection open, but it should die when the > last tunneled X11 connection is closed (i.e., when the remote xterm > exits). That's what it's traditionally done, and that's the more > useful behavior. Sorry, I misread your mail. Kris --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE89tByWry0BWjoQKURAu63AJ9C8nWtYY7UuEx/EDxcU57uJ9qbbACg8ti6 EJfAqu1MmN4RiAmftelXWq0= =4S6B -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 18:33: 7 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id CC4CF37B404 for ; Thu, 30 May 2002 18:33:00 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g4V1Wsp72022; Thu, 30 May 2002 18:32:54 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g4V1Wrw38438; Thu, 30 May 2002 18:32:53 -0700 (PDT) (envelope-from jdp) Date: Thu, 30 May 2002 18:32:53 -0700 (PDT) Message-Id: <200205310132.g4V1Wrw38438@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: mike@adept.org Subject: Re: ssh + X11 forwarding = a hung ssh process In-Reply-To: <20020530170501.A37186-100000@snafu.adept.org> References: <20020530170501.A37186-100000@snafu.adept.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020530170501.A37186-100000@snafu.adept.org>, Mike Hoskins wrote: > On Thu, 30 May 2002, John Polstra wrote: > > > Nah, I don't agree with that. The ssh process should stay around as > > long as there is an X11 connection open, but it should die when the > > last tunneled X11 connection is closed (i.e., when the remote xterm > > exits). That's what it's traditionally done, and that's the more > > useful behavior. > > I see what I've always observed, > > mike@mojo{mike}$ ssh -C -X snafu.adept.org xterm > mike@snafu.adept.org's password: > > > Waiting for forwarded connections to terminate... > The following connections are open: > #1 X11 connection from snafu.adept.org port 2758 (t4 r0 i4/0 o16/0 fd 8/8) > > If you try to close the tunnel while X sessions are active, you get > alerted of the open sessions. Otherwise, as in this case, things close > normally. It only happens when protocol version 2 is used. Try forcing that with "ssh -2 ...", and there's a good chance you'll see the problem. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 22: 4:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 82F4B37B406 for ; Thu, 30 May 2002 22:04:40 -0700 (PDT) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id IBS96788; Fri, 31 May 2002 08:04:29 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.6/8.11.6) id g4V52mv00301; Fri, 31 May 2002 08:02:48 +0300 (EEST) (envelope-from netch) Date: Fri, 31 May 2002 08:02:48 +0300 From: Valentin Nechayev To: Dmitry Morozovsky Cc: stable@FreeBSD.ORG Subject: Re: Tagged IBM ATA drives under nowadays -stable Message-ID: <20020531080248.A233@iv.nn.kiev.ua> References: <20020515154032.U19317-100000@woozle.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020515154032.U19317-100000@woozle.rinet.ru>; from marck@rinet.ru on Wed, May 15, 2002 at 04:05:39PM +0400 X-42: On Organization: Dark side of coredump Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Wed, May 15, 2002 at 16:05:39, marck (Dmitry Morozovsky) wrote about "Tagged IBM ATA drives under nowadays -stable": > am I the only unlucky person who stucks with non-working tagged ATA drives > from IBM with nowadays ata? > > All our systems with different chipsets (from Intel TX to VIA K7) with ata > tags enabled drops to ata timeouts, and then swiths to PIO mode, where > (partly) successively works. Part of my dmesg with any kernel later than Mar,17: start_init: trying /sbin/init ad2: invalid primary partition table: no magic ad2: timeout waiting for READY ad2: invalidating queued requests - resetting ata1: resetting devices .. ata1: mask=03 ostat0=51 ostat2=00 ad2: ATAPI 00 00 ata1-slave: ATAPI 00 00 ata1: mask=03 stat0=50 stat1=00 ad2: ATA 01 a5 ata1: devices=01 ad2: invalidating queued requests ad2: success setting UDMA2 on Intel chip done ad2: no request for tag=0 ad2: invalidating queued requests ad2: READ command timeout tag=0 serv=0 - resetting ad2: invalidating queued requests ata1: resetting devices .. ata1: mask=03 ostat0=51 ostat2=00 ad2: ATAPI 00 00 ata1-slave: ATAPI 00 00 ata1: mask=03 stat0=50 stat1=00 ad2: ATA 01 a5 ata1: devices=01 ad2: invalidating queued requests ad2: success setting UDMA2 on Intel chip done ad2: no request for tag=0 ad2: invalidating queued requests ad2: READ command timeout tag=0 serv=0 - resetting ad2: invalidating queued requests ata1: resetting devices .. ata1: mask=03 ostat0=51 ostat2=00 ad2: ATAPI 00 00 ata1-slave: ATAPI 00 00 ata1: mask=03 stat0=50 stat1=00 ad2: ATA 01 a5 ata1: devices=01 [...] ad2: success setting PIO4 on generic chip This can be somewhere explained, but "ad2: invalid primary partition table: no magic" looks too strange :( This is i815E MB with ICH2; ad2: ATA-5 disk at ata1-master ad2: 39266MB (80418240 sectors), 79780 C, 16 H, 63 S, 512 B ad2: 16 secs/int, 32 depth queue, tagged UDMA33 ad2: piomode=4 dmamode=2 udmamode=5 cblid=1 /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu May 30 23: 0:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 34CAC37B404 for ; Thu, 30 May 2002 23:00:03 -0700 (PDT) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id WAA53394; Thu, 30 May 2002 22:56:05 -0700 (PDT) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.6/8.11.6) id g4V5t5p99068; Thu, 30 May 2002 22:55:05 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200205310555.g4V5t5p99068@arch20m.dellroad.org> Subject: Re: pthreads + msgrcv In-Reply-To: <3CF53129.6040903@hostname.org> "from Fabio Yasusi Yamamoto at May 29, 2002 04:51:05 pm" To: Fabio Yasusi Yamamoto Date: Thu, 30 May 2002 22:55:05 -0700 (PDT) Cc: stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Fabio Yasusi Yamamoto writes: > i'm trying to use "pthread" with "ipc messages". > For a reason I don't know it stops ( block )the entire process. The reason is bin/37676. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 0: 3:54 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tesla.distributel.net (nat.MTL.distributel.NET [66.38.181.24]) by hub.freebsd.org (Postfix) with ESMTP id 544B337B401 for ; Fri, 31 May 2002 00:03:50 -0700 (PDT) Received: (from bmilekic@localhost) by tesla.distributel.net (8.11.6/8.11.6) id g4TG10j61588; Wed, 29 May 2002 12:01:00 -0400 (EDT) (envelope-from bmilekic@unixdaemons.com) Date: Wed, 29 May 2002 12:01:00 -0400 From: Bosko Milekic To: Ian Dowse Cc: Makoto Matsushita , stable@FreeBSD.ORG Subject: Re: VMware 3.1.1 for Windows and FreeBSD 4.6-RC2 Message-ID: <20020529120100.A61559@unixdaemons.com> References: <20020529113651.A74576@unixdaemons.com> <200205291648.aa58472@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200205291648.aa58472@salmon.maths.tcd.ie>; from iedowse@maths.tcd.ie on Wed, May 29, 2002 at 04:48:01PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, May 29, 2002 at 04:48:01PM +0100, Ian Dowse wrote: > In message <20020529113651.A74576@unixdaemons.com>, Bosko Milekic writes: > > I don't know what's up, but I tried installing a -CURRENT snapshot via > > a virtual CD "containing" the snapshot iso and got this behavior (I've > > tried several times on my laptop): > > On most hardware you need to disable the use of "cmpxchg" to get > -CURRENT to run in VMware at a non-zero speed: > > Index: atomic.h > =================================================================== > RCS file: /dump/FreeBSD-CVS/src/sys/i386/include/atomic.h,v > retrieving revision 1.26 > diff -u -r1.26 atomic.h > --- atomic.h 28 Feb 2002 06:17:05 -0000 1.26 > +++ atomic.h 11 Mar 2002 17:43:37 -0000 > @@ -106,7 +106,7 @@ > * Returns 0 on failure, non-zero on success > */ > > -#if defined(I386_CPU) > +#if defined(I386_CPU) || 1 > static __inline int > atomic_cmpset_int(volatile u_int *dst, u_int exp, u_int src) > { > > I haven't seen the need for this on -stable, but it might be > worth a try. We could do with a loader-tunable setting so that > you don't need to build a custom kernel for installation in > VMware. Yes, that would be awesome. By the way, why "cmpxchg?" Does it have to do with VMWare not liking bus-locked instructions? How about the instruction prefix "lock" ? How is it handled by VMWare, anyway? > Ian Thanks, -- Bosko Milekic bmilekic@unixdaemons.com bmilekic@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 0: 6:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cicero2.cybercity.dk (cicero2.cybercity.dk [212.242.40.53]) by hub.freebsd.org (Postfix) with ESMTP id 016F437B404; Fri, 31 May 2002 00:06:08 -0700 (PDT) Received: from user2.cybercity.dk (fxp0.user2.ip.cybercity.dk [212.242.41.35]) by cicero2.cybercity.dk (Postfix) with ESMTP id 8EF921000D6; Fri, 31 May 2002 09:06:06 +0200 (CEST) Received: from thrawn.birch.se (port324.cvx3-mal.ppp.netlink.se [62.66.14.71]) by user2.cybercity.dk (Postfix) with ESMTP id 14B1B540F; Fri, 31 May 2002 09:05:59 +0200 (CEST) Date: Fri, 31 May 2002 09:06:23 +0200 (CEST) From: =?iso8859-1?Q?Mattias_Bj=F6rk?= X-X-Sender: thrawn@thrawn.birch.se To: Ruslan Ermilov Cc: stable@FreeBSD.ORG Subject: Re: Problems when runing make installworld. In-Reply-To: <20020528071935.GD53736@sunbay.com> Message-ID: <20020531090140.V40770-200000@thrawn.birch.se> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1986994741-1022828783=:40770" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1986994741-1022828783=:40770 Content-Type: TEXT/PLAIN; charset=iso8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Hi, Again, thanks for the answer, i read http://www.freebsd.org/cgi/query-pr.cgi?pr=3D30276. It says there that if you are building make world with a p3 and run make in= stallworld on a 486 you get this error. But I don't have a p3 I have a dual celeron, I have also attached my make.conf from the building machine. And its a p90 that Im makeing the make worldinstall on. But any way the problem seams too be the same or am I wrong? Thanks in advance for the answer, sorry that I did take so mutch time on answering your answer. Mvh Mattias Bj=F6rk Real Programmers don't write in PL/I. PL/I is for programmers who can't decide whether to write in COBOL or FORTRAN. On Tue, 28 May 2002, Ruslan Ermilov wrote: > This is a known issue, for which there's no a quick solution. > Please see PR 30276 for details. > > On Mon, May 27, 2002 at 10:52:23PM +0200, Mattias Bj?rk wrote: > > On Mon, 27 May 2002, Mattias Bj?rk wrote: > > > > > Hi, > > > > > > I have one dual celeron 400 MHz that i runed a make buildworld. And t= hen i > > > export /usr/src and /usr/obj with nfs to my box that I world like to > > > upgrade. Its an p90 laptop, so that is why Im doing the build on my d= ual > > > 400. :) > > > > > > Any way when I run make installworld on the laptop, I get goes for ab= out > > > 30 sec to one minute and then /usr/bin/install crashes with this erro= r > > > message: > > > > > > mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p > > > /usr/include > > > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*= =2Eh > > > /usr/include/cam > > > Illegal instruction - core dumped > > > *** Error code 132 > > > > > > Stop in /usr/src/include. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > > > > Any clues? I have attched the hole make installworld log. It seems th= at > > > there is something wrong with my install file or? I copyied it from > > > another machine that is a p120, but that did not help. Same problem, = first > > > I thought that It hade something to do with that I was runing make > > > installworld in multiuser mode. But i rebooted and runed it with boot= -s > > > but that did not help either. > > > > > > Any clues/tips/flames welcome, as you can see it is no fun at all (TM= ) to > > > run a make world on a p90. I have done it before and it worked but i > > > rather not do that... :) > > > > > > Perhaps you need more info, then do not hasitate to ask for it. Might= take > > > some time to answer this mail because I have some mails to catch up i= n > > > my mbox... > > > > > > Sorry if i typ to mutch... I will do better next time... > > > > > > Mvh Mattias Bj?rk > > > > > > Real Programmers don't write in PL/I. PL/I is for programmers who > > > can't decide whether to write in COBOL or FORTRAN. > > > > > > Script started on Mon May 27 22:36:18 2002 > > # make installworld > > mkdir -p /tmp/install.2474 > > for prog in [ awk cat chflags chmod chown date echo egrep find grep ln= make makewhatis mtree mv perl rm sed sh sysctl test true uname wc zic; do= cp `which $prog` /tmp/install.2474; done > > cd /usr/src; MAKEOBJDIRPREFIX=3D/usr/obj MACHINE_ARCH=3Di386 MACHINE= =3Di386 OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec PERL5LIB=3D/us= r/obj/usr/src/i386/usr/libdata/perl/5.00503 GROFF_BIN_PATH=3D/usr/obj/usr/= src/i386/usr/bin GROFF_FONT_PATH=3D/usr/obj/usr/src/i386/usr/share/groff_f= ont GROFF_TMAC_PATH=3D/usr/obj/usr/src/i386/usr/share/tmac PATH=3D/usr/ob= j/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386= /usr/games:/tmp/install.2474 make -f Makefile.inc1 reinstall > > -------------------------------------------------------------- > > >>> Making hierarchy > > -------------------------------------------------------------- > > cd /usr/src; make -f Makefile.inc1 hierarchy > > cd /usr/src/etc;=09=09make distrib-dirs > > set - `grep "^[a-zA-Z]" /usr/src/etc/locale.deprecated`; while [ $# -g= t 0 ] ; do for dir in /usr/share/locale /usr/share/nls /usr/local/share= /nls; do test -d /${dir} && cd /${dir}; test -L "$2" && rm -rf "$2"; te= st \! -L "$1" && test -d "$1" && mv "$1" "$2"; done; shift; shift; done > > mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / > > mtree -deU -f /usr/src/etc/mtree/BSD.var.dist -p /var > > mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr > > mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include > > mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/libdata/perl= /5.00503/mach > > cd /; rm -f /sys; ln -s usr/src/sys sys > > cd /usr/share/man/en.ISO8859-1; ln -sf ../man* . > > cd /usr/share/man; set - `grep "^[a-zA-Z]" /usr/src/etc/man.alias`; w= hile [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; don= e > > cd /usr/share/locale; set - `grep "^[a-zA-Z]" /usr/src/etc/locale.alia= s`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift= ; done > > cd /usr/share/nls; set - `grep "^[a-zA-Z]" /usr/src/etc/nls.alias`; w= hile [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; don= e > > > > -------------------------------------------------------------- > > >>> Installing everything.. > > -------------------------------------------------------------- > > cd /usr/src; make -f Makefile.inc1 install > > =3D=3D=3D> share/info > > =3D=3D=3D> include > > if [ -h /usr/include/cam ]; then rm -f /usr/include/cam; fi > > if [ -h /usr/include/msdosfs ]; then rm -f /usr/include/msdosfs; fi > > if [ -h /usr/include/net ]; then rm -f /usr/include/net; fi > > if [ -h /usr/include/netatalk ]; then rm -f /usr/include/netatalk; fi > > if [ -h /usr/include/netatm ]; then rm -f /usr/include/netatm; fi > > if [ -h /usr/include/netgraph ]; then rm -f /usr/include/netgraph; fi > > if [ -h /usr/include/netinet ]; then rm -f /usr/include/netinet; fi > > if [ -h /usr/include/netinet6 ]; then rm -f /usr/include/netinet6; fi > > if [ -h /usr/include/netipx ]; then rm -f /usr/include/netipx; fi > > if [ -h /usr/include/netkey ]; then rm -f /usr/include/netkey; fi > > if [ -h /usr/include/netnatm ]; then rm -f /usr/include/netnatm; fi > > if [ -h /usr/include/netncp ]; then rm -f /usr/include/netncp; fi > > if [ -h /usr/include/netns ]; then rm -f /usr/include/netns; fi > > if [ -h /usr/include/netsmb ]; then rm -f /usr/include/netsmb; fi > > if [ -h /usr/include/nfs ]; then rm -f /usr/include/nfs; fi > > if [ -h /usr/include/ntfs ]; then rm -f /usr/include/ntfs; fi > > if [ -h /usr/include/nwfs ]; then rm -f /usr/include/nwfs; fi > > if [ -h /usr/include/pccard ]; then rm -f /usr/include/pccard; fi > > if [ -h /usr/include/posix4 ]; then rm -f /usr/include/posix4; fi > > if [ -h /usr/include/sys ]; then rm -f /usr/include/sys; fi > > if [ -h /usr/include/vm ]; then rm -f /usr/include/vm; fi > > if [ -h /usr/include/fs/smbfs ]; then rm -f /usr/include/fs/smbfs; fi > > if [ -h /usr/include/isofs/cd9660 ]; then rm -f /usr/include/isofs/cd9= 660; fi > > if [ -h /usr/include/ufs/ffs ]; then rm -f /usr/include/ufs/ffs; fi > > if [ -h /usr/include/ufs/mfs ]; then rm -f /usr/include/ufs/mfs; fi > > if [ -h /usr/include/ufs/ufs ]; then rm -f /usr/include/ufs/ufs; fi > > if [ -h /usr/include/dev/ppbus ]; then rm -f /usr/include/dev/ppbus; = fi > > if [ -h /usr/include/dev/usb ]; then rm -f /usr/include/dev/usb; fi > > if [ -h /usr/include/machine ]; then rm -f /usr/include/machine; fi > > mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p /usr/i= nclude > > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*.h= /usr/include/cam > > Illegal instruction - core dumped > > *** Error code 132 > > > > Stop in /usr/src/include. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > # d=08 =08 > > > -- > Ruslan Ermilov=09=09Sysadmin and DBA, > ru@sunbay.com=09=09Sunbay Software AG, > ru@FreeBSD.org=09=09FreeBSD committer, > +380.652.512.251=09Simferopol, Ukraine > > http://www.FreeBSD.org=09The Power To Serve > http://www.oracle.com=09Enabling The Information Age > --0-1986994741-1022828783=:40770 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="make.conf" Content-Transfer-Encoding: BASE64 Content-ID: <20020531090623.W40770@thrawn.birch.se> Content-Description: Content-Disposition: attachment; filename="make.conf" IyAkRnJlZUJTRDogc3JjL2V0Yy9kZWZhdWx0cy9tYWtlLmNvbmYsdiAxLjk3 LjIuNjUgMjAwMi8wNS8xNSAxMjo1MToyNyBuZWN0YXIgRXhwICQNCiMNCiMg Tk9URTogIFBsZWFzZSB3b3VsZCBhbnkgY29tbWl0dGVyIHVwZGF0aW5nIHRo aXMgZmlsZSBhbHNvIHVwZGF0ZSB0aGUNCiMgbWFrZS5jb25mKDUpIG1hbnVh bCBwYWdlLCBpZiBuZWNlc3NhcnksIHdoaWNoIGlzIGxvY2F0ZWQgaW4NCiMg c3JjL3NoYXJlL21hbi9tYW41L21ha2UuY29uZi41Lg0KIw0KIyBUaGlzIGZp bGUsIGlmIHByZXNlbnQsIHdpbGwgYmUgcmVhZCBieSBtYWtlIChzZWUgL3Vz ci9zaGFyZS9tay9zeXMubWspLg0KIyBJdCBhbGxvd3MgeW91IHRvIG92ZXJy aWRlIG1hY3JvIGRlZmluaXRpb25zIHRvIG1ha2Ugd2l0aG91dCBjaGFuZ2lu Zw0KIyB5b3VyIHNvdXJjZSB0cmVlLCBvciBhbnl0aGluZyB0aGUgc291cmNl IHRyZWUgaW5zdGFsbHMuDQojDQojIFRoaXMgZmlsZSBtdXN0IGJlIGluIHZh bGlkIE1ha2VmaWxlIHN5bnRheC4NCiMNCiMgWW91IGhhdmUgdG8gZmluZCB0 aGUgdGhpbmdzIHlvdSBjYW4gcHV0IGhlcmUgaW4gdGhlIE1ha2VmaWxlcyBh bmQgDQojIGRvY3VtZW50YXRpb24gb2YgdGhlIHNvdXJjZSB0cmVlLg0KIw0K Iw0KIyBUaGUgQ1BVVFlQRSB2YXJpYWJsZSBjb250cm9scyB3aGljaCBwcm9j ZXNzb3Igc2hvdWxkIGJlIHRhcmdldHRlZCBmb3INCiMgZ2VuZXJhdGVkIGNv ZGUuICBUaGlzIGNvbnRyb2xzIHByb2Nlc3Nvci1zcGVjaWZpYyBvcHRpbWl6 YXRpb25zIGluDQojIGNlcnRhaW4gY29kZSAoY3VycmVudGx5IG9ubHkgT3Bl blNTTCkgYXMgd2VsbCBhcyBtb2RpZnlpbmcgdGhlIHZhbHVlDQojIG9mIENG TEFHUyB0byBjb250YWluIHRoZSBhcHByb3ByaWF0ZSBvcHRpbWl6YXRpb24g ZGlyZWN0aXZlIHRvIGdjYy4NCiMgVGhlIGF1dG9tYXRpYyBzZXR0aW5nIG9m IENGTEFHUyBtYXkgYmUgb3ZlcnJpZGRlbiB1c2luZyB0aGUNCiMgTk9fQ1BV X0NGTEFHUyB2YXJpYWJsZSBiZWxvdy4NCiMgQ3VycmVudGx5IHRoZSBmb2xs b3dpbmcgQ1BVIHR5cGVzIGFyZSByZWNvZ25pc2VkOg0KIyAgIEludGVsIHg4 NiBhcmNoaXRlY3R1cmU6DQojICAgICAgIChBTUQgQ1BVcykJazcgazYtMiBr NiBrNQ0KIyAgICAgICAoSW50ZWwgQ1BVcykJcDQgcDMgcDIgaTY4NiBpNTg2 L21teCBpNTg2IGk0ODYgaTM4Ng0KIyAgIEFscGhhL0FYUCBhcmNoaXRlY3R1 cmU6IGV2NiBwY2E1NiBldjU2IGV2NSBldjQ1IGV2NA0KIw0KIyBJZiB5b3Ug ZXhwZXJpZW5jZSBhbnkgcHJvYmxlbXMgYWZ0ZXIgc2V0dGluZyB0aGlzIGZs YWcsIHBsZWFzZSB1bnNldA0KIyBpdCBhZ2FpbiBiZWZvcmUgc3VibWl0dGlu ZyBhIGJ1ZyByZXBvcnQgb3IgYXR0ZW1wdGluZyB0byBtb2RpZnkgY29kZS4N CiMgSXQgbWF5IGJlIHRoYXQgY2VydGFpbiB0eXBlcyBvZiBzb2Z0d2FyZSB3 aWxsIGJlY29tZSB1bnN0YWJsZSBhZnRlciBiZWluZw0KIyBjb21waWxlZCB3 aXRoIHByb2Nlc3Nvci1zcGVjaWZpYyAob3IgaGlnaGVyIC0gc2VlIGJlbG93 KSBvcHRpbWl6YXRpb24gZmxhZ3MuDQojIElmIGluIGRvdWJ0LCBkbyBub3Qg c2V0IENQVVRZUEUgb3IgQ0ZMQUdTIHRvIG5vbi1kZWZhdWx0IHZhbHVlcy4N CiMNCkNQVVRZUEU9aTU4Ng0KI05PX0NQVV9DRkxBR1M9CXRydWUJIyBEb24n dCBhZGQgLW1hcmNoPTxjcHU+IHRvIENGTEFHUyBhdXRvbWF0aWNhbGx5DQoj Tk9fQ1BVX0NPUFRGTEFHUz10cnVlCSMgRG9uJ3QgYWRkIC1tYXJjaD08Y3B1 PiB0byBDT1BURkxBR1MgYXV0b21hdGljYWxseQ0KIw0KIyBDRkxBR1MgY29u dHJvbHMgdGhlIGNvbXBpbGVyIHNldHRpbmdzIHVzZWQgd2hlbiBjb21waWxp bmcgQyBjb2RlLg0KIyBOb3RlIHRoYXQgb3B0aW1pemF0aW9uIHNldHRpbmdz IGFib3ZlIC1PICgtTzIsIC4uLikgYXJlIG5vdCByZWNvbW1lbmRlZA0KIyBv ciBzdXBwb3J0ZWQgZm9yIGNvbXBpbGluZyB0aGUgd29ybGQgb3IgdGhlIGtl cm5lbCAtIHBsZWFzZSByZXZlcnQgYW55DQojIG5vbnN0YW5kYXJkIG9wdGlt aXphdGlvbiBzZXR0aW5ncyB0byAiLU8iIGJlZm9yZSBzdWJtaXR0aW5nIGJ1 ZyByZXBvcnRzDQojIHRvIHRoZSBkZXZlbG9wZXJzLg0KIyBOb3RlIGFsc28g dGhhdCBhdCB0aGlzIHRpbWUgdGhlIC1PMiBzZXR0aW5nIGlzIGtub3duIHRv IHByb2R1Y2UgQlJPS0VODQojIENPREUgb24gdGhlIEFscGhhIHBsYXRmb3Jt Lg0KIw0KQ0ZMQUdTPSAtTyAtcGlwZSAtbWFyY2g9aTU4Ng0KIw0KIyBDWFhG TEFHUyBjb250cm9scyB0aGUgY29tcGlsZXIgc2V0dGluZ3MgdXNlZCB3aGVu IGNvbXBpbGluZyBDKysgY29kZS4NCiMgTm90ZSB0aGF0IENYWEZMQUdTIGlz IGluaXRpYWxseSBzZXQgdG8gdGhlIHZhbHVlIG9mIENGTEFHUy4gIElmIHlv dSB3aXNoDQojIHRvIGFkZCB0byBDWFhGTEFHUyB2YWx1ZSwgIis9IiBtdXN0 IGJlIHVzZWQgcmF0aGVyIHRoYW4gIj0iLiAgVXNpbmcgIj0iDQojIGFsb25l IHdpbGwgcmVtb3ZlIHRoZSBvZnRlbiBuZWVkZWQgY29udGVudHMgb2YgQ0ZM QUdTIGZyb20gQ1hYRkxBR1MuDQojDQojQ1hYRkxBR1MrPSAtZm1lbW9pemUt bG9va3VwcyAtZnNhdmUtbWVtb2l6ZWQNCiMNCiMgQkRFQ0ZMQUdTIGFyZSBh IHNldCBvZiBnY2Mgd2FybmluZyBzZXR0aW5ncyB0aGF0IEJydWNlIEV2YW5z IGhhcyBzdWdnZXN0ZWQNCiMgZm9yIHVzZSBpbiBkZXZlbG9waW5nIEZyZWVC U0QgYW5kIHRlc3RpbmcgY2hhbmdlcy4gIFRoZXkgY2FuIGJlIHVzZWQgYnkN CiMgcHV0dGluZyAiQ0ZMQUdTKz0ke0JERUNGTEFHU30iIGluIC9ldGMvbWFr ZS5jb25mLiAgLVdjb252ZXJzaW9uIGlzIG5vdA0KIyBpbmNsdWRlZCBoZXJl IGR1ZSB0byBjb21waWxlciBidWdzLCBlZzogbWtkaXIoKSdzIG1vZGVfdCBh cmd1bWVudC4NCiMNCkJERUNGTEFHUz0JLVcgLVdhbGwgLWFuc2kgLXBlZGFu dGljIC1XYmFkLWZ1bmN0aW9uLWNhc3QgLVdjYXN0LWFsaWduIFwNCgkJLVdj YXN0LXF1YWwgLVdjaGFyLXN1YnNjcmlwdHMgLVdpbmxpbmUgXA0KCQktV21p c3NpbmctcHJvdG90eXBlcyAtV25lc3RlZC1leHRlcm5zIC1XcG9pbnRlci1h cml0aCBcDQoJCS1XcmVkdW5kYW50LWRlY2xzIC1Xc2hhZG93IC1Xc3RyaWN0 LXByb3RvdHlwZXMgLVd3cml0ZS1zdHJpbmdzDQojDQojIFdBUk5TX1dFUlJP UiBjYXVzZXMgLVdlcnJvciB0byBiZSBhZGRlZCB3aGVuIFdBUk5TIGlzIGlu IGVmZmVjdC4NCiMNCiNXQVJOU19XRVJST1I9CXllcw0KIw0KIyBUbyBjb21w aWxlIGp1c3QgdGhlIGtlcm5lbCB3aXRoIHNwZWNpYWwgb3B0aW1pemF0aW9u cywgeW91IHNob3VsZCB1c2UNCiMgdGhpcyBpbnN0ZWFkIG9mIENGTEFHUyAo d2hpY2ggaXMgbm90IGFwcGxpY2FibGUgdG8ga2VybmVsIGJ1aWxkcyBhbnl3 YXkpLg0KIyBUaGVyZSBpcyB2ZXJ5IGxpdHRsZSB0byBnYWluIGJ5IHVzaW5n IGhpZ2hlciBvcHRpbWl6YXRpb24gbGV2ZWxzLCBhbmQgZG9pbmcNCiMgc28g Y2FuIGNhdXNlIHByb2JsZW1zLg0KIw0KI0NPUFRGTEFHUz0gLU8gLXBpcGUN CiMNCiMgQ29tcGFyZSBiZWZvcmUgaW5zdGFsbA0KI0lOU1RBTEw9aW5zdGFs bCAtQw0KIw0KIyBUbyBlbmFibGUgaW5zdGFsbGluZyBzdWlkcGVybCB3aXRo IHRoZSBzZXR1aWQgYml0IHR1cm5lZCBvbg0KI0VOQUJMRV9TVUlEUEVSTD0J dHJ1ZQ0KIw0KIyBUbyBidWlsZCBwcHAgd2l0aCBub3JtYWwgcGVybWlzc2lv bnMNCiNQUFBfTk9TVUlEPQl0cnVlDQojDQojIFRvIGVuYWJsZSBpbnN0YWxs aW5nIHNzaCgxKSB3aXRoIHRoZSBzZXR1aWQgYml0IHR1cm5lZCBvbg0KI0VO QUJMRV9TVUlEX1NTSD0JdHJ1ZQ0KIw0KIyBUbyBhdm9pZCBidWlsZGluZyB2 YXJpb3VzIHBhcnRzIG9mIHRoZSBiYXNlIHN5c3RlbToNCiNOT19DVlM9CXRy dWUJIyBkbyBub3QgYnVpbGQgQ1ZTDQpOT19CSU5EPQl0cnVlCSMgZG8gbm90 IGJ1aWxkIEJJTkQNCk5PX0ZPUlRSQU49CXRydWUJIyBkbyBub3QgYnVpbGQg Zzc3IGFuZCByZWxhdGVkIGxpYnJhcmllcw0KTk9fSTRCPQl0cnVlCSMgZG8g bm90IGJ1aWxkIGlzZG40YnNkIHBhY2thZ2UNCk5PX0xQUj0JdHJ1ZQkjIGRv IG5vdCBidWlsZCBscHIgYW5kIHJlbGF0ZWQgcHJvZ3JhbXMNCiNOT19NQUlM V1JBUFBFUj10cnVlCSMgZG8gbm90IGJ1aWxkIHRoZSBtYWlsd3JhcHBlcig4 KSBNVEEgc2VsZWN0b3INCiNOT19NT0RVTEVTPQl0cnVlCSMgZG8gbm90IGJ1 aWxkIG1vZHVsZXMgd2l0aCB0aGUga2VybmVsDQojTk9fT0JKQz0JdHJ1ZQkj IGRvIG5vdCBidWlsZCBPYmplY3RpdmUgQyBzdXBwb3J0DQpOT19PUEVOU1NI PQl0cnVlCSMgZG8gbm90IGJ1aWxkIE9wZW5TU0gNCiNOT19PUEVOU1NMPQl0 cnVlCSMgZG8gbm90IGJ1aWxkIE9wZW5TU0wgKGltcGxpZXMgTk9fT1BFTlNT SCkNCk5PX1NFTkRNQUlMPQl0cnVlCSMgZG8gbm90IGJ1aWxkIHNlbmRtYWls IGFuZCByZWxhdGVkIHByb2dyYW1zDQojTk9fU0hBUkVET0NTPQl0cnVlCSMg ZG8gbm90IGJ1aWxkIHRoZSA0LjRCU0QgbGVnYWN5IGRvY3MNCiNOT19UQ1NI PQl0cnVlCSMgZG8gbm90IGJ1aWxkIGFuZCBpbnN0YWxsIC9iaW4vY3NoICh3 aGljaCBpcyB0Y3NoKQ0KTk9fWD0JCXRydWUJIyBkbyBub3QgY29tcGlsZSBp biBYV2luZG93cyBzdXBwb3J0IChlLmcuIGRvc2NtZCkNCiNOT0NSWVBUPQl0 cnVlCSMgZG8gbm90IGJ1aWxkIGFueSBjcnlwdG8gY29kZQ0KI05PR0FNRVM9 CXRydWUJIyBkbyBub3QgYnVpbGQgZ2FtZXMgKGdhbWVzLyBzdWJkaXIpDQoj Tk9JTkZPPQl0cnVlCSMgZG8gbm90IG1ha2Ugb3IgaW5zdGFsbCBpbmZvIGZp bGVzDQojTk9MSUJDX1I9CXRydWUJIyBkbyBub3QgYnVpbGQgbGliY19yIChy ZS1lbnRyYW50IHZlcnNpb24gb2YgbGliYykNCiNOT1BFUkw9CXRydWUJIyBk byBub3QgYnVpbGQgcGVybC4gRGlzYWJsZXMgT3BlblNTTCBvcHRpbWl6YXRp b25zDQpOT1BST0ZJTEU9CXRydWUJIyBBdm9pZCBjb21waWxpbmcgcHJvZmls ZWQgbGlicmFyaWVzDQojTk9TRUNVUkU9CXRydWUJIyBkbyBub3QgYnVpbGQg Y3J5cHRvIGNvZGUgaW4gc2VjdXJlLyBzdWJkaXINCiNOT1NIQVJFPQl0cnVl CSMgZG8gbm90IGdvIGludG8gdGhlIHNoYXJlIHN1YmRpcg0KTk9VVUNQPQl0 cnVlCSMgZG8gbm90IGJ1aWxkIHV1Y3AgcmVsYXRlZCBwcm9ncmFtcw0KIw0K IyBUbyBidWlsZCB0aGUgT3BlblNTTCBtYW5wYWdlcywgdW5jb21tZW50IHRo ZSBmb2xsb3dpbmcuICBUaGVzZSBhcmUgbm90DQojIGJ1aWx0IGJ5IGRlZmF1 bHQgYmVjYXVzZSB0aGV5IGNsb2JiZXIgYSBudW1iZXIgb2Ygc3lzdGVtIG1h bnBhZ2VzIHdpdGgNCiMgbWFucGFnZXMgZGVzY3JpYmluZyBwYXJ0cyBvZiB0 aGUgT3BlblNTTCB0b29sa2l0LCBpbmNsdWRpbmcgcGFzc3dkKDEpLA0KIyBl cnIoMyksIG1kNSgzKSwgYW5kIG90aGVycy4NCiMNCiNXQU5UX09QRU5TU0xf TUFOUEFHRVM9CXRydWUNCiMNCiMgVG8gYnVpbGQgc3lzL21vZHVsZXMgd2hl biBidWlsZGluZyB0aGUgd29ybGQgKG91ciBvbGQgd2F5IG9mIGRvaW5nIHRo aW5ncykNCiNNT0RVTEVTX1dJVEhfV09STEQ9dHJ1ZQkjIGRvIG5vdCBidWls ZCBtb2R1bGVzIHdoZW4gYnVpbGRpbmcga2VybmVsDQojDQojDQojIFRoZSBm b2xsb3dpbmcgY29udHJvbHMgYnVpbGRpbmcgb3B0aW9uYWwgSURFQSBjb2Rl IGluIGxpYmNyeXB0byBhbmQNCiMgY2VydGFpbiBwb3J0cy4gIFBhdGVudHMg YXJlIGludm9sdmVkIC0geW91IG11c3Qgbm90IHVzZSB0aGlzIHVubGVzcw0K IyB5b3UgZWl0aGVyIGhhdmUgYSBsaWNlbnNlIG9yIGZhbGwgd2l0aGluIHBh dGVudCAnZmFpciB1c2UnDQojIHByb3Zpc2lvbnMuDQojDQojICoqKiBJdCBp cyBZT1VSIFJFU1BPTlNJQklMSVRZIHRvIGRldGVybWluZSBpZiB5b3UgY2Fu IHVzZSB0aGlzISAqKioNCiMNCiMgSURFQSBpcyBwYXRlbnRlZCBpbiB0aGUg VVNBIGFuZCBtYW55IGV1cm9wZWFuIGNvdW50cmllcyAtIHRob3VnaHQgdG8N CiMgYmUgT0sgdG8gdXNlIGZvciBhbnkgbm9uLWNvbW1lcmNpYWwgdXNlLiAg VGhpcyBpcyBvcHRpb25hbC4NCiNNQUtFX0lERUE9CVlFUwkjIElERUEgKDEy OCBiaXQgc3ltbWV0cmljIGVuY3J5cHRpb24pDQojDQojIFRvIGF2b2lkIHJ1 bm5pbmcgTUFLRURFViBhbGwgb24gL2RldiBkdXJpbmcgaW5zdGFsbDoNCiNO T19NQUtFREVWPQl0cnVlDQojDQojIElmIHlvdSBkbyBub3Qgd2FudCB1bmZv cm1hdHRlZCBtYW51YWwgcGFnZXMgdG8gYmUgY29tcHJlc3NlZA0KIyB3aGVu IHRoZXkgYXJlIGluc3RhbGxlZDoNCiMNCiNOT01BTkNPTVBSRVNTPQl0cnVl DQojDQojDQojIElmIHlvdSB3YW50IHRoZSAiY29tcGF0IiBzaGFyZWQgbGli cmFyaWVzIGluc3RhbGxlZCBhcyBwYXJ0IG9mIHlvdXIgbm9ybWFsDQojIGJ1 aWxkcywgdW5jb21tZW50IHRoZXNlOg0KIw0KI0NPTVBBVDFYPQl5ZXMNCiND T01QQVQyMD0JeWVzDQojQ09NUEFUMjE9CXllcw0KI0NPTVBBVDIyPQl5ZXMN CiNDT01QQVQzWD0JeWVzDQojQ09NUEFUNFg9CXllcw0KIw0KIw0KIyBJZiB5 b3UgZG8gbm90IHdhbnQgYWRkaXRpb25hbCBkb2N1bWVudGF0aW9uIChzb21l IG9mIHdoaWNoIGFyZQ0KIyBhIGZldyBodW5kcmVkIEtCJ3MpIGZvciBwb3J0 cyB0byBiZSBpbnN0YWxsZWQ6DQojDQojTk9QT1JURE9DUz0JdHJ1ZQ0KIw0K Iw0KIyBEZWZhdWx0IGZvcm1hdCBmb3Igc3lzdGVtIGRvY3VtZW50YXRpb24s IGRlcGVuZHMgb24geW91ciBwcmludGVyLg0KIyBTZXQgdGhpcyB0byAiYXNj aWkiIGZvciBzaW1wbGUgcHJpbnRlcnMgb3Igc2NyZWVuDQojDQojUFJJTlRF UkRFVklDRT0JcHMNCiMNCiMNCiMgSG93IGxvbmcgdG8gd2FpdCBmb3IgYSBj b25zb2xlIGtleXByZXNzIGJlZm9yZSBib290aW5nIHRoZSBkZWZhdWx0IGtl cm5lbC4NCiMgVGhpcyB2YWx1ZSBpcyBhcHByb3hpbWF0ZWx5IGluIG1pbGxp c2Vjb25kcy4gS2V5cHJlc3NlcyBhcmUgYWNjZXB0ZWQgYnkgdGhlDQojIEJJ T1MgYmVmb3JlIGJvb3RpbmcgZnJvbSBkaXNrLCBtYWtpbmcgaXQgcG9zc2li bGUgdG8gZ2l2ZSBjdXN0b20gYm9vdA0KIyBwYXJhbWV0ZXJzIGV2ZW4gd2hl biB0aGlzIGlzIHNldCB0byAwLg0KIw0KI0JPT1RXQUlUPTANCiNCT09UV0FJ VD0zMDAwMA0KIw0KIyBCeSBkZWZhdWx0LCB0aGUgc3lzdGVtIHdpbGwgYWx3 YXlzIHVzZSB0aGUga2V5Ym9hcmQvdmlkZW8gY2FyZCBhcyBzeXN0ZW0NCiMg Y29uc29sZS4gIEhvd2V2ZXIsIHRoZSBib290IGJsb2NrcyBtYXkgYmUgZHlu YW1pY2FsbHkgY29uZmlndXJlZCB0byB1c2UgYQ0KIyBzZXJpYWwgcG9ydCBp biBhZGRpdGlvbiB0byBvciBpbnN0ZWFkIG9mIHRoZSBrZXlib2FyZC92aWRl byBjb25zb2xlLg0KIw0KIyBCeSBkZWZhdWx0IHdlIHVzZSBDT00xIGFzIG91 ciBzZXJpYWwgY29uc29sZSBwb3J0ICppZiogd2UncmUgZ29pbmcgdG8gdXNl DQojIGEgc2VyaWFsIHBvcnQgYXMgb3VyIGNvbnNvbGUgYXQgYWxsLiAgQWx0 ZXIgYXMgbmVjZXNzYXJ5Lg0KIw0KIyAgIENPTTE6ID0gMHgzRjgsIENPTTI6 ID0gMHgyRjgsIENPTTM6ID0gMHgzRTgsIENPTTQ6ID0gMHgyRTgNCiMNCiNC T09UX0NPTUNPTlNPTEVfUE9SVD0JMHgzRjgNCiMNCiMgVGhlIGRlZmF1bHQg c2VyaWFsIGNvbnNvbGUgc3BlZWQgaXMgOTYwMC4gIFNldCB0aGUgc3BlZWQg dG8gYSBsYXJnZXIgdmFsdWUNCiMgZm9yIGJldHRlciBpbnRlcmFjdGl2ZSBy ZXNwb25zZS4NCiMNCiNCT09UX0NPTUNPTlNPTEVfU1BFRUQ9CTExNTIwMA0K Iw0KIyBCeSBkZWZhdWx0IHRoZSAncHhlYm9vdCcgbG9hZGVyIHJldHJpZXZl cyB0aGUga2VybmVsIHZpYSBORlMuICBEZWZpbmluZw0KIyB0aGlzIGFuZCBy ZWNvbXBpbGluZyAvdXNyL3NyYy9zeXMvYm9vdCB3aWxsIGNhdXNlIGl0IHRv IHJldHJpZXZlIHRoZSBrZXJuZWwNCiMgdmlhIFRGVFAuICBUaGlzIGFsbG93 cyBweGVib290IHRvIGxvYWQgYSBjdXN0b20gQk9PVFAgZGlza2xlc3Mga2Vy bmVsIHlldA0KIyBzdGlsbCBtb3VudCB0aGUgc2VydmVyJ3MgJy8nIChpLmUu IHJhdGhlciB0aGVuIGxvYWQgdGhlIHNlcnZlcidzIGtlcm5lbCkuDQojDQoj TE9BREVSX1RGVFBfU1VQUE9SVD0gWUVTDQojDQojIEJ5IGRlZmF1bHQsIHRo ZSBwb3J0cyBjb2xsZWN0aW9uIGF0dGVtcHRzIHRvIHVzZSBYRnJlZTg2IDMu My5YLiAgSWYNCiMgeW91IGFyZSBydW5uaW5nIFhGcmVlODYgNC5YLCB1bmNv bW1lbnQgdGhpcyBsaW5lLg0KIw0KWEZSRUU4Nl9WRVJTSU9OPQkzDQojDQoj IEJ5IGRlZmF1bHQsIHRoaXMgcG9pbnRzIHRvIC91c3IvWDExUjYgZm9yIFhG cmVlODYgcmVsZWFzZXMgMy4wIG9yIGVhcmxpZXIuDQojIElmIHlvdSBoYXZl IGEgWEZyZWU4NiBmcm9tIGJlZm9yZSAzLjAgdGhhdCBoYXMgdGhlIFggZGlz dHJpYnV0aW9uIGluDQojIC91c3IvWDM4NiwgeW91IHdhbnQgdG8gdW5jb21t ZW50IHRoaXMuDQojDQojWDExQkFTRT0JL3Vzci9YMzg2DQojDQojDQojIElm IHlvdSBoYXZlIE1vdGlmIG9uIHlvdXIgc3lzdGVtLCB1bmNvbW1lbnQgdGhp cy4NCiMNCiNIQVZFX01PVElGPQl5ZXMNCiNNT1RJRl9TVEFUSUM9ICB5ZXMN CiMNCiMgSWYgdGhlIGRlZmF1bHQgbG9jYXRpb24gb2YgdGhlIE1vdGlmIGxp YnJhcnkgKHNwZWNpZmllZCBiZWxvdykgaXMgTk9UDQojIGFwcHJvcHJpYXRl IGZvciB5b3UsIHVuY29tbWVudCB0aGlzIGFuZCBjaGFuZ2UgaXQgdG8gdGhl IGNvcnJlY3QgdmFsdWUuDQojIElmIHlvdXIgbW90aWYgaXMgaW4gJHtYMTFC QVNFfS9saWIsIHlvdSBkb24ndCBuZWVkIHRvIHRvdWNoIHRoaXMgbGluZS4N CiMNCiNNT1RJRkxJQj0JLUwke1gxMUJBU0V9L2xpYiAtbFhtDQojDQojDQoj IElmIHlvdSdyZSByZXNpZGVudCBpbiB0aGUgVVNBLCB0aGlzIHdpbGwgaGVs cCB2YXJpb3VzIHBvcnRzIHRvIGRldGVybWluZQ0KIyB3aGV0aGVyIG9yIG5v dCB0aGV5IHNob3VsZCBhdHRlbXB0IHRvIGNvbXBseSB3aXRoIHRoZSB2YXJp b3VzIFUuUy4NCiMgZXhwb3J0IHJlZ3VsYXRpb25zIG9uIGNlcnRhaW4gdHlw ZXMgb2Ygc29mdHdhcmUgd2hpY2ggZG8gbm90IGFwcGx5IHRvDQojIGFueW9u ZSBlbHNlIGluIHRoZSB3b3JsZC4NCiMNCiNVU0FfUkVTSURFTlQ9CQlZRVMN CiMNCiMNCiMgT3ZlcnJpZGUgImRvbid0IGluc3RhbGwgYSBwb3J0IHRoYXQn cyBhbHJlYWR5IGluc3RhbGxlZCIgYmVoYXZpb3IuDQojIE9uZSBtaWdodCB3 aXNoIHRvIGRvIHRoaXMgZm9yIHBvcnRzIGRlYnVnZ2luZyBvciB0byB1bmNv bmRpdGlvbmFsbHkNCiMgcmVpbnN0YWxsIGEgc2V0IG9mIHN1c3BlY3QvYnJv a2VuIHBvcnRzLg0KIw0KI0ZPUkNFX1BLR19SRUdJU1RFUj0gICAgWUVTDQoj DQojDQojIElmIHlvdSdyZSBiZWhpbmQgYSBmaXJld2FsbCBhbmQgbmVlZCBG VFAgb3IgSFRUUCBwcm94eSBzZXJ2aWNlcyBmb3INCiMgcG9ydHMgY29sbGVj dGlvbiBmZXRjaGluZyB0byB3b3JrLCB0aGUgZm9sbG93aW5nIGV4YW1wbGVz IGdpdmUgdGhlDQojIG5lY2Vzc2FyeSBzeW50YXguICBTZWUgdGhlIGZldGNo KDMpIG1hbiBwYWdlIGZvciBkZXRhaWxzLg0KIw0KI0ZFVENIX0VOVj0JRlRQ X1BST1hZPWZ0cDovLzEwLjAuMC4xOjIxDQojRkVUQ0hfRU5WPQlIVFRQX1BS T1hZPWh0dHA6Ly8xMC4wLjAuMTo4MA0KIw0KIw0KIyBQb3J0IG1hc3RlciBz aXRlcy4NCiMNCiMgSWYgeW91IHdhbnQgeW91ciBwb3J0IGZldGNoZXMgdG8g Z28gc29tZXdoZXJlIGVsc2UgdGhhbiB0aGUgZGVmYXVsdA0KIyAoc3BlY2lm aWVkIGJlbG93KSBpbiBjYXNlIHRoZSBkaXN0ZmlsZS9wYXRjaGZpbGUgd2Fz IG5vdCBmb3VuZCwNCiMgdW5jb21tZW50IHRoaXMgYW5kIGNoYW5nZSBpdCB0 byBhIGxvY2F0aW9uIG5lYXJlc3QgeW91LiAgKERvbid0DQojIHJlbW92ZSB0 aGUgIi8ke0RJU1RfU1VCRElSfS8iIHBhcnQuKQ0KIw0KI01BU1RFUl9TSVRF X0JBQ0tVUD89CVwNCiMJZnRwOi8vZnRwLmZyZWVic2Qub3JnL3B1Yi9GcmVl QlNEL3BvcnRzL2Rpc3RmaWxlcy8ke0RJU1RfU1VCRElSfS8NCiMNCiMgSWYg eW91IHdhbnQgeW91ciBwb3J0IGZldGNoZXMgdG8gY2hlY2sgdGhlIGFib3Zl IHNpdGUgZmlyc3QgKGJlZm9yZQ0KIyB0aGUgTUFTVEVSX1NJVEVTIHNwZWNp ZmllZCBpbiB0aGUgcG9ydCBNYWtlZmlsZXMpLCB1bmNvbW1lbnQgdGhlDQoj IGxpbmUgYmVsb3cuICBZb3UgY2FuIGFsc28gY2hhbmdlIHRoZSByaWdodCBz aWRlIHRvIHBvaW50IHRvIHdoZXJldmVyIA0KIyB5b3Ugd2FudC4NCiMNCiNN QVNURVJfU0lURV9PVkVSUklERT89CSR7TUFTVEVSX1NJVEVfQkFDS1VQfQ0K Iw0KIyBTb21lIHBvcnRzIHVzZSBhIHNwZWNpYWwgdmFyaWFibGUgdG8gcG9p bnQgdG8gYSBjb2xsZWN0aW9uIG9mDQojIG1pcnJvcnMgb2Ygd2VsbC1rbm93 biBzb2Z0d2FyZSBhcmNoaXZlcy4gIElmIHlvdSBoYXZlIGEgbWlycm9yIGNs b3NlDQojIHRvIHlvdSwgdW5jb21tZW50IGFueSBvZiB0aGUgZm9sbG93aW5n IGxpbmVzIGFuZCBjaGFuZ2UgaXQgdG8gdGhhdA0KIyBhZGRyZXNzLiAgKERv bid0IHJlbW92ZSB0aGUgIi8lU1VCRElSJS8iIHBhcnQuKQ0KIw0KIyBOb3Rl OiB0aGUgcmlnaHQgaGFuZCBzaWRlcyBvZiB0aGUgZm9sbG93aW5nIGxpbmVz IGFyZSBvbmx5IGZvciB5b3VyDQojIGluZm9ybWF0aW9uLiAgRm9yIGEgZnVs bCBsaXN0IG9mIGRlZmF1bHQgc2l0ZXMsIHRha2UgYSBsb29rIGF0DQojIGJz ZC5zaXRlcy5tay4NCiMNCiNNQVNURVJfU0lURV9BRlRFUlNURVA9CWZ0cDov L2Z0cC5hZnRlcnN0ZXAub3JnLyVTVUJESVIlLw0KI01BU1RFUl9TSVRFX0NP TVBfU09VUkNFUz0JZnRwOi8vZ2F0ZWtlZXBlci5kZWMuY29tL3B1Yi91c2Vu ZXQvY29tcC5zb3VyY2VzLiVTVUJESVIlLw0KI01BU1RFUl9TSVRFX0ZSRUVC U0RfT1JHPSAgICAgIGZ0cDovL2Z0cC5GcmVlQlNELm9yZy9wdWIvRnJlZUJT RC8lU1VCRElSJS8NCiNNQVNURVJfU0lURV9HTk9NRT0JZnRwOi8vZnRwLmdu b21lLm9yZy9wdWIvR05PTUUvJVNVQkRJUiUvDQojTUFTVEVSX1NJVEVfR05V PQlmdHA6Ly9mdHAuZ251Lm9yZy9nbnUvJVNVQkRJUiUvDQojTUFTVEVSX1NJ VEVfS0RFPQlmdHA6Ly9mdHAua2RlLm9yZy9wdWIva2RlLyVTVUJESVIlLw0K I01BU1RFUl9TSVRFX0xPQ0FMPQlmdHA6Ly9mdHAuRnJlZUJTRC5vcmcvcHVi L0ZyZWVCU0QvcG9ydHMvbG9jYWwtZGlzdGZpbGVzLyVTVUJESVIlLw0KI01B U1RFUl9TSVRFX01PWklMTEE9CWZ0cDovL2Z0cC5tb3ppbGxhLm9yZy9wdWIv JVNVQkRJUiUvDQojTUFTVEVSX1NJVEVfTkVUQlNEPQlmdHA6Ly9mdHAubmV0 YnNkLm9yZy9wdWIvTmV0QlNEL3BhY2thZ2VzL2Rpc3RmaWxlcy8lU1VCRElS JS8NCiNNQVNURVJfU0lURV9QRVJMX0NQQU49CWZ0cDovL2Z0cC5kaWdpdGFs LmNvbS9wdWIvcGxhbi9wZXJsL0NQQU4vbW9kdWxlcy9ieS1tb2R1bGUvJVNV QkRJUiUvDQojTUFTVEVSX1NJVEVfUE9SVFNfSlA9CWZ0cDovL3BvcnRzLmpw LkZyZWVCU0Qub3JnL3B1Yi9GcmVlQlNELWpwL3BvcnRzLWpwL0xPQ0FMX1BP UlRTLyVTVUJESVIlLw0KI01BU1RFUl9TSVRFX1JJTkdTRVJWRVI9CWZ0cDov L2Z0cC5kbnNiYWxhbmNlLnJpbmcuZ3IuanAvcHViLyVTVUJESVIlLw0KI01B U1RFUl9TSVRFX1JVQlk9ICAgICBmdHA6Ly9mdHAucnVieS1sYW5nLm9yZy9w dWIvcnVieS8lU1VCRElSJS8NCiNNQVNURVJfU0lURV9TT1VSQ0VGT1JHRT0J ZnRwOi8vZnRwMi5zb3VyY2Vmb3JnZS5uZXQvcHViL3NvdXJjZWZvcmdlLyVT VUJESVIlLw0KI01BU1RFUl9TSVRFX1NPVVJDRVdBUkU9CWZ0cDovL2Z0cC5m cmVlc29mdHdhcmUuY29tL3B1Yi9zb3VyY2V3YXJlLyVTVUJESVIlLw0KI01B U1RFUl9TSVRFX1NVTlNJVEU9CWZ0cDovL21ldGFsYWIudW5jLmVkdS9wdWIv TGludXgvJVNVQkRJUiUvDQojTUFTVEVSX1NJVEVfVENMVEs9CWZ0cDovL2Z0 cC5zY3JpcHRpY3MuY29tL3B1Yi90Y2wvJVNVQkRJUiUvDQojTUFTVEVSX1NJ VEVfVEVYX0NUQU49CWZ0cDovL2Z0cC50ZXguYWMudWsvdGV4LWFyY2hpdmUv JVNVQkRJUiUvDQojTUFTVEVSX1NJVEVfVEhFTUVTPQlmdHA6Ly9mdHAudGhl bWVzLm9yZy9wdWIvdGhlbWVzLyVTVUJESVIlLw0KI01BU1RFUl9TSVRFX1dJ TkRPV01BS0VSPQlmdHA6Ly9mdHAud2luZG93bWFrZXIub3JnL3B1Yi8lU1VC RElSJS8NCiNNQVNURVJfU0lURV9YQ09OVFJJQj0JZnRwOi8vZnRwLngub3Jn L2NvbnRyaWIvJVNVQkRJUiUvDQojTUFTVEVSX1NJVEVfWEVNQUNTPQlmdHA6 Ly9mdHAueGVtYWNzLm9yZy9wdWIveGVtYWNzLyVTVUJESVIlLw0KI01BU1RF Ul9TSVRFX1hGUkVFPQlmdHA6Ly9mdHAueGZyZWU4Ni5vcmcvcHViL1hGcmVl ODYvJVNVQkRJUiUvc291cmNlLw0KIw0KIyBBbHNvIGl0IGlzIGhpZ2hseSBy ZWNvbW1lbmRlZCB0aGF0IHlvdSBjb25maWd1cmUgTUFTVEVSX1NPUlRfUkVH RVgNCiMgdG8gY2hvb3NlIGJldHRlciBtaXJyb3Igc2l0ZXMgZm9yIHlvdS4g IExpc3QgYXdrKDEpLXN0eWxlIHJlZ3VsYXINCiMgZXhwcmVzc2lvbnMgc2Vw YXJhdGVkIGJ5IHNwYWNlIHNvIE1BU1RFUl9TSVRFUyB3aWxsIGJlIHNvcnRl ZCBpbg0KIyB0aGF0IG9yZGVyLiAgVGhlIGZvbGxvd2luZyBleGFtcGxlIGlz IGZvciBKYXBhbmVzZSB1c2VyczsgY2hhbmdlDQojICJqcCIgcGFydCB0byB5 b3VyIGNjVExEICgiZGUiLCAicnUiLCAidWsiLCBldGMuKSBvciB0aGUgZG9t YWluIG5hbWVzDQojIG9mIHlvdXIgbmVhcmVzdC91cHN0cmVhbSBuZXR3b3Jr cyB0byBtZWV0IHlvdXIgbmVlZHMuDQojDQojTUFTVEVSX1NPUlRfUkVHRVg/ PQleZmlsZTogXmZ0cDovL2Z0cFwuRnJlZUJTRFwub3JnL3B1Yi9GcmVlQlNE L3BvcnRzL2xvY2FsLWRpc3RmaWxlcy8gOi8vW14vXSpcLmpwLyA6Ly9bXi9d KlwuanBcLg0KIw0KIyBQb3J0cyBjYW4gcGxhY2UgdGhlaXIgd29ya2luZyBk aXJlY3RvcmllcyBzb21ld2hlcmUgb3RoZXIgdGhhbiB1bmRlciANCiMgL3Vz ci9wb3J0cy4gIA0KI1dSS0RJUlBSRUZJWD0JL3Zhci90bXANCiMNCiMgS2Vy YmVyb3MgSVYNCiMgSWYgeW91IHdhbnQgS2VyYmVyb3NJViAoS1RIIGVCb25l cyksIGRlZmluZSB0aGlzOg0KIw0KI01BS0VfS0VSQkVST1M0PQl5ZXMNCiMN CiMNCiMgS2VyYmVyb3MgNQ0KIyBJZiB5b3Ugd2FudCBLZXJiZXJvcyA1IChL VEggSGVpbWRhbCksIGRlZmluZSB0aGlzOg0KIw0KI01BS0VfS0VSQkVST1M1 PQl5ZXMNCiMNCiMgS2VyYmVyb3MgNSBzdSAoazVzdSkNCiMgSWYgeW91IHdh bnQgdG8gdXNlIHRoZSBrNXN1IHV0aWxpdHksIGRlZmluZSB0aGlzIHRvIGhh dmUgaXQgaW5zdGFsbGVkDQojIHNldC11c2VyLUlELg0KI0VOQUJMRV9TVUlE X0s1U1U9CXllcw0KIw0KIw0KIyBLZXJiZXJvczUNCiMgSWYgeW91IHdhbnQg dG8gaW5zdGFsbCBNSVQgS2VyYmVyb3M1IHBvcnQgc29tZXdoZXJlIG90aGVy IHRoYW4gL3Vzci9sb2NhbCwNCiMgZGVmaW5lIHRoaXMgKHRoaXMgaXMgYWxz byB1c2VkIHRvIHRlbGwgc3NoMSB0aGF0IGtlcmJlcm9zIGlzIG5lZWRlZCk6 DQojDQojS1JCNV9IT01FPQkJL3Vzci9sb2NhbA0KIw0KIw0KIyBDVlN1cCB1 cGRhdGUgZmxhZ3MuICBFZGl0IFNVUEZJTEUgc2V0dGluZ3MgdG8gcmVmbGVj dCB3aGljaGV2ZXIgZGlzdHJpYnV0aW9uDQojIGZpbGUocykgeW91IHVzZSBv biB5b3VyIHNpdGUgKHNlZSAvdXNyL3NoYXJlL2V4YW1wbGVzL2N2c3VwL1JF QURNRSBmb3IgbW9yZQ0KIyBpbmZvcm1hdGlvbiBvbiBDVlN1cCBhbmQgdGhl c2UgZmlsZXMpLiAgVG8gdXNlLCBkbyAibWFrZSB1cGRhdGUiIGluIC91c3Iv c3JjLg0KIw0KI1NVUF9VUERBVEU9ICAgICB5ZXMNCiMNCiNTVVA9ICAgICAg ICAgICAgL3Vzci9sb2NhbC9iaW4vY3ZzdXANCiNTVVBGTEFHUz0gICAgICAg LWcgLUwgMg0KI1NVUEhPU1Q9ICAgICAgICBjdnN1cC51ay5GcmVlQlNELm9y Zw0KI1NVUEZJTEU9ICAgICAgICAvdXNyL3NoYXJlL2V4YW1wbGVzL2N2c3Vw L3N0YWJsZS1zdXBmaWxlDQojUE9SVFNTVVBGSUxFPSAgIC91c3Ivc2hhcmUv ZXhhbXBsZXMvY3ZzdXAvcG9ydHMtc3VwZmlsZQ0KI0RPQ1NVUEZJTEU9ICAg ICAvdXNyL3NoYXJlL2V4YW1wbGVzL2N2c3VwL2RvYy1zdXBmaWxlDQojDQoj IHRvcCgxKSB1c2VzIGEgaGFzaCB0YWJsZSBmb3IgdGhlIHVzZXIgbmFtZXMu ICBUaGUgc2l6ZSBvZiB0aGlzIGhhc2gNCiMgY2FuIGJlIHR1bmVkIHRvIG1h dGNoIHRoZSBudW1iZXIgb2YgbG9jYWwgdXNlcnMuICBUaGUgdGFibGUgc2l6 ZSBzaG91bGQNCiMgYmUgYSBwcmltZSBudW1iZXIgYXBwcm94aW1hdGVseSB0 d2ljZSBhcyBsYXJnZSBhcyB0aGUgbnVtYmVyIG9mIGxpbmVzIGluDQojIC9l dGMvcGFzc3dkLiAgVGhlIGRlZmF1bHQgbnVtYmVyIGlzIDIwMDExLg0KIw0K I1RPUF9UQUJMRV9TSVpFPSAxMDENCiMNCiMgRG9jdW1lbnRhdGlvbg0KIw0K IyBUaGUgbGlzdCBvZiBsYW5ndWFnZXMgYW5kIGVuY29kaW5ncyB0byBidWls ZCBhbmQgaW5zdGFsbA0KIw0KI0RPQ19MQU5HPQllbl9VUy5JU084ODU5LTEg cnVfUlUuS09JOC1SDQojDQojDQojIHNlbmRtYWlsDQojDQojIFRoZSBmb2xs b3dpbmcgc2V0cyB0aGUgZGVmYXVsdCBtNCBjb25maWd1cmF0aW9uIGZpbGUg dG8gdXNlIGF0DQojIGluc3RhbGwgdGltZS4gIFVzZSB3aXRoIGNhdXRpb24g YXMgYSBtYWtlIGluc3RhbGwgd2lsbCBvdmVyd3JpdGUNCiMgYW55IGV4aXN0 aW5nIC9ldGMvbWFpbC9zZW5kbWFpbC5jZi4gIE5vdGUgdGhhdCBTRU5ETUFJ TF9DRiBpcyBub3cNCiMgZGVwcmVjYXRlZC4gIFRoZSB2YWx1ZSBzaG91bGQg YmUgYSBmdWxseSBxdWFsaWZpZWQgcGF0aCBuYW1lLg0KIw0KI1NFTkRNQUlM X01DPS9ldGMvbWFpbC9teWNvbmZpZy5tYw0KIw0KIyBUaGUgZm9sbG93aW5n IHNldHMgdGhlIGRlZmF1bHQgbTQgY29uZmlndXJhdGlvbiBmaWxlIGZvciBt YWlsDQojIHN1Ym1pc3Npb24gdG8gdXNlIGF0IGluc3RhbGwgdGltZS4gIFVz ZSB3aXRoIGNhdXRpb24gYXMgYSBtYWtlDQojIGluc3RhbGwgd2lsbCBvdmVy d3JpdGUgYW55IGV4aXN0aW5nIC9ldGMvbWFpbC9zdWJtaXQuY2YuICBUaGUN CiMgdmFsdWUgc2hvdWxkIGJlIGEgZnVsbHkgcXVhbGlmaWVkIHBhdGggbmFt ZS4NCiMNCiNTRU5ETUFJTF9TVUJNSVRfTUM9L2V0Yy9tYWlsL215c3VibWl0 Lm1jDQojDQojIElmIHlvdSBuZWVkIHRvIGJ1aWxkIGFkZGl0aW9uYWwgLmNm IGZpbGVzIGR1cmluZyBhIG1ha2UgYnVpbGR3b3JsZCwNCiMgaW5jbHVkZSB0 aGUgZnVsbCBwYXRocyB0byB0aGUgLm1jIGZpbGVzIGluIFNFTkRNQUlMX0FE RElUSU9OQUxfTUMuDQojDQojU0VORE1BSUxfQURESVRJT05BTF9NQz0vZXRj L21haWwvZm9vLm1jIC9ldGMvbWFpbC9iYXIubWMNCiMNCiMgU2V0dGluZyB0 aGUgZm9sbG93aW5nIHZhcmlhYmxlIG1vZGlmaWVzIHRoZSBmbGFncyBwYXNz ZWQgdG8gbTQgd2hlbg0KIyBidWlsZGluZyBhIC5jZiBmaWxlIGZyb20gYSAu bWMgZmlsZS4gIEl0IGNhbiBiZSB1c2VkIHRvIGVuYWJsZQ0KIyBmZWF0dXJl cyBkaXNhYmxlZCBieSBkZWZhdWx0Lg0KIw0KI1NFTkRNQUlMX000X0ZMQUdT PQ0KIw0KIyBTZXR0aW5nIHRoZSBmb2xsb3dpbmcgdmFyaWFibGVzIG1vZGlm aWVzIHRoZSBidWlsZCBlbnZpcm9ubWVudCBmb3INCiMgc2VuZG1haWwgYW5k IGl0cyByZWxhdGVkIHV0aWxpdGllcy4gRm9yIGV4YW1wbGUsIFNBU0wgc3Vw cG9ydCBjYW4gYmUNCiMgYWRkZWQgd2l0aCBzZXR0aW5ncyBzdWNoIGFzOg0K Iw0KIwlTRU5ETUFJTF9DRkxBR1M9LUkvdXNyL2xvY2FsL2luY2x1ZGUvc2Fz bCAtRFNBU0wNCiMJU0VORE1BSUxfTERGTEFHUz0tTC91c3IvbG9jYWwvbGli DQojCVNFTkRNQUlMX0xEQUREPS1sc2FzbA0KIw0KIyBOb3RlOiBJZiB5b3Ug YXJlIHVzaW5nIEN5cnVzIFNBU0wgd2l0aCBvdGhlciBhcHBsaWNhdGlvbnMg d2hpY2ggcmVxdWlyZQ0KIwlhY2Nlc3MgdG8gdGhlIHNhc2xkYiBmaWxlLCB5 b3Ugc2hvdWxkIGFkZCB0aGUgZm9sbG93aW5nIHRvIHlvdXINCiMJc2VuZG1h aWwubWMgZmlsZToNCiMNCiMJZGVmaW5lKGBjb25mRE9OVF9CTEFNRV9TRU5E TUFJTCcsYEdyb3VwUmVhZGFibGVTQVNMREJGaWxlJykNCiMNCiNTRU5ETUFJ TF9DRkxBR1M9DQojU0VORE1BSUxfTERGTEFHUz0NCiNTRU5ETUFJTF9MREFE RD0NCiNTRU5ETUFJTF9EUEFERD0NCiMNCiMgU2V0dGluZyBTRU5ETUFJTF9T RVRfVVNFUl9JRCB3aWxsIGluc3RhbGwgdGhlIHNlbmRtYWlsIGJpbmFyeSBh cyBhDQojIHNldC11c2VyLUlEIHJvb3QgYmluYXJ5IGluc3RlYWQgb2YgYSBz ZXQtZ3JvdXAtSUQgc21tc3AgYmluYXJ5IGFuZCB3aWxsDQojIHByZXZlbnQg dGhlIGluc3RhbGxhdGlvbiBvZiAvZXRjL21haWwvc3VibWl0LmNmLg0KIyBU aGlzIGlzIGEgZGVwcmVjYXRlZCBtb2RlIG9mIG9wZXJhdGlvbi4gIFNlZSBl dGMvbWFpbC9SRUFETUUgZm9yIG1vcmUNCiMgaW5mb3JtYXRpb24uDQojDQoj U0VORE1BSUxfU0VUX1VTRVJfSUQ9DQo= --0-1986994741-1022828783=:40770-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 0:55:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from n9.grp.scd.yahoo.com (n9.grp.scd.yahoo.com [66.218.66.93]) by hub.freebsd.org (Postfix) with SMTP id 5724737B405 for ; Fri, 31 May 2002 00:55:16 -0700 (PDT) X-eGroups-Return: notify-return-stable=FreeBSD.org@returns.groups.yahoo.com Received: from [66.218.66.95] by n9.grp.scd.yahoo.com with NNFMP; 31 May 2002 07:55:16 -0000 Received: (qmail 99112 invoked by uid 7800); 31 May 2002 07:55:16 -0000 Date: 31 May 2002 07:55:16 -0000 Message-ID: <1022831716.175.99105.m7@yahoogroups.com> From: SKATINGEXTREME Moderator To: stable@FreeBSD.org Subject: Welcome to SKATINGEXTREME MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, Thank you for being a subscriber to this list. I hope that you get a chance to check out my web sites. I have one at http://www.howard.net/hilary and one also at http://www.webpost.net/sk/SkatersChoice . I will try to be in the chat room on Thursday evenings. Go to Hilarys Skating Center then if you want to try to chat. I would love to get a lot of skaters out there in a chat. Pass the word and lets find some skaters eh. Thanks, Hilary Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 1:48:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from n33.grp.scd.yahoo.com (n33.grp.scd.yahoo.com [66.218.66.101]) by hub.freebsd.org (Postfix) with SMTP id A684537B407 for ; Fri, 31 May 2002 01:48:26 -0700 (PDT) X-eGroups-Return: confirm-return-stable=FreeBSD.org@returns.groups.yahoo.com Received: from [66.218.67.192] by n33.grp.scd.yahoo.com with NNFMP; 31 May 2002 08:48:26 -0000 Received: (qmail 97725 invoked by uid 7800); 31 May 2002 08:48:25 -0000 Date: 31 May 2002 08:48:25 -0000 Message-ID: <1022834905.55.97724.m10@yahoogroups.com> From: Yahoo!Groups Notification Reply-To: confirm-unsub-X78_QQucFxkmqaVHL7zKPVbyZ0c@yahoogroups.com To: stable@FreeBSD.org Subject: Please reply to unsubscribe from SKATINGEXTREME MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, We have received a request from you to unsubscribe from the SKATINGEXTREME group. Please confirm your request by replying to this message. If you do not wish to unsubscribe from SKATINGEXTREME, please ignore this message. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 1:49:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from n21.grp.scd.yahoo.com (n21.grp.scd.yahoo.com [66.218.66.77]) by hub.freebsd.org (Postfix) with SMTP id 3091737B401 for ; Fri, 31 May 2002 01:49:48 -0700 (PDT) X-eGroups-Return: notify-return-stable=FreeBSD.org@returns.groups.yahoo.com Received: from [66.218.67.200] by n21.grp.scd.yahoo.com with NNFMP; 31 May 2002 08:49:48 -0000 Received: (qmail 17744 invoked by uid 7800); 31 May 2002 08:49:47 -0000 Date: 31 May 2002 08:49:47 -0000 Message-ID: <1022834987.94.17743.m8@yahoogroups.com> From: Yahoo!Groups Notification To: stable@FreeBSD.org Subject: You have been unsubscribed from SKATINGEXTREME MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, This is to inform you that your request to unsubscribe from SKATINGEXTREME has been completed. Regards, Yahoo! Groups Customer Care Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 2: 3: 4 2002 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 3959B37B405 for ; Fri, 31 May 2002 02:02:49 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g4V91uw29617; Fri, 31 May 2002 12:01:56 +0300 (EEST) (envelope-from ru) Date: Fri, 31 May 2002 12:01:56 +0300 From: Ruslan Ermilov To: Mattias Bj?rk Cc: stable@FreeBSD.ORG Subject: Re: Problems when runing make installworld. Message-ID: <20020531090156.GB27669@sunbay.com> References: <20020528071935.GD53736@sunbay.com> <20020531090140.V40770-200000@thrawn.birch.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="i9LlY+UWpKt15+FH" Content-Disposition: inline In-Reply-To: <20020531090140.V40770-200000@thrawn.birch.se> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --i9LlY+UWpKt15+FH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 31, 2002 at 09:06:23AM +0200, Mattias Bj?rk wrote: > Hi, Again, thanks for the answer, i read > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D30276. >=20 > It says there that if you are building make world with a p3 and run > make installworld on a 486 you get this error. But I don't have a > p3 I have a dual celeron, I have also attached my make.conf from > the building machine. And its a p90 that Im makeing the make > worldinstall on. But any way the problem seams too be the same or > am I wrong? >=20 Did you set CPUTYPE=3Di586 just before doing a buildworld? Was it by chance set to CPUTYPE=3Di686 before? If that's the case, your /usr/lib stuff on the build box has some P6 CPU instructions, and some tools (like install(1) and strip(1)) that are used during installworld on your Pentium box use these libraries and fail. To work around this, you'll have to: 1. Rebuild and reinstall world/kernel on your build box with the compatible (with your install box) CPUTYPE setting like CPUTYPE=3Di586. 2. Reboot with the new kernel and world. 3. Build the world again (!). 4. Install this second world on a Pentium box. > On Tue, 28 May 2002, Ruslan Ermilov wrote: >=20 > > This is a known issue, for which there's no a quick solution. > > Please see PR 30276 for details. > > > > On Mon, May 27, 2002 at 10:52:23PM +0200, Mattias Bj?rk wrote: > > > On Mon, 27 May 2002, Mattias Bj?rk wrote: > > > > > > > Hi, > > > > > > > > I have one dual celeron 400 MHz that i runed a make buildworld. And= then i > > > > export /usr/src and /usr/obj with nfs to my box that I world like to > > > > upgrade. Its an p90 laptop, so that is why Im doing the build on my= dual > > > > 400. :) > > > > > > > > Any way when I run make installworld on the laptop, I get goes for = about > > > > 30 sec to one minute and then /usr/bin/install crashes with this er= ror > > > > message: > > > > > > > > mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p > > > > /usr/include > > > > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam= /*.h > > > > /usr/include/cam > > > > Illegal instruction - core dumped > > > > *** Error code 132 > > > > > > > > Stop in /usr/src/include. > > > > *** Error code 1 > > > > > > > > Stop in /usr/src. > > > > *** Error code 1 > > > > > > > > Stop in /usr/src. > > > > *** Error code 1 > > > > > > > > Stop in /usr/src. > > > > *** Error code 1 > > > > > > > > Stop in /usr/src. > > > > > > > > Any clues? I have attched the hole make installworld log. It seems = that > > > > there is something wrong with my install file or? I copyied it from > > > > another machine that is a p120, but that did not help. Same problem= , first > > > > I thought that It hade something to do with that I was runing make > > > > installworld in multiuser mode. But i rebooted and runed it with bo= ot -s > > > > but that did not help either. > > > > > > > > Any clues/tips/flames welcome, as you can see it is no fun at all (= TM) to > > > > run a make world on a p90. I have done it before and it worked but i > > > > rather not do that... :) > > > > > > > > Perhaps you need more info, then do not hasitate to ask for it. Mig= ht take > > > > some time to answer this mail because I have some mails to catch up= in > > > > my mbox... > > > > > > > > Sorry if i typ to mutch... I will do better next time... > > > > > > > > Mvh Mattias Bj?rk > > > > > > > > Real Programmers don't write in PL/I. PL/I is for programmers who > > > > can't decide whether to write in COBOL or FORTRAN. > > > > > > > > > Script started on Mon May 27 22:36:18 2002 > > > # make installworld > > > mkdir -p /tmp/install.2474 > > > for prog in [ awk cat chflags chmod chown date echo egrep find grep = ln make makewhatis mtree mv perl rm sed sh sysctl test true uname wc zic; = do cp `which $prog` /tmp/install.2474; done > > > cd /usr/src; MAKEOBJDIRPREFIX=3D/usr/obj MACHINE_ARCH=3Di386 MACHIN= E=3Di386 OBJFORMAT_PATH=3D/usr/obj/usr/src/i386/usr/libexec PERL5LIB=3D/u= sr/obj/usr/src/i386/usr/libdata/perl/5.00503 GROFF_BIN_PATH=3D/usr/obj/usr= /src/i386/usr/bin GROFF_FONT_PATH=3D/usr/obj/usr/src/i386/usr/share/groff_= font GROFF_TMAC_PATH=3D/usr/obj/usr/src/i386/usr/share/tmac PATH=3D/usr/o= bj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i38= 6/usr/games:/tmp/install.2474 make -f Makefile.inc1 reinstall > > > -------------------------------------------------------------- > > > >>> Making hierarchy > > > -------------------------------------------------------------- > > > cd /usr/src; make -f Makefile.inc1 hierarchy > > > cd /usr/src/etc; make distrib-dirs > > > set - `grep "^[a-zA-Z]" /usr/src/etc/locale.deprecated`; while [ $# = -gt 0 ] ; do for dir in /usr/share/locale /usr/share/nls /usr/local/sha= re/nls; do test -d /${dir} && cd /${dir}; test -L "$2" && rm -rf "$2"; = test \! -L "$1" && test -d "$1" && mv "$1" "$2"; done; shift; shift; done > > > mtree -deU -f /usr/src/etc/mtree/BSD.root.dist -p / > > > mtree -deU -f /usr/src/etc/mtree/BSD.var.dist -p /var > > > mtree -deU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr > > > mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include > > > mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/libdata/pe= rl/5.00503/mach > > > cd /; rm -f /sys; ln -s usr/src/sys sys > > > cd /usr/share/man/en.ISO8859-1; ln -sf ../man* . > > > cd /usr/share/man; set - `grep "^[a-zA-Z]" /usr/src/etc/man.alias`; = while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; d= one > > > cd /usr/share/locale; set - `grep "^[a-zA-Z]" /usr/src/etc/locale.al= ias`; while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shi= ft; done > > > cd /usr/share/nls; set - `grep "^[a-zA-Z]" /usr/src/etc/nls.alias`; = while [ $# -gt 0 ] ; do rm -rf "$1"; ln -s "$2" "$1"; shift; shift; d= one > > > > > > -------------------------------------------------------------- > > > >>> Installing everything.. > > > -------------------------------------------------------------- > > > cd /usr/src; make -f Makefile.inc1 install > > > =3D=3D=3D> share/info > > > =3D=3D=3D> include > > > if [ -h /usr/include/cam ]; then rm -f /usr/include/cam; fi > > > if [ -h /usr/include/msdosfs ]; then rm -f /usr/include/msdosfs; fi > > > if [ -h /usr/include/net ]; then rm -f /usr/include/net; fi > > > if [ -h /usr/include/netatalk ]; then rm -f /usr/include/netatalk; = fi > > > if [ -h /usr/include/netatm ]; then rm -f /usr/include/netatm; fi > > > if [ -h /usr/include/netgraph ]; then rm -f /usr/include/netgraph; = fi > > > if [ -h /usr/include/netinet ]; then rm -f /usr/include/netinet; fi > > > if [ -h /usr/include/netinet6 ]; then rm -f /usr/include/netinet6; = fi > > > if [ -h /usr/include/netipx ]; then rm -f /usr/include/netipx; fi > > > if [ -h /usr/include/netkey ]; then rm -f /usr/include/netkey; fi > > > if [ -h /usr/include/netnatm ]; then rm -f /usr/include/netnatm; fi > > > if [ -h /usr/include/netncp ]; then rm -f /usr/include/netncp; fi > > > if [ -h /usr/include/netns ]; then rm -f /usr/include/netns; fi > > > if [ -h /usr/include/netsmb ]; then rm -f /usr/include/netsmb; fi > > > if [ -h /usr/include/nfs ]; then rm -f /usr/include/nfs; fi > > > if [ -h /usr/include/ntfs ]; then rm -f /usr/include/ntfs; fi > > > if [ -h /usr/include/nwfs ]; then rm -f /usr/include/nwfs; fi > > > if [ -h /usr/include/pccard ]; then rm -f /usr/include/pccard; fi > > > if [ -h /usr/include/posix4 ]; then rm -f /usr/include/posix4; fi > > > if [ -h /usr/include/sys ]; then rm -f /usr/include/sys; fi > > > if [ -h /usr/include/vm ]; then rm -f /usr/include/vm; fi > > > if [ -h /usr/include/fs/smbfs ]; then rm -f /usr/include/fs/smbfs; = fi > > > if [ -h /usr/include/isofs/cd9660 ]; then rm -f /usr/include/isofs/c= d9660; fi > > > if [ -h /usr/include/ufs/ffs ]; then rm -f /usr/include/ufs/ffs; fi > > > if [ -h /usr/include/ufs/mfs ]; then rm -f /usr/include/ufs/mfs; fi > > > if [ -h /usr/include/ufs/ufs ]; then rm -f /usr/include/ufs/ufs; fi > > > if [ -h /usr/include/dev/ppbus ]; then rm -f /usr/include/dev/ppbus;= fi > > > if [ -h /usr/include/dev/usb ]; then rm -f /usr/include/dev/usb; fi > > > if [ -h /usr/include/machine ]; then rm -f /usr/include/machine; fi > > > mtree -deU -f /usr/src/include/../etc/mtree/BSD.include.dist -p /usr= /include > > > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 cam/*= .h /usr/include/cam > > > Illegal instruction - core dumped > > > *** Error code 132 > > > > > > Stop in /usr/src/include. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > *** Error code 1 > > > > > > Stop in /usr/src. > > > # d=08 =08 > CPUTYPE=3Di586 > CFLAGS=3D -O -pipe -march=3Di586 ^^^^^^^^^^^ This is bogus, CPUTYPE adds to CFLAGS as necessary. This is not relevant to the problem though. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --i9LlY+UWpKt15+FH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE89zwEUkv4P6juNwoRAt8fAJ0TFip+mO7igiSVVWYFpiSY9P9nmQCfWaW3 /YEIiX6XL4gzj6Z0XKCavHI= =cIu+ -----END PGP SIGNATURE----- --i9LlY+UWpKt15+FH-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 2:41:39 2002 Delivered-To: freebsd-stable@freebsd.org Received: from alogis.com (firewall.solit-ag.de [212.184.102.1]) by hub.freebsd.org (Postfix) with ESMTP id 4E82437B416; Fri, 31 May 2002 02:41:14 -0700 (PDT) Received: from alogis.com (kipp@clausthal.int1.b.intern [10.1.1.30]) by alogis.com (8.11.1/8.9.3) with ESMTP id g4V9f0l94878; Fri, 31 May 2002 11:41:02 +0200 (CEST) (envelope-from holger.kipp@alogis.com) Message-ID: <3CF74128.708F4612@alogis.com> Date: Fri, 31 May 2002 11:23:52 +0200 From: Holger Kipp X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.13 i686) X-Accept-Language: en MIME-Version: 1.0 To: JJ Behrens Cc: FreeBSD-STABLE Mailing List , freebsd-questions@FreeBSD.ORG Subject: Re: Server won't boot after recompile the kernel with ipfw support References: <20020528142640.A22370@phxby.com> <20020528133316.S16405-100000@boris.st.hmc.edu> <20020528150941.A24676@phxby.com> <200205282131.g4SLVmYZ024980@apollo.backplane.com> <3CF48FB4.E82525FE@alogis.com> <20020530144048.A24912@alicia.nttmcl.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG JJ Behrens wrote: > > > To point out the obvious: put the firewall rules in "/etc/ipfw.conf", > > if firewall_type contains a filename. If firewall_type is the name > > of a configuration, edit rc.firewall. > > Hmm, very interesting. I can't seem to find this (i.e. pre-made > firewall_type's) documented in the handbook. Am I missing something, or should > I submit a PR? I'd say you're missing something . It is all described within /etc/defaults/rc.conf and /etc/rc.firewall. You might also want to look at 'man firewall', as has been pointed out already. Regards, Holger --- 8< ----------------- snip ----------------------------------------------- fgrep firewall /etc/defaults/rc.conf gives (among others): ### Basic network and firewall/security options: ### firewall_enable="NO" # Set to YES to enable firewall functionality firewall_script="/etc/rc.firewall" # Which script to run to set up the firewall firewall_type="UNKNOWN" # Firewall type (see /etc/rc.firewall) Firewall type (see /etc/rc.firewall) gives: ############ # Define the firewall type in /etc/rc.conf. Valid values are: # open - will allow anyone in # client - will try to protect just this machine # simple - will try to protect a whole network # closed - totally disables IP services except via lo0 interface # UNKNOWN - disables the loading of firewall rules. # filename - will load the rules in the given filename (full path required) # # For ``client'' and ``simple'' the entries below should be customized # appropriately. -- Holger Kipp, Dipl.-Math., Systemadministrator | alogis AG Fon: +49 (0)30 / 43 65 8 - 114 | Berliner Strasse 26 Fax: +49 (0)30 / 43 65 8 - 214 | D-13507 Berlin Tegel email: holger.kipp@alogis.com | http://www.alogis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 5:34:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from 141.com (mail1.141.com [65.168.139.2]) by hub.freebsd.org (Postfix) with ESMTP id 5D05E37B404 for ; Fri, 31 May 2002 05:34:55 -0700 (PDT) Received: from 141.com [151.200.59.171] by 141.com with ESMTP (SMTPD32-7.10) id AE318B200E6; Fri, 31 May 2002 06:36:01 -0600 To: stable@FreeBSD.org Subject: Re: Tagged IBM ATA drives under nowadays -stable Date: Fri, 31 May 2002 08:34:52 -0400 From: Andrew Lankford Message-Id: <200205310636250.SM02244@141.com> X-RBL-Warning: SPAMHEADERS: This E-mail has headers consistent with spam [4000020e]. X-Note: This E-mail was scanned for spam. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I recompiled my kernel just after Soren's last commit yesterday and enabled tags. Still had to mount root manually, though I'm not sure the latest change was directed at my problem. Andrew Lankford To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 6:59:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id 09AF637B408 for ; Fri, 31 May 2002 06:59:29 -0700 (PDT) Received: (qmail 9518 invoked by uid 0); 31 May 2002 13:59:25 -0000 Received: from acb97b1f.ipt.aol.com (HELO bowman.gmx.net) (172.185.123.31) by mail.gmx.net (mp014-rz3) with SMTP; 31 May 2002 13:59:25 -0000 Message-Id: <5.1.0.14.0.20020531155904.00a07cd0@pop.gmx.net> X-Sender: 12223972@pop.gmx.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 31 May 2002 15:59:16 +0200 To: freebsd-stable@FreeBSD.ORG From: Daniel Geske Subject: auth 650a995d unsubscribe freebsd-stable danielgeske@gmx.net Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG auth 650a995d unsubscribe freebsd-stable danielgeske@gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 7:12:15 2002 Delivered-To: freebsd-stable@freebsd.org Received: from nef.ens.fr (nef.ens.fr [129.199.96.32]) by hub.freebsd.org (Postfix) with ESMTP id D604537B438 for ; Fri, 31 May 2002 07:11:36 -0700 (PDT) Received: from corto.lpt.ens.fr (corto.lpt.ens.fr [129.199.122.2]) by nef.ens.fr (8.10.1/1.01.28121999) with ESMTP id g4VEBZp41624 ; Fri, 31 May 2002 16:11:35 +0200 (CEST) Received: from (rsidd@localhost) by corto.lpt.ens.fr (8.9.3/jtpda-5.3.1) id QAA57790 ; Fri, 31 May 2002 16:11:34 +0200 (CEST) Date: Fri, 31 May 2002 16:11:34 +0200 From: Rahul Siddharthan To: John Polstra Cc: stable@freebsd.org Subject: Re: ssh + X11 forwarding = a hung ssh process Message-ID: <20020531161134.E46325@lpt.ens.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020530170501.A37186-100000@snafu.adept.org> X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John Polstra wrote: > It only happens when protocol version 2 is used. Try forcing that > with "ssh -2 ...", and there's a good chance you'll see the problem. I think it's a problem in OpenSSH 2.9 but not in 3.x. It doesn't seem specific to FreeBSD. ssh -2 from FreeBSD 4-stable to FreeBSD 4-stable: hangs ssh -2 from FreeBSD 4-stable to Linux with OpenSSH (2.9 or 3.1): hangs ssh -2 from FreeBSD 4-stable to FreeBSD with commercial SSH2: no hang ssh -2 from Linux (OpenSSH 3.1p1) to other machines: no hang ssh -2 from Linux (OpenSSH 2.9p1) to FreeBSD : hangs ssh -2 from Linux (OpenSSH 2.9p1) to Linux (OpenSSH 3.x): hangs I don't have a FreeBSD machine with OpenSSH 3.x installed, but I suspect it will work ok... - Rahul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 8:47:50 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 7EADE37B403 for ; Fri, 31 May 2002 08:47:44 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g4VFlep76499; Fri, 31 May 2002 08:47:40 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g4VFle239342; Fri, 31 May 2002 08:47:40 -0700 (PDT) (envelope-from jdp) Date: Fri, 31 May 2002 08:47:40 -0700 (PDT) Message-Id: <200205311547.g4VFle239342@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: rsidd@online.fr Subject: Re: ssh + X11 forwarding = a hung ssh process In-Reply-To: <20020531161134.E46325@lpt.ens.fr> References: <20020531161134.E46325@lpt.ens.fr> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <20020531161134.E46325@lpt.ens.fr>, Rahul Siddharthan wrote: > I think it's a problem in OpenSSH 2.9 but not in 3.x. It doesn't seem > specific to FreeBSD. > > ssh -2 from FreeBSD 4-stable to FreeBSD 4-stable: hangs > ssh -2 from FreeBSD 4-stable to Linux with OpenSSH (2.9 or 3.1): hangs > ssh -2 from FreeBSD 4-stable to FreeBSD with commercial SSH2: no hang > ssh -2 from Linux (OpenSSH 3.1p1) to other machines: no hang > ssh -2 from Linux (OpenSSH 2.9p1) to FreeBSD : hangs > ssh -2 from Linux (OpenSSH 2.9p1) to Linux (OpenSSH 3.x): hangs Thanks for trying all those different combinations. I agree with your conclusion. It looks like the bug is in OpenSSH 2.9 but not in OpenSSH 3.1. When 3.1 gets merged into -stable we can hope the problem will vanish. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 8:51:27 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cyclone.tornadogroup.com (cyclone.tornadogroup.com [212.172.155.83]) by hub.freebsd.org (Postfix) with ESMTP id BE05237B408 for ; Fri, 31 May 2002 08:51:19 -0700 (PDT) Received: from claudette.e1.tornadogroup.com (root@claudette.e1.tornadogroup.com [192.168.0.77]) by cyclone.tornadogroup.com (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id g4VFpCr16364; Fri, 31 May 2002 16:51:12 +0100 (BST) Received: from claudette.e1.tornadogroup.com (matthew@localhost [IPv6:::1]) by claudette.e1.tornadogroup.com (8.12.3/8.12.3) with ESMTP id g4VFpCiH080429; Fri, 31 May 2002 16:51:12 +0100 (BST) (envelope-from matthew.seaman@tornadogroup.com) Received: (from matthew@localhost) by claudette.e1.tornadogroup.com (8.12.3/8.12.3/Submit) id g4VFpAV3080428; Fri, 31 May 2002 16:51:10 +0100 (BST) (envelope-from matthew.seaman@tornadogroup.com) X-Authentication-Warning: claudette.e1.tornadogroup.com: matthew set sender to matthew.seaman@tornadogroup.com using -f Subject: Re: ssh + X11 forwarding = a hung ssh process From: Matthew Seaman To: Rahul Siddharthan Cc: John Polstra , stable@FreeBSD.ORG In-Reply-To: <20020531161134.E46325@lpt.ens.fr> References: <20020531161134.E46325@lpt.ens.fr> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 31 May 2002 16:51:10 +0100 Message-Id: <1022860270.78295.36.camel@claudette.e1.tornadogroup.com> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 2002-05-31 at 15:11, Rahul Siddharthan wrote: > John Polstra wrote: > > It only happens when protocol version 2 is used. Try forcing that > > with "ssh -2 ...", and there's a good chance you'll see the problem. > > I think it's a problem in OpenSSH 2.9 but not in 3.x. It doesn't seem > specific to FreeBSD. > > ssh -2 from FreeBSD 4-stable to FreeBSD 4-stable: hangs > ssh -2 from FreeBSD 4-stable to Linux with OpenSSH (2.9 or 3.1): hangs > ssh -2 from FreeBSD 4-stable to FreeBSD with commercial SSH2: no hang > ssh -2 from Linux (OpenSSH 3.1p1) to other machines: no hang > ssh -2 from Linux (OpenSSH 2.9p1) to FreeBSD : hangs > ssh -2 from Linux (OpenSSH 2.9p1) to Linux (OpenSSH 3.x): hangs > > I don't have a FreeBSD machine with OpenSSH 3.x installed, but I > suspect it will work ok... Is this the same problem as I reported in PR bin/35538 ? If so, OpenSSH 3.x on FreeBSD doesn't hang Cheers, Matthew -- Matthew Seaman 01628 498661 Scrutantibus gehennas parabat St Augustine To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 9: 3:59 2002 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 428C037B404 for ; Fri, 31 May 2002 09:03:54 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id g4VG3np76571; Fri, 31 May 2002 09:03:50 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id g4VG3nA39402; Fri, 31 May 2002 09:03:49 -0700 (PDT) (envelope-from jdp) Date: Fri, 31 May 2002 09:03:49 -0700 (PDT) Message-Id: <200205311603.g4VG3nA39402@vashon.polstra.com> To: stable@freebsd.org From: John Polstra Cc: matthew.seaman@tornadogroup.com Subject: Re: ssh + X11 forwarding = a hung ssh process In-Reply-To: <1022860270.78295.36.camel@claudette.e1.tornadogroup.com> References: <20020531161134.E46325@lpt.ens.fr> <1022860270.78295.36.camel@claudette.e1.tornadogroup.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <1022860270.78295.36.camel@claudette.e1.tornadogroup.com>, Matthew Seaman wrote: > Is this the same problem as I reported in PR bin/35538 ? I'm not sure whether it's the same bug or not. It could be. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 9:52:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by hub.freebsd.org (Postfix) with ESMTP id 4650B37B408; Fri, 31 May 2002 09:52:07 -0700 (PDT) Received: from bmah.dyndns.org ([12.233.149.189]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020531165206.USVE29266.sccrmhc01.attbi.com@bmah.dyndns.org>; Fri, 31 May 2002 16:52:06 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.3/8.12.3) with ESMTP id g4VGq5fs004137; Fri, 31 May 2002 09:52:05 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.3/8.12.3/Submit) id g4VGq5YV004136; Fri, 31 May 2002 09:52:05 -0700 (PDT) Message-Id: <200205311652.g4VGq5YV004136@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20020506 with nmh-1.0.4 To: freebsd-qa@freebsd.org, freebsd-stable@freebsd.org Cc: re@freebsd.org Subject: 4.6-RELEASE delayed From: bmah@freebsd.org (Bruce A. Mah) Reply-To: bmah@freebsd.org X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 May 2002 09:52:05 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just a note to say that due to some late-breaking issues, 4.6 will be released about a week later than originally planned. The magic date is now 8 June 2002...I've just updated the release schedule on the Web site. We'll be doing another release candidate (4.6-RC4...for various reasons there won't be a 4.6-RC3) on Monday, in which we hope to see the major remaining issues addressed. We encourage you to see the testing page for this release at: http://www.freebsd.org/releases/4.6R/qa.html Note that as we get closer to the release, it becomes harder for us to justify making changes. We always value feedback, testing reports, and requests for changes, but we also need to balance potential changes against the risks of instability and more testing. Thanks for your understanding...we're looking forward to having a good release! Bruce and the rest of the RE team. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 9:56:44 2002 Delivered-To: freebsd-stable@freebsd.org Received: from hermes.pressenter.com (hermes.pressenter.com [209.224.20.19]) by hub.freebsd.org (Postfix) with ESMTP id 7B94837B404; Fri, 31 May 2002 09:56:30 -0700 (PDT) Received: from [209.224.35.190] (helo=daggar.sbgnet.net) by hermes.pressenter.com with smtp (Exim 3.16 #1) id 17Dph8-0008Ov-00; Fri, 31 May 2002 11:56:08 -0500 Date: Fri, 31 May 2002 11:55:53 -0500 From: Stephen Hilton To: freebsd-stable@freebsd.org Cc: ru@FreeBSD.ORG, thrawn@linux.nu Subject: Re: Problems when runing make installworld. Message-Id: <20020531115553.3aff789f.nospam@hiltonbsd.com> In-Reply-To: <20020531090156.GB27669@sunbay.com> References: <20020528071935.GD53736@sunbay.com> <20020531090140.V40770-200000@thrawn.birch.se> <20020531090156.GB27669@sunbay.com> Organization: HiltonBSD.com X-Mailer: Sylpheed version 0.7.6 (GTK+ 1.2.10; i386-portbld-freebsd4.6) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 31 May 2002 12:01:56 +0300 Ruslan Ermilov wrote: > On Fri, May 31, 2002 at 09:06:23AM +0200, Mattias Bj?rk wrote: > > Hi, Again, thanks for the answer, i read > > http://www.freebsd.org/cgi/query-pr.cgi?pr=30276. > > > > It says there that if you are building make world with a p3 and run > > make installworld on a 486 you get this error. But I don't have a > > p3 I have a dual celeron, I have also attached my make.conf from > > the building machine. And its a p90 that Im makeing the make > > worldinstall on. But any way the problem seams too be the same or > > am I wrong? > > > Did you set CPUTYPE=i586 just before doing a buildworld? Was it by > chance set to CPUTYPE=i686 before? > > If that's the case, your /usr/lib stuff on the build box has some P6 > CPU instructions, and some tools (like install(1) and strip(1)) that > are used during installworld on your Pentium box use these libraries > and fail. To work around this, you'll have to: > > 1. Rebuild and reinstall world/kernel on your build box with the > compatible (with your install box) CPUTYPE setting like > CPUTYPE=i586. > > 2. Reboot with the new kernel and world. > > 3. Build the world again (!). > > 4. Install this second world on a Pentium box. > Ruslan, This is good information to have, but it brings to mind, how do the release engineers build a release that will install binaries, and then allow you to run a buildworld on machines types from a Intel 386 to an AMD Athlon? Is it a matter of using the lowest common denominator? and the release building hardware is running the operating system with out any optimizations? P.S. and to keep this "On-Topic" for the stable list, my buildworlds and systems have been running great on 4.6-Pre, Great work and kudos to the Project members and contributers. Regards, Stephen Hilton nospam@hiltonbsd.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 10:21:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-187.dsl.lsan03.pacbell.net [64.169.107.187]) by hub.freebsd.org (Postfix) with ESMTP id 63CEB37B408; Fri, 31 May 2002 10:21:27 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B9FDA66B8B; Fri, 31 May 2002 10:21:26 -0700 (PDT) Date: Fri, 31 May 2002 10:21:26 -0700 From: Kris Kennaway To: =?iso-8859-1?Q?Mattias_Bj=F6rk?= Cc: Ruslan Ermilov , stable@FreeBSD.ORG Subject: Re: Problems when runing make installworld. Message-ID: <20020531102126.A28135@xor.obsecurity.org> References: <20020528071935.GD53736@sunbay.com> <20020531090140.V40770-200000@thrawn.birch.se> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="wac7ysb48OaltWcw" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020531090140.V40770-200000@thrawn.birch.se>; from thrawn@linux.nu on Fri, May 31, 2002 at 09:06:23AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --wac7ysb48OaltWcw Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 31, 2002 at 09:06:23AM +0200, Mattias Bj=F6rk wrote: > Hi, Again, thanks for the answer, i read > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D30276. >=20 > It says there that if you are building make world with a p3 and run make = installworld on a 486 > you get this error. But I don't have a p3 I have a dual celeron, I have > also attached my make.conf from the building machine. And its a p90 that > Im makeing the make worldinstall on. But any way the problem seams too be > the same or am I wrong? The point is when you try and install a world built with different CPU optimizations. I assume you have CPUTYPE set on your build machine; this is what controls the optimizations that will be used when you build world, so it's obviously not going to work when you compile your binaries for a Pentium Pro and try and install them on a Pentium. Kris --wac7ysb48OaltWcw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE897EVWry0BWjoQKURAg54AKDYaKyuOL40TyDPSBUc9eqaJJjucwCfccq5 C2h4EqK1czQFlwh/9Xv1NiA= =4Ld2 -----END PGP SIGNATURE----- --wac7ysb48OaltWcw-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 10:31:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id D181E37B406 for ; Fri, 31 May 2002 10:31:26 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g4VHTbV89410; Fri, 31 May 2002 20:29:37 +0300 (EEST) (envelope-from ru) Date: Fri, 31 May 2002 20:29:37 +0300 From: Ruslan Ermilov To: Kris Kennaway Cc: Mattias Bj?rk , stable@FreeBSD.ORG Subject: Re: Problems when runing make installworld. Message-ID: <20020531172937.GB88599@sunbay.com> References: <20020528071935.GD53736@sunbay.com> <20020531090140.V40770-200000@thrawn.birch.se> <20020531102126.A28135@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD" Content-Disposition: inline In-Reply-To: <20020531102126.A28135@xor.obsecurity.org> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --uZ3hkaAS1mZxFaxD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 31, 2002 at 10:21:26AM -0700, Kris Kennaway wrote: > On Fri, May 31, 2002 at 09:06:23AM +0200, Mattias Bj?rk wrote: > > Hi, Again, thanks for the answer, i read > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D30276. > >=20 > > It says there that if you are building make world with a p3 and run mak= e installworld on a 486 > > you get this error. But I don't have a p3 I have a dual celeron, I have > > also attached my make.conf from the building machine. And its a p90 that > > Im makeing the make worldinstall on. But any way the problem seams too = be > > the same or am I wrong? >=20 > The point is when you try and install a world built with different CPU > optimizations. I assume you have CPUTYPE set on your build machine; > this is what controls the optimizations that will be used when you > build world, so it's obviously not going to work when you compile your > binaries for a Pentium Pro and try and install them on a Pentium. >=20 No, the problem is worse. Even if you set CPUTYPE for the target, some tools (bootstrap-tools and cross-tools) are built with /usr/lib stuff. And your /usr/lib stuff might be built with an incompatible CPU stuff. This is much easier demonstrated with cross-arch builds/installs. These simply do not work now. You can't build TARGET_ARCH=3Dalpha world on i386, then NFS mount /usr/src and /usr/obj on alpha, and install world from there. For this to work, we must rebuild all bootstrap- and cross-tools that we use during installworld on the target. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --uZ3hkaAS1mZxFaxD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE897MBUkv4P6juNwoRAsx2AJ47YAzWadB5uPhN+26bCIY1KCOHpQCfa4f3 UCeVY7qS7yvtruGCIJcc/g4= =POxL -----END PGP SIGNATURE----- --uZ3hkaAS1mZxFaxD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 10:32:49 2002 Delivered-To: freebsd-stable@freebsd.org Received: from whale.sunbay.crimea.ua (whale.sunbay.crimea.ua [212.110.138.65]) by hub.freebsd.org (Postfix) with ESMTP id 76F8437B400 for ; Fri, 31 May 2002 10:32:39 -0700 (PDT) Received: (from ru@localhost) by whale.sunbay.crimea.ua (8.11.6/8.11.2) id g4VHWBc89680; Fri, 31 May 2002 20:32:11 +0300 (EEST) (envelope-from ru) Date: Fri, 31 May 2002 20:32:11 +0300 From: Ruslan Ermilov To: Stephen Hilton Cc: freebsd-stable@freebsd.org, thrawn@linux.nu Subject: Re: Problems when runing make installworld. Message-ID: <20020531173211.GC88599@sunbay.com> References: <20020528071935.GD53736@sunbay.com> <20020531090140.V40770-200000@thrawn.birch.se> <20020531090156.GB27669@sunbay.com> <20020531115553.3aff789f.nospam@hiltonbsd.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GZVR6ND4mMseVXL/" Content-Disposition: inline In-Reply-To: <20020531115553.3aff789f.nospam@hiltonbsd.com> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --GZVR6ND4mMseVXL/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 31, 2002 at 11:55:53AM -0500, Stephen Hilton wrote: > On Fri, 31 May 2002 12:01:56 +0300 > Ruslan Ermilov wrote: >=20 > > On Fri, May 31, 2002 at 09:06:23AM +0200, Mattias Bj?rk wrote: > > > Hi, Again, thanks for the answer, i read > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D30276. > > >=20 > > > It says there that if you are building make world with a p3 and run > > > make installworld on a 486 you get this error. But I don't have a > > > p3 I have a dual celeron, I have also attached my make.conf from > > > the building machine. And its a p90 that Im makeing the make > > > worldinstall on. But any way the problem seams too be the same or > > > am I wrong? > > >=20 > > Did you set CPUTYPE=3Di586 just before doing a buildworld? Was it by > > chance set to CPUTYPE=3Di686 before? > >=20 > > If that's the case, your /usr/lib stuff on the build box has some P6 > > CPU instructions, and some tools (like install(1) and strip(1)) that > > are used during installworld on your Pentium box use these libraries > > and fail. To work around this, you'll have to: > >=20 > > 1. Rebuild and reinstall world/kernel on your build box with the > > compatible (with your install box) CPUTYPE setting like > > CPUTYPE=3Di586. > >=20 > > 2. Reboot with the new kernel and world. > >=20 > > 3. Build the world again (!). > >=20 > > 4. Install this second world on a Pentium box. > >=20 >=20 > Ruslan, >=20 > This is good information to have, but it brings to mind, how=20 > do the release engineers build a release that will install=20 > binaries, and then allow you to run a buildworld on machines=20 > types from a Intel 386 to an AMD Athlon? >=20 > Is it a matter of using the lowest common denominator? and=20 > the release building hardware is running the operating=20 > system with out any optimizations? >=20 Yes. "make release" builds the world in a "pristine", chroot(8) environment, where /etc/make.conf is empty. See release(7) for details. > P.S. and to keep this "On-Topic" for the stable list, my=20 > buildworlds and systems have been running great on 4.6-Pre, > Great work and kudos to the Project members and contributers. >=20 Thanks. :-) Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --GZVR6ND4mMseVXL/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE897ObUkv4P6juNwoRAoBEAJ4yfrfrMno5TmqpUU2tf+DXFPLOMgCfbzZw 6w6hUxbXZxYv1vbjZ+pWdr4= =VwkF -----END PGP SIGNATURE----- --GZVR6ND4mMseVXL/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 11:23:20 2002 Delivered-To: freebsd-stable@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-107-187.dsl.lsan03.pacbell.net [64.169.107.187]) by hub.freebsd.org (Postfix) with ESMTP id 6D2D637B406; Fri, 31 May 2002 11:23:06 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C436F66B8B; Fri, 31 May 2002 11:23:05 -0700 (PDT) Date: Fri, 31 May 2002 11:23:05 -0700 From: Kris Kennaway To: Ruslan Ermilov Cc: Kris Kennaway , Mattias Bj?rk , stable@FreeBSD.ORG Subject: Re: Problems when runing make installworld. Message-ID: <20020531112305.A29796@xor.obsecurity.org> References: <20020528071935.GD53736@sunbay.com> <20020531090140.V40770-200000@thrawn.birch.se> <20020531102126.A28135@xor.obsecurity.org> <20020531172937.GB88599@sunbay.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020531172937.GB88599@sunbay.com>; from ru@FreeBSD.ORG on Fri, May 31, 2002 at 08:29:37PM +0300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 31, 2002 at 08:29:37PM +0300, Ruslan Ermilov wrote: > On Fri, May 31, 2002 at 10:21:26AM -0700, Kris Kennaway wrote: > > On Fri, May 31, 2002 at 09:06:23AM +0200, Mattias Bj?rk wrote: > > > Hi, Again, thanks for the answer, i read > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D30276. > > >=20 > > > It says there that if you are building make world with a p3 and run m= ake installworld on a 486 > > > you get this error. But I don't have a p3 I have a dual celeron, I ha= ve > > > also attached my make.conf from the building machine. And its a p90 t= hat > > > Im makeing the make worldinstall on. But any way the problem seams to= o be > > > the same or am I wrong? > >=20 > > The point is when you try and install a world built with different CPU > > optimizations. I assume you have CPUTYPE set on your build machine; > > this is what controls the optimizations that will be used when you > > build world, so it's obviously not going to work when you compile your > > binaries for a Pentium Pro and try and install them on a Pentium. > >=20 > No, the problem is worse. Oh, that's right; I'd forgotten the details of the problem. My point still stands that it doesn't depend on the p3/486 combination but only on installing on a different CPU type than the build system. Kris --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE897+IWry0BWjoQKURAi9OAJ9VzZETUnZvJOrWy+azZHNHayoxawCg8IbD iuYBFEGUHSJycSZleIq9Hb8= =B5nB -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 11:32:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 5A56737B403; Fri, 31 May 2002 11:32:09 -0700 (PDT) Received: from whizzo.transsys.com (#6@localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.12.3/8.12.3) with ESMTP id g4VIW8IY091328; Fri, 31 May 2002 14:32:08 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200205311832.g4VIW8IY091328@whizzo.transsys.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: bmah@FreeBSD.ORG Cc: freebsd-qa@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, re@FreeBSD.ORG X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" Subject: Re: 4.6-RELEASE delayed References: <200205311652.g4VGq5YV004136@intruder.bmah.org> In-reply-to: Your message of "Fri, 31 May 2002 09:52:05 PDT." <200205311652.g4VGq5YV004136@intruder.bmah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 May 2002 14:32:08 -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Just some feedback, perhaps for release notes regarding the new dhclient DHCP client program. I've been using FreeBSD 4-STABLE in an embedded system environment (Soekris net4501) where the system boots and runs a stripped down FreeBSD installation from a Compact Flash card. I had a dhclient-related problem when upgrading to a version with the new dhclient. If the dhclient-script exits abnormally, then the dhclient program again attempts to acquire an address from the DHCP server. In my environment, the root file system is mounted read-only, and the dhclient-script shell script fails when it attempts to update /etc/resolv.conf with the name servers and default domain returned from the DHCP server. The system would pause indefinately during boot repeatedly trying to get an IP address, and then failing to update the read-only /etc/resolv.conf file. It also leaves a route for each address it acquired on the loopback interface which is not removed when the next attempt is made. You can't configure the "update /etc/resolv.conf" behavior, so I had to manually edit the /sbin/dhclient-script to resolve this issue. The older version of /sbin/dhclient ignored the error when trying to update /etc/resolv.conf. Louis Mamakos To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 11:48:16 2002 Delivered-To: freebsd-stable@freebsd.org Received: from cheer.mahoroba.org (flets19-004.kamome.or.jp [218.45.19.4]) by hub.freebsd.org (Postfix) with ESMTP id ED24337B404; Fri, 31 May 2002 11:48:05 -0700 (PDT) Received: from mille.mahoroba.org (IDENT:UsCakVATBHokzH8ULmlWz0C+wU/MKb9DY4sA4TLpECsqclrsCZwDiEUlteVF2hsO@mille.mahoroba.org [IPv6:2001:200:301:0:202:2dff:fe0a:6bee]) (user=ume mech=CRAM-MD5 bits=0) by cheer.mahoroba.org (8.12.3/8.12.3) with ESMTP/inet6 id g4VIm2LE040955 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 1 Jun 2002 03:48:02 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Sat, 01 Jun 2002 03:48:01 +0900 Message-ID: From: Hajimu UMEMOTO To: "Louis A. Mamakos" Cc: bmah@FreeBSD.ORG, freebsd-qa@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, re@FreeBSD.ORG Subject: Re: 4.6-RELEASE delayed In-Reply-To: <200205311832.g4VIW8IY091328@whizzo.transsys.com> References: <200205311652.g4VGq5YV004136@intruder.bmah.org> <200205311832.g4VIW8IY091328@whizzo.transsys.com> User-Agent: xcite1.38> Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2 (i386--freebsd) MULE/5.0 (=?ISO-2022-JP?B?GyRCOC1MWhsoQg==?=) X-Operating-System: FreeBSD 4.6-PRERELEASE MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, >>>>> On Fri, 31 May 2002 14:32:08 -0400 >>>>> "Louis A. Mamakos" said: louie> You can't configure the "update /etc/resolv.conf" behavior, so I had louie> to manually edit the /sbin/dhclient-script to resolve this issue. You can re-define make_resolv_conf() in /etc/dhclient-enter-hooks to don't update /etc/resolv.conf. Please refer dhclient-script(8) manpage. Sincerely, -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 12: 8:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.pilikia.net (ns1.pilikia.net [66.180.134.50]) by hub.freebsd.org (Postfix) with ESMTP id DA55337B406 for ; Fri, 31 May 2002 12:08:31 -0700 (PDT) Received: from uluru.local.net (uluru.local.net [10.25.0.4]) by ns1.pilikia.net (8.11.6/8.11.6) with ESMTP id g4VJ8Pu70741 for ; Fri, 31 May 2002 09:08:25 -1000 (HST) (envelope-from art@pilikia.net) Received: from gecko (gecko.local.net [10.25.0.9]) by uluru.local.net (8.11.6/8.11.6) with ESMTP id g4VJ8Pe05536 for ; Fri, 31 May 2002 09:08:25 -1000 (HST) (envelope-from art@pilikia.net) Message-ID: <200205310908250689.20627768@10.25.0.4> X-Mailer: Calypso Version 3.30.00.00 (4) Date: Fri, 31 May 2002 09:08:25 -1000 Reply-To: art@pilikia.net From: "Arthur W. Neilson III" To: freebsd-stable@freebsd.org Subject: perlMX Content-Type: text/plain; charset="us-ascii" X-Virus-Scanned: by AMaViS/NAI-uvscan-4.14 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Has anyone evaluated or purchased the new product PerlMX http://www.activestate.com/Products/PerlMX from ActiveState? We currently use Amavis with NAI's uvscan to scan mail being relayed by sendmail on our FreeBSD 4.4 mail exchangers. We plan to upgrade to 4-stable and use the 8.12.3 sendmail with the milter interface for either Amavis or a commercial product such as PerlMX. -- __ / ) _/_ It is a capital mistake to theorise before one has data. /--/ __ / Insensibly one begins to twist facts to suit theories, / (_/ (_<__ Instead of theories to suit facts. -- Sherlock Holmes, "A Scandal in Bohemia" Arthur W. Neilson III, WH7N - FISTS #7448 Bank of Hawaii Network Services http://www.pilikia.net art@pilikia.net, aneilson@boh.com, wh7n@arrl.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 12: 9:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from blue.mcneil.com (cpe-66-75-176-109.socal.rr.com [66.75.176.109]) by hub.freebsd.org (Postfix) with ESMTP id 39D8F37B405 for ; Fri, 31 May 2002 12:09:46 -0700 (PDT) Received: from mcneil.com (mcneil.com [66.75.176.109]) by blue.mcneil.com (8.12.3/8.12.3) with ESMTP id g4VJ9qnR081916 for ; Fri, 31 May 2002 12:09:52 -0700 (PDT) (envelope-from sean@mcneil.com) Subject: new dhcp client causing problems From: Sean McNeil To: freebsd-stable@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 31 May 2002 12:09:52 -0700 Message-Id: <1022872192.81856.2.camel@blue.mcneil.com> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I've noticed that I occasionally lose connections through my computer to the internet. This has been happening because the dhcp client is trying to change my ip to something bogus and resetting the ethernet: May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 May 30 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 May 31 02:38:07 blue su: sean to root on /dev/ttyp0 The previous dhcp client in 4.5 did not do this. It is only happening with the 4.6-RC. Cheers, Sean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 13: 3: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.27in.tv (roc-24-169-198-248.rochester.rr.com [24.169.198.248]) by hub.freebsd.org (Postfix) with ESMTP id C8FEF37B401 for ; Fri, 31 May 2002 13:02:59 -0700 (PDT) Received: (from root@localhost) by mail.27in.tv (8.12.3/8.11.6) id g4VK2wc8033572; Fri, 31 May 2002 16:02:58 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from 27in.tv (localhost [127.0.0.1]) by mail.27in.tv (8.12.3/8.11.6av) with SMTP id g4VK2uTI033562; Fri, 31 May 2002 16:02:56 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from 216.153.201.118 (SquirrelMail authenticated user cjm2) by www.27in.tv with HTTP; Fri, 31 May 2002 16:02:57 -0400 (EDT) Message-ID: <2432.216.153.201.118.1022875377.squirrel@www.27in.tv> Date: Fri, 31 May 2002 16:02:57 -0400 (EDT) Subject: dhclient on ro filesystems [Was: 4.6-RELEASE delayed] From: "C J Michaels" To: In-Reply-To: References: <200205311652.g4VGq5YV004136@intruder.bmah.org> <200205311832.g4VIW8IY091328@whizzo.transsys.com> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: , X-Mailer: SquirrelMail (version 1.3.0 [CVS-DEVEL]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hajimu UMEMOTO said: > Hi, > >>>>>> On Fri, 31 May 2002 14:32:08 -0400 >>>>>> "Louis A. Mamakos" said: > > louie> You can't configure the "update /etc/resolv.conf" behavior, so I > had louie> to manually edit the /sbin/dhclient-script to resolve this > issue. I ran the exact same problem about a week ago. In retro-spect I should have put in a PR (sorry about that). I'll try and put one together this weekend if there isn't already one. (Did you submit one Louie?) > > You can re-define make_resolv_conf() in /etc/dhclient-enter-hooks to > don't update /etc/resolv.conf. Please refer dhclient-script(8) > manpage. While this would be a short-term fix. This problem should be treated as a bug. If /etc/resolv.conf isn't writable, dhclient should print an error and exit (previous behavior). Not get stuck in an infinite loop, requesting a new lease every ~5 seconds. > > Sincerely, > > -- > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan > ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org > http://www.imasy.org/~ume/ > -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 13:18:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.27in.tv (roc-24-169-198-248.rochester.rr.com [24.169.198.248]) by hub.freebsd.org (Postfix) with ESMTP id 313B137B405 for ; Fri, 31 May 2002 13:18:32 -0700 (PDT) Received: (from root@localhost) by mail.27in.tv (8.12.3/8.11.6) id g4VKIVfs033926; Fri, 31 May 2002 16:18:31 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from 27in.tv (localhost [127.0.0.1]) by mail.27in.tv (8.12.3/8.11.6av) with SMTP id g4VKITTI033916; Fri, 31 May 2002 16:18:30 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from 216.153.201.118 (SquirrelMail authenticated user cjm2) by www.27in.tv with HTTP; Fri, 31 May 2002 16:18:30 -0400 (EDT) Message-ID: <2453.216.153.201.118.1022876310.squirrel@www.27in.tv> Date: Fri, 31 May 2002 16:18:30 -0400 (EDT) Subject: Re: new dhcp client causing problems From: "C J Michaels" To: In-Reply-To: <1022872192.81856.2.camel@blue.mcneil.com> References: <1022872192.81856.2.camel@blue.mcneil.com> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.3.0 [CVS-DEVEL]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sean McNeil said: > Hi, > > I've noticed that I occasionally lose connections through my computer to > the internet. This has been happening because the dhcp client is trying > to change my ip to something bogus and resetting the ethernet: Can you give an example of the 'bogus' ip address it's trying to set? What you have listed below (without any additional information) appears to be valid. (Note: no ip address is actually listed.) > > May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 > May 30 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 Yes, I did note the broadcast address, my dhclient is pulling the same broadcast addr (RoadRunner) and I have no problems. I believe this may actually be an issue w/ a mis-configured dhcpd not dhclient. > May 31 02:38:07 blue su: sean to root on /dev/ttyp0 > > The previous dhcp client in 4.5 did not do this. It is only happening > with the 4.6-RC. > > Cheers, > Sean -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 13:31:33 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id BF36E37B408 for ; Fri, 31 May 2002 13:31:26 -0700 (PDT) Received: from merlin.emma.line.org (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id B6F04A3831 for ; Fri, 31 May 2002 22:31:24 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 168AD36C8C; Fri, 31 May 2002 22:31:20 +0200 (CEST) To: freebsd-stable@freebsd.org Subject: Re: 4.6-RELEASE delayed References: <200205311652.g4VGq5YV004136@intruder.bmah.org> In-Reply-To: <200205311652.g4VGq5YV004136@intruder.bmah.org> (bmah@freebsd.org's message of "Fri, 31 May 2002 09:52:05 -0700") From: Matthias Andree Date: Fri, 31 May 2002 22:31:19 +0200 Message-ID: Lines: 36 User-Agent: Gnus/5.090007 (Oort Gnus v0.07) Emacs/21.1 (i686-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG bmah@freebsd.org (Bruce A. Mah) writes: > We'll be doing another release candidate (4.6-RC4...for various > reasons I appreciate this. > there won't be a 4.6-RC3) on Monday, in which we hope to see the major > remaining issues addressed. We encourage you to see the testing page > for this release at: > > http://www.freebsd.org/releases/4.6R/qa.html It says ata(4) tags problems were related to motherboard-based ATA channels. I see that S=F8ren's patch to fix the panic on boot that I observed has now been merged into 4-STABLE, however, it seems as though the "timeout and fall-back to PIO" issue is still unfixed in 4-STABLE. My main board, a Gigabyte 7ZX-R rev. 1.0, offers four ATA channels. Two are driven by the south bridge, VIA KT133 (VT82C686 stuff), the other two are driven by a Promise PDC-20265R (in UDMA/100 mode). IIRC, this Promise chip is in the "doesn't to tags, but freezes" blacklist. VIA chips are not blacklisted, and AFAICS, tagged queueing not working on my system is a regression over 4.5-RELEASE which had working tagged queueing. S=F8ren said he was able to reproduce the timeout problem with tags, and we should expect a fix "real soon now". This is the only list I follow, but I haven't yet seen anything ata-related since. What's the release engineering team's opinion on this ata issue? Will 4.6 be delayed until the tagged stuff is fixed? Will 4.6 ship with ata tagged stuff disabled altogether? Or will 4.6 ship with ata as it is today, with the risk that it breaks some systems 4.5 ata did work on? --=20 Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 13:50:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tntpro.com (dsl-207-5-188-75.gwi.net [207.5.188.75]) by hub.freebsd.org (Postfix) with ESMTP id 9DA6837B400 for ; Fri, 31 May 2002 13:49:15 -0700 (PDT) Received: from celery (celery.tntpro.com [192.168.0.13]) by tntpro.com (8.12.3/8.12.3) with ESMTP id g4VKlr31004178; Fri, 31 May 2002 16:47:53 -0400 (EDT) (envelope-from tony@tntpro.com) From: "tony" To: "'C J Michaels'" , Cc: Subject: RE: new dhcp client causing problems Date: Fri, 31 May 2002 16:49:27 -0400 Message-ID: <07f401c208e4$a7a8f9f0$0d00a8c0@celery> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <2453.216.153.201.118.1022876310.squirrel@www.27in.tv> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Since updating to 4.6R I seem to be having the same problem May 31 03:21:42 tntpro dhclient: New Network Number: 192.168.0.0 May 31 03:21:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 31 08:14:03 tntpro dhclient: New Network Number: 192.168.0.0 May 31 08:14:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 31 13:46:04 tntpro dhclient: New Network Number: 192.168.0.0 May 31 13:46:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 root:~# ifconfig -a xl0: flags=8843 mtu 1500 options=3 inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:50:da:c2:a1:48 media: Ethernet autoselect (100baseTX ) status: active lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 Here is a grep just for fun notice it gets a new addy every 5 minutes most of the time root:~# grep dhclient /var/log/messages May 27 01:02:12 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:02:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:06:09 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:06:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:10:24 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:10:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:14:39 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:14:39 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:19:19 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:19:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:23:31 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:23:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:27:27 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:27:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:31:27 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:31:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:36:05 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:36:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:40:19 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:40:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:45:04 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:45:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:48:57 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:48:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:53:26 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:53:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 01:58:13 tntpro dhclient: New Network Number: 192.168.0.0 May 27 01:58:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:02:23 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:02:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:06:51 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:06:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:10:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:10:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:15:26 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:15:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:20:19 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:20:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:25:08 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:25:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:29:19 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:29:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:33:40 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:33:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:38:29 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:38:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:43:11 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:43:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:48:06 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:48:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:52:52 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:52:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 02:57:43 tntpro dhclient: New Network Number: 192.168.0.0 May 27 02:57:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:02:18 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:02:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:06:29 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:06:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:10:56 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:10:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:15:15 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:15:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:19:49 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:19:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:23:57 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:23:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:28:12 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:28:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:32:22 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:32:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:37:15 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:37:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:42:02 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:42:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:46:29 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:46:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:51:07 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:51:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:55:34 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:55:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 03:59:25 tntpro dhclient: New Network Number: 192.168.0.0 May 27 03:59:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:04:25 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:04:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:09:19 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:09:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:13:37 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:13:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:18:21 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:18:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:22:25 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:22:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:26:43 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:26:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:31:32 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:31:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:35:33 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:35:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:40:02 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:40:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:44:25 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:44:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:48:50 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:48:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:52:50 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:52:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 04:57:00 tntpro dhclient: New Network Number: 192.168.0.0 May 27 04:57:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:00:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:00:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:04:45 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:04:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:09:13 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:09:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:13:28 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:13:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:17:25 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:17:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:21:39 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:21:39 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:25:36 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:25:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:29:58 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:29:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:33:57 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:33:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:38:32 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:38:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:43:25 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:43:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:48:22 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:48:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:53:03 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:53:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 05:57:16 tntpro dhclient: New Network Number: 192.168.0.0 May 27 05:57:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:01:17 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:01:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:05:15 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:05:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:09:45 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:09:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:14:20 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:14:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:19:08 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:19:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:23:16 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:23:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:27:41 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:27:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:32:08 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:32:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:36:42 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:36:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:41:35 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:41:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:45:22 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:45:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:49:49 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:49:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:53:44 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:53:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 06:58:42 tntpro dhclient: New Network Number: 192.168.0.0 May 27 06:58:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:03:14 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:03:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:07:11 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:07:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:11:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:11:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:16:02 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:16:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:20:10 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:20:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:24:02 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:24:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:28:44 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:28:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:33:26 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:33:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:38:04 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:38:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:42:34 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:42:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:47:10 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:47:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:51:34 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:51:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 07:55:26 tntpro dhclient: New Network Number: 192.168.0.0 May 27 07:55:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:00:23 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:00:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:05:16 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:05:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:09:56 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:09:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:13:57 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:13:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:18:34 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:18:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:23:23 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:23:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:27:46 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:27:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:31:38 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:31:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:36:32 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:36:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:41:03 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:41:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:45:45 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:45:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:49:53 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:49:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:54:53 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:54:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 08:58:51 tntpro dhclient: New Network Number: 192.168.0.0 May 27 08:58:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:03:52 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:03:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:08:46 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:08:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:12:40 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:12:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:17:27 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:17:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:22:04 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:22:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:25:54 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:25:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:29:59 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:29:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:34:15 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:34:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:39:15 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:39:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:43:51 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:43:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:48:49 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:48:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:53:42 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:53:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 09:58:36 tntpro dhclient: New Network Number: 192.168.0.0 May 27 09:58:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:02:51 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:02:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:07:37 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:07:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:12:20 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:12:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:16:17 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:16:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:20:10 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:20:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:24:35 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:24:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:28:53 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:28:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:33:24 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:33:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:37:27 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:37:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:41:38 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:41:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:46:12 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:46:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:50:32 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:50:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:55:00 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:55:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 10:59:03 tntpro dhclient: New Network Number: 192.168.0.0 May 27 10:59:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:03:24 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:03:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:07:32 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:07:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:11:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:11:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:16:29 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:16:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:20:34 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:20:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:24:33 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:24:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:29:19 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:29:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:34:15 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:34:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:38:20 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:38:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:42:34 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:42:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:46:52 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:46:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:51:35 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:51:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 11:56:13 tntpro dhclient: New Network Number: 192.168.0.0 May 27 11:56:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:00:24 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:00:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:05:23 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:05:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:09:37 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:09:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:13:49 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:13:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:18:23 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:18:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:22:42 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:22:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:26:46 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:26:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:31:43 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:31:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:36:22 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:36:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:40:43 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:40:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:44:54 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:44:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:49:19 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:49:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:54:09 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:54:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 12:58:02 tntpro dhclient: New Network Number: 192.168.0.0 May 27 12:58:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:03:01 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:03:01 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:07:00 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:07:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:11:16 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:11:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:15:41 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:15:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:20:37 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:20:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:24:55 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:24:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:29:31 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:29:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:33:40 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:33:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:38:34 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:38:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:43:11 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:43:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:47:24 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:47:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:52:19 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:52:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 13:56:44 tntpro dhclient: New Network Number: 192.168.0.0 May 27 13:56:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:00:35 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:00:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:04:25 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:04:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:08:36 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:08:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:13:08 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:13:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:18:09 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:18:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:23:10 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:23:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:27:30 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:27:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:31:50 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:31:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:36:17 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:36:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:40:10 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:40:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:45:10 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:45:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:49:54 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:49:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:54:54 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:54:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 14:59:15 tntpro dhclient: New Network Number: 192.168.0.0 May 27 14:59:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:03:14 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:03:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:07:53 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:07:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:12:32 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:12:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:16:46 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:16:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:21:30 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:21:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:26:23 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:26:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:30:36 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:30:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:35:11 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:35:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:39:10 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:39:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:43:00 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:43:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:47:00 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:47:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:51:04 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:51:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:55:05 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:55:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 15:59:06 tntpro dhclient: New Network Number: 192.168.0.0 May 27 15:59:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:03:29 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:03:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:08:12 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:08:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:11:59 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:11:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:16:28 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:16:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:21:21 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:21:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:25:16 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:25:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:29:24 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:29:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:33:18 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:33:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:37:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:37:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:42:35 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:42:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:47:01 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:47:01 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:50:57 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:50:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:54:48 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:54:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 16:59:16 tntpro dhclient: New Network Number: 192.168.0.0 May 27 16:59:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:03:57 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:03:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:07:52 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:07:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:12:38 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:12:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:17:06 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:17:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:20:53 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:20:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:25:46 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:25:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:30:05 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:30:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:34:09 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:34:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:38:48 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:38:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:43:30 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:43:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:47:50 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:47:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:52:28 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:52:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 17:56:51 tntpro dhclient: New Network Number: 192.168.0.0 May 27 17:56:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:01:05 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:01:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:05:33 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:05:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:09:57 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:09:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:13:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:13:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:17:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:17:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:21:46 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:21:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:25:57 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:25:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:30:01 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:30:01 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:34:20 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:34:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:39:14 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:39:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:43:06 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:43:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:47:20 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:47:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:51:48 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:51:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 18:56:31 tntpro dhclient: New Network Number: 192.168.0.0 May 27 18:56:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:00:53 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:00:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:05:12 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:05:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:09:35 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:09:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:13:55 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:13:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:18:54 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:18:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:23:53 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:23:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:28:04 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:28:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:32:10 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:32:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:36:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:36:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:41:37 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:41:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:46:26 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:46:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:50:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:50:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:54:36 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:54:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 19:58:31 tntpro dhclient: New Network Number: 192.168.0.0 May 27 19:58:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:02:43 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:02:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:06:45 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:06:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:11:08 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:11:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:15:43 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:15:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:19:30 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:19:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:23:18 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:23:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:27:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:27:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:31:48 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:31:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:35:43 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:35:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:39:46 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:39:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:43:56 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:43:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:48:27 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:48:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:52:29 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:52:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 20:57:11 tntpro dhclient: New Network Number: 192.168.0.0 May 27 20:57:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:01:40 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:01:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:05:42 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:05:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:10:28 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:10:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:15:08 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:15:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:19:03 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:19:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:23:37 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:23:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:27:33 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:27:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:31:55 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:31:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:36:29 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:36:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:41:28 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:41:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:45:51 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:45:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:50:47 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:50:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:54:58 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:54:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 21:59:55 tntpro dhclient: New Network Number: 192.168.0.0 May 27 21:59:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:04:00 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:04:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:08:50 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:08:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:13:22 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:13:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:17:39 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:17:39 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:22:28 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:22:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:26:41 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:26:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:31:31 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:31:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:36:14 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:36:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:40:25 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:40:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:45:07 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:45:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:49:14 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:49:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:53:07 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:53:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 22:58:05 tntpro dhclient: New Network Number: 192.168.0.0 May 27 22:58:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:02:33 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:02:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:07:27 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:07:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:11:28 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:11:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:15:56 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:15:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:20:09 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:20:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:24:53 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:24:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:29:20 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:29:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:34:18 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:34:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:38:45 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:38:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:43:14 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:43:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:47:12 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:47:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:52:06 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:52:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 27 23:56:32 tntpro dhclient: New Network Number: 192.168.0.0 May 27 23:56:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:01:31 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:01:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:06:28 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:06:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:11:07 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:11:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:16:00 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:16:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:20:14 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:20:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:24:11 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:24:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:28:58 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:28:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:32:49 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:32:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:37:22 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:37:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:41:21 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:41:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:46:12 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:46:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:50:03 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:50:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:54:18 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:54:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 00:59:19 tntpro dhclient: New Network Number: 192.168.0.0 May 28 00:59:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:03:41 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:03:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:08:30 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:08:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:12:56 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:12:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:17:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:17:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:22:12 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:22:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:26:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:26:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:30:30 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:30:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:35:25 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:35:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:40:13 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:40:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:44:34 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:44:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:49:31 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:49:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:54:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:54:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 01:58:27 tntpro dhclient: New Network Number: 192.168.0.0 May 28 01:58:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:03:22 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:03:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:07:34 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:07:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:11:54 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:11:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:15:49 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:15:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:20:22 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:20:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:24:41 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:24:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:28:46 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:28:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:32:36 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:32:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:37:20 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:37:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:42:06 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:42:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:46:22 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:46:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:50:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:50:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:54:52 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:54:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 02:59:44 tntpro dhclient: New Network Number: 192.168.0.0 May 28 02:59:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:03:40 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:03:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:08:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:08:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:12:30 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:12:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:17:04 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:17:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:21:22 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:21:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:25:49 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:25:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:30:33 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:30:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:34:55 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:34:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:38:44 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:38:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:43:33 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:43:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:47:21 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:47:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:51:19 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:51:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 03:56:15 tntpro dhclient: New Network Number: 192.168.0.0 May 28 03:56:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:01:13 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:01:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:05:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:05:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:10:00 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:10:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:14:23 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:14:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:18:36 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:18:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:23:14 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:23:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:27:38 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:27:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:31:33 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:31:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:35:59 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:35:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:39:46 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:39:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:43:52 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:43:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:48:45 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:48:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:52:48 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:52:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 04:57:28 tntpro dhclient: New Network Number: 192.168.0.0 May 28 04:57:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:01:15 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:01:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:06:11 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:06:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:10:48 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:10:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:15:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:15:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:19:29 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:19:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:24:25 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:24:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:28:54 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:28:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:33:15 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:33:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:37:31 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:37:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:41:24 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:41:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:45:20 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:45:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:49:52 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:49:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:53:54 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:53:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 05:57:53 tntpro dhclient: New Network Number: 192.168.0.0 May 28 05:57:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:01:46 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:01:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:05:45 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:05:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:10:38 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:10:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:15:20 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:15:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:19:51 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:19:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:24:08 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:24:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:28:58 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:28:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:33:22 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:33:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:38:18 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:38:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:42:16 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:42:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:47:11 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:47:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:52:08 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:52:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 06:56:25 tntpro dhclient: New Network Number: 192.168.0.0 May 28 06:56:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:00:20 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:00:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:04:38 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:04:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:08:55 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:08:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:12:58 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:12:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:17:06 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:17:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:20:56 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:20:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:25:09 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:25:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:29:41 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:29:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:33:53 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:33:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:38:38 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:38:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:43:05 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:43:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:47:06 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:47:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:51:23 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:51:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:55:33 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:55:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 07:59:30 tntpro dhclient: New Network Number: 192.168.0.0 May 28 07:59:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:04:00 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:04:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:07:47 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:07:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:12:19 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:12:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:16:20 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:16:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:20:56 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:20:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:25:29 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:25:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:29:30 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:29:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:33:18 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:33:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:37:13 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:37:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:42:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:42:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:46:41 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:46:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:50:48 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:50:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:54:53 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:54:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 08:59:45 tntpro dhclient: New Network Number: 192.168.0.0 May 28 08:59:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:04:25 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:04:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:09:23 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:09:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:13:36 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:13:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:18:36 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:18:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:22:26 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:22:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:26:48 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:26:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:31:23 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:31:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:36:09 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:36:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:40:52 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:40:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:44:41 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:44:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:49:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:49:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:53:29 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:53:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 09:58:18 tntpro dhclient: New Network Number: 192.168.0.0 May 28 09:58:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:03:14 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:03:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:07:59 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:07:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:12:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:12:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:16:11 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:16:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:20:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:20:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:24:43 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:24:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:28:44 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:28:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:32:53 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:32:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:37:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:37:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:41:34 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:41:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:46:26 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:46:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:51:09 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:51:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:55:06 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:55:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 10:59:34 tntpro dhclient: New Network Number: 192.168.0.0 May 28 10:59:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:03:32 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:03:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:08:09 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:08:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:13:00 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:13:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:17:58 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:17:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:22:08 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:22:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:26:58 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:26:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:31:13 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:31:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:35:45 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:35:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:40:11 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:40:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:44:43 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:44:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:48:48 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:48:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:52:51 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:52:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 11:56:40 tntpro dhclient: New Network Number: 192.168.0.0 May 28 11:56:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:01:19 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:01:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:06:19 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:06:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:10:38 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:10:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:14:26 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:14:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:18:34 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:18:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:23:30 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:23:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:27:50 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:27:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:31:42 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:31:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:35:36 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:35:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:39:56 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:39:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:43:49 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:43:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:47:36 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:47:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:52:33 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:52:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 12:57:21 tntpro dhclient: New Network Number: 192.168.0.0 May 28 12:57:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:02:03 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:02:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:06:52 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:06:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:11:32 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:11:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:15:23 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:15:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:19:34 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:19:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:24:31 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:24:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:28:43 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:28:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:33:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:33:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:37:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:37:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:41:54 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:41:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:46:13 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:46:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:50:51 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:50:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:54:51 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:54:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 13:59:22 tntpro dhclient: New Network Number: 192.168.0.0 May 28 13:59:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:03:32 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:03:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:08:31 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:08:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:12:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:12:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:17:28 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:17:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:22:29 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:22:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:27:15 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:27:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:31:30 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:31:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:35:40 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:35:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:40:17 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:40:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:44:18 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:44:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:49:08 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:49:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:53:04 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:53:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 14:57:55 tntpro dhclient: New Network Number: 192.168.0.0 May 28 14:57:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:01:55 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:01:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:06:47 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:06:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:11:13 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:11:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:16:05 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:16:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:20:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:20:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:25:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:25:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:30:22 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:30:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:35:06 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:35:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:39:43 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:39:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:44:21 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:44:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:48:26 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:48:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:52:52 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:52:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 15:57:45 tntpro dhclient: New Network Number: 192.168.0.0 May 28 15:57:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:02:30 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:02:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:07:12 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:07:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:11:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:11:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:15:50 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:15:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:20:05 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:20:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:24:11 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:24:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:28:03 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:28:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:31:54 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:31:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:35:42 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:35:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:39:59 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:39:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:44:21 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:44:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:48:31 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:48:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:53:13 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:53:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 16:58:06 tntpro dhclient: New Network Number: 192.168.0.0 May 28 16:58:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:01:58 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:01:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:06:39 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:06:39 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:11:02 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:11:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:15:02 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:15:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:18:53 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:18:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:22:45 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:22:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:27:32 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:27:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:31:23 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:31:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:36:17 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:36:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:40:26 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:40:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:44:14 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:44:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:48:07 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:48:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:52:05 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:52:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 17:55:54 tntpro dhclient: New Network Number: 192.168.0.0 May 28 17:55:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:00:05 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:00:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:04:33 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:04:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:08:49 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:08:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:13:47 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:13:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:18:28 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:18:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:22:56 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:22:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:26:46 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:26:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:30:55 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:30:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:35:31 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:35:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:39:25 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:39:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:44:16 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:44:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:49:06 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:49:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 18:55:37 tntpro dhclient: New Network Number: 192.168.0.0 May 28 18:55:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 20:45:10 tntpro dhclient: New Network Number: 192.168.0.0 May 28 20:45:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 28 20:45:10 tntpro dhclient: New IP Address (xl0): 192.168.0.100 May 28 20:45:10 tntpro dhclient: New Subnet Mask (xl0): 255.255.255.0 May 28 20:45:10 tntpro dhclient: New Broadcast Address (xl0): 192.168.0.255 May 28 20:45:10 tntpro dhclient: New Routers: 192.168.0.1 May 29 01:47:45 tntpro dhclient: New Network Number: 192.168.0.0 May 29 01:47:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 29 07:36:42 tntpro dhclient: New Network Number: 192.168.0.0 May 29 07:36:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 29 12:17:01 tntpro dhclient: New Network Number: 192.168.0.0 May 29 12:17:01 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 29 16:52:50 tntpro dhclient: New Network Number: 192.168.0.0 May 29 16:52:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 29 21:29:36 tntpro dhclient: New Network Number: 192.168.0.0 May 29 21:29:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 30 02:23:28 tntpro dhclient: New Network Number: 192.168.0.0 May 30 02:23:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 30 07:46:05 tntpro dhclient: New Network Number: 192.168.0.0 May 30 07:46:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 30 12:51:40 tntpro dhclient: New Network Number: 192.168.0.0 May 30 12:51:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 30 17:49:23 tntpro dhclient: New Network Number: 192.168.0.0 May 30 17:49:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 31 03:21:42 tntpro dhclient: New Network Number: 192.168.0.0 May 31 03:21:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 31 08:14:03 tntpro dhclient: New Network Number: 192.168.0.0 May 31 08:14:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 31 13:46:04 tntpro dhclient: New Network Number: 192.168.0.0 May 31 13:46:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 root:~# -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of C J Michaels Sent: Friday, May 31, 2002 4:19 PM To: sean@mcneil.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: new dhcp client causing problems Sean McNeil said: > Hi, > > I've noticed that I occasionally lose connections through my computer > to the internet. This has been happening because the dhcp client is > trying to change my ip to something bogus and resetting the ethernet: Can you give an example of the 'bogus' ip address it's trying to set? What you have listed below (without any additional information) appears to be valid. (Note: no ip address is actually listed.) > > May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 May 30 > 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 Yes, I did note the broadcast address, my dhclient is pulling the same broadcast addr (RoadRunner) and I have no problems. I believe this may actually be an issue w/ a mis-configured dhcpd not dhclient. > May 31 02:38:07 blue su: sean to root on /dev/ttyp0 > > The previous dhcp client in 4.5 did not do this. It is only happening > with the 4.6-RC. > > Cheers, > Sean -- Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 14:12:23 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ntplx.net (mail7.ntplx.net [204.213.176.181]) by hub.freebsd.org (Postfix) with ESMTP id B39F837B40C for ; Fri, 31 May 2002 14:11:39 -0700 (PDT) Received: from ntplx.net (dhcp-209-54-72-110.ct.dsl.ntplx.com [209.54.72.110]) by mail.ntplx.net (8.11.6/8.11.4/NETPLEX) with ESMTP id g4VLBcD14076 for ; Fri, 31 May 2002 17:11:38 -0400 (EDT) Message-ID: <3CF7E836.742CD559@ntplx.net> Date: Fri, 31 May 2002 17:16:38 -0400 From: Ted Sikora X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.18 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: new dhcp client causing problems References: <1022872192.81856.2.camel@blue.mcneil.com> <2453.216.153.201.118.1022876310.squirrel@www.27in.tv> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG C J Michaels wrote: > > Sean McNeil said: > > Hi, > > > > I've noticed that I occasionally lose connections through my computer to > > the internet. This has been happening because the dhcp client is trying > > to change my ip to something bogus and resetting the ethernet: > > Can you give an example of the 'bogus' ip address it's trying to set? > What you have listed below (without any additional information) appears to > be valid. (Note: no ip address is actually listed.) > > > > > May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 > > May 30 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 > > Yes, I did note the broadcast address, my dhclient is pulling the same > broadcast addr (RoadRunner) and I have no problems. I believe this may > actually be an issue w/ a mis-configured dhcpd not dhclient. > > > May 31 02:38:07 blue su: sean to root on /dev/ttyp0 > > > > The previous dhcp client in 4.5 did not do this. It is only happening > > with the 4.6-RC. > > > > Cheers, > > Sean The default lease time has changed in the client. Does it on all my dhcp connected servers with -stable. Maybe adding a line like Cy Schubert suggested send requested-lease-time 172800 in dhclient.conf with unlimited lease might be a good idea or a commented out one explaining why. Nice to have options. -- Ted Sikora tsikora@unixos2.org http://unixos2.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 14:19:55 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 7314737B405 for ; Fri, 31 May 2002 14:19:50 -0700 (PDT) Received: from bmah.dyndns.org ([12.233.149.189]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020531211950.TMCU2751.rwcrmhc52.attbi.com@bmah.dyndns.org>; Fri, 31 May 2002 21:19:50 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.3/8.12.3) with ESMTP id g4VLJnfs008903; Fri, 31 May 2002 14:19:49 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.3/8.12.3/Submit) id g4VLJm7d008902; Fri, 31 May 2002 14:19:48 -0700 (PDT) Message-Id: <200205312119.g4VLJm7d008902@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20020506 with nmh-1.0.4 To: Matthias Andree Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.6-RELEASE delayed In-reply-to: References: <200205311652.g4VGq5YV004136@intruder.bmah.org> Comments: In-reply-to Matthias Andree message dated "Fri, 31 May 2002 22:31:19 +0200." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Fri, 31 May 2002 14:19:48 -0700 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by bmah.dyndns.org id g4VLJnfs008903 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If memory serves me right, Matthias Andree wrote: > It says ata(4) tags problems were related to motherboard-based ATA > channels. I see that S=F8ren's patch to fix the panic on boot that I > observed has now been merged into 4-STABLE, however, it seems as though > the "timeout and fall-back to PIO" issue is still unfixed in 4-STABLE. This is my understanding of the state of things too. (I haven't=20 experienced this personally...I'm mostly a SCSI person.) > My main board, a Gigabyte 7ZX-R rev. 1.0, offers four ATA channels. Two > are driven by the south bridge, VIA KT133 (VT82C686 stuff), the other > two are driven by a Promise PDC-20265R (in UDMA/100 mode). IIRC, this > Promise chip is in the "doesn't to tags, but freezes" blacklist. VIA > chips are not blacklisted, and AFAICS, tagged queueing not working on m= y > system is a regression over 4.5-RELEASE which had working tagged > queueing. "blacklist" isn't really the right word here (it implies some=20 deliberate malice). I get your point though, you have working tagged=20 queueing on 4.5 but not on 4.6. > S=F8ren said he was able to reproduce the timeout problem with tags, an= d > we should expect a fix "real soon now". This is the only list I follow, > but I haven't yet seen anything ata-related since. What's the release > engineering team's opinion on this ata issue? Will 4.6 be delayed until > the tagged stuff is fixed? Will 4.6 ship with ata tagged stuff disabled > altogether? Or will 4.6 ship with ata as it is today, with the risk tha= t > it breaks some systems 4.5 ata did work on? After much discussion between soren and murray, the conclusion was that soren probably won't be able to fix this in time for the release. (We offered to hold it a few days.) So unless something miraculous happens in the next few days, 4.6-RELEASE will ship with the ata(4) system as it sits today. Please note that: ATA tagged queueing is disabled by default (you need to enable it explicitly). There's also only a few drives (as I understand it) that even support this feature. I tried to capture this in the release notes for 4.6. Yes, it sucks if you happen to use this feature. The alternative (according to soren) is to back out the entire MFC of the ata(4) system, which means we'd lose support for new controllers, atacontrol(8), lots of ATA raid support, and other bugfixes and features I've lost track of. We thought this was a lose, so we're proceeding. Holding up the release indefinitely is not really an alternative. Our calendar from 2002 includes the following releases and snapshots: 4.5-RELEASE, 5.0-DP1, 4.6-RELEASE, 5.0-DP2, 4.7-RELEASE, 5.0-RELEASE. Put another way, the same people trying to get 4.6-RELEASE out the door now are going to try to bring the 5.0-DP2 snapshot to you twenty-six days from today. [1] Cheers, Bruce. [1] Down, not across. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 14:21:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.27in.tv (roc-24-169-198-248.rochester.rr.com [24.169.198.248]) by hub.freebsd.org (Postfix) with ESMTP id A89D637B40B for ; Fri, 31 May 2002 14:21:10 -0700 (PDT) Received: (from root@localhost) by mail.27in.tv (8.12.3/8.11.6) id g4VLLAiE035053; Fri, 31 May 2002 17:21:10 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from 27in.tv (localhost [127.0.0.1]) by mail.27in.tv (8.12.3/8.11.6av) with SMTP id g4VLL2TI035029; Fri, 31 May 2002 17:21:07 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from 216.153.201.118 (SquirrelMail authenticated user cjm2) by www.27in.tv with HTTP; Fri, 31 May 2002 17:21:08 -0400 (EDT) Message-ID: <2618.216.153.201.118.1022880068.squirrel@www.27in.tv> Date: Fri, 31 May 2002 17:21:08 -0400 (EDT) Subject: RE: new dhcp client causing problems From: "C J Michaels" To: In-Reply-To: <07f401c208e4$a7a8f9f0$0d00a8c0@celery> References: <2453.216.153.201.118.1022876310.squirrel@www.27in.tv> <07f401c208e4$a7a8f9f0$0d00a8c0@celery> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.3.0 [CVS-DEVEL]) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG tony said: > Since updating to 4.6R I seem to be having the same problem Same in that your connections are being reset? Because nothing looks bogus in your output either. Can you take a look in /var/db/dhclient.leases and see what "renew", "rebind", "expire", "option dhcp-lease-time" are set to for the most current lease. > > May 31 03:21:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 03:21:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 08:14:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 08:14:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 13:46:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 13:46:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > root:~# ifconfig -a > xl0: flags=8843 mtu 1500 > options=3 > inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:50:da:c2:a1:48 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > Here is a grep just for fun notice it gets a new addy every 5 minutes > most of the time > > root:~# grep dhclient /var/log/messages > May 27 01:02:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:02:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 [Was it necessary to paste the WHOLE log?] > > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of C J Michaels > Sent: Friday, May 31, 2002 4:19 PM > To: sean@mcneil.com > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: new dhcp client causing problems > > > Sean McNeil said: >> Hi, >> >> I've noticed that I occasionally lose connections through my computer >> to the internet. This has been happening because the dhcp client is >> trying to change my ip to something bogus and resetting the ethernet: > > Can you give an example of the 'bogus' ip address it's trying to set? > What you have listed below (without any additional information) appears > to be valid. (Note: no ip address is actually listed.) > >> >> May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 May 30 >> 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 > > Yes, I did note the broadcast address, my dhclient is pulling the same > broadcast addr (RoadRunner) and I have no problems. I believe this may > actually be an issue w/ a mis-configured dhcpd not dhclient. > >> May 31 02:38:07 blue su: sean to root on /dev/ttyp0 >> >> The previous dhcp client in 4.5 did not do this. It is only happening >> with the 4.6-RC. >> >> Cheers, >> Sean > > -- > Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 14:24: 4 2002 Delivered-To: freebsd-stable@freebsd.org Received: from bubba.NMSU.Edu (bubba.NMSU.Edu [128.123.3.39]) by hub.freebsd.org (Postfix) with ESMTP id 8620037B407 for ; Fri, 31 May 2002 14:23:59 -0700 (PDT) Received: from dns1.nmsu.edu (dns1.NMSU.Edu [128.123.3.5]) by bubba.NMSU.Edu (8.10.2+Sun/8.9.0) with ESMTP id g4VLNu407834 for ; Fri, 31 May 2002 15:23:57 -0600 (MDT) Received: from blackadder.nmsu.edu (blackadder.nmsu.edu [128.123.195.182]) by dns1.nmsu.edu (8.9.3/8.9.0) with ESMTP id PAA55310 for ; Fri, 31 May 2002 15:23:57 -0600 (MDT) Date: Fri, 31 May 2002 15:23:57 -0600 (MDT) From: "Byron L. Hicks" To: freebsd-stable@freebsd.org Subject: Announcements only mailing list? Message-ID: <20020531152231.V45424-100000@blackadder.nmsu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Is there an announcements-only mailing list I can subscribe to? I don't really need all the daily play by play, I just want to know when major releases happen, and why. Is there a list like that? -- Byron L. Hicks Network Engineer NMSU ICT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 14:28:48 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tntpro.com (dsl-207-5-188-75.gwi.net [207.5.188.75]) by hub.freebsd.org (Postfix) with ESMTP id 8D6D537B401 for ; Fri, 31 May 2002 14:27:55 -0700 (PDT) Received: from celery (celery.tntpro.com [192.168.0.13]) by tntpro.com (8.12.3/8.12.3) with ESMTP id g4VLQb31005363; Fri, 31 May 2002 17:26:37 -0400 (EDT) (envelope-from tony@tntpro.com) From: "tony" To: "'C J Michaels'" Cc: Subject: RE: new dhcp client causing problems Date: Fri, 31 May 2002 17:28:11 -0400 Message-ID: <07f501c208ea$11139260$0d00a8c0@celery> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <2618.216.153.201.118.1022880068.squirrel@www.27in.tv> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG lease { interface "xl0"; fixed-address 192.168.0.100; option subnet-mask 255.255.255.0; option routers 192.168.0.1; option dhcp-lease-time 43200; option dhcp-message-type 5; option domain-name-servers 192.168.0.1; option dhcp-server-identifier 192.168.0.1; option domain-name "tntpro.com"; renew 5 2002/5/31 23:21:04; rebind 6 2002/6/1 04:16:04; expire 6 2002/6/1 05:46:04; } -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of C J Michaels Sent: Friday, May 31, 2002 5:21 PM To: tony@tntpro.com Cc: freebsd-stable@FreeBSD.ORG Subject: RE: new dhcp client causing problems tony said: > Since updating to 4.6R I seem to be having the same problem Same in that your connections are being reset? Because nothing looks bogus in your output either. Can you take a look in /var/db/dhclient.leases and see what "renew", "rebind", "expire", "option dhcp-lease-time" are set to for the most current lease. > > May 31 03:21:42 tntpro dhclient: New Network Number: 192.168.0.0 May > 31 03:21:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 May > 31 08:14:03 tntpro dhclient: New Network Number: 192.168.0.0 May 31 > 08:14:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 May 31 > 13:46:04 tntpro dhclient: New Network Number: 192.168.0.0 May 31 > 13:46:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 root:~# > ifconfig -a > xl0: flags=8843 mtu 1500 > options=3 > inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:50:da:c2:a1:48 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > Here is a grep just for fun notice it gets a new addy every 5 minutes > most of the time > > root:~# grep dhclient /var/log/messages > May 27 01:02:12 tntpro dhclient: New Network Number: 192.168.0.0 May > 27 01:02:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 [Was it necessary to paste the WHOLE log?] > > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of C J Michaels > Sent: Friday, May 31, 2002 4:19 PM > To: sean@mcneil.com > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: new dhcp client causing problems > > > Sean McNeil said: >> Hi, >> >> I've noticed that I occasionally lose connections through my computer >> to the internet. This has been happening because the dhcp client is >> trying to change my ip to something bogus and resetting the ethernet: > > Can you give an example of the 'bogus' ip address it's trying to set? > What you have listed below (without any additional information) > appears to be valid. (Note: no ip address is actually listed.) > >> >> May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 May 30 >> 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 > > Yes, I did note the broadcast address, my dhclient is pulling the same > broadcast addr (RoadRunner) and I have no problems. I believe this > may actually be an issue w/ a mis-configured dhcpd not dhclient. > >> May 31 02:38:07 blue su: sean to root on /dev/ttyp0 >> >> The previous dhcp client in 4.5 did not do this. It is only >> happening with the 4.6-RC. >> >> Cheers, >> Sean > > -- > Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 14:31:42 2002 Delivered-To: freebsd-stable@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 916D137B401 for ; Fri, 31 May 2002 14:31:11 -0700 (PDT) Received: from odin.ac.hmc.edu (IDENT:brdavis@localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.12.3/8.12.3) with ESMTP id g4VLV8eE018381; Fri, 31 May 2002 14:31:08 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.12.3/8.12.3/Submit) id g4VLV8H1018380; Fri, 31 May 2002 14:31:08 -0700 Date: Fri, 31 May 2002 14:31:08 -0700 From: Brooks Davis To: "Byron L. Hicks" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Announcements only mailing list? Message-ID: <20020531143108.C14397@Odin.AC.HMC.Edu> References: <20020531152231.V45424-100000@blackadder.nmsu.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="ctP54qlpMx3WjD+/" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020531152231.V45424-100000@blackadder.nmsu.edu>; from bhicks@nmsu.edu on Fri, May 31, 2002 at 03:23:57PM -0600 X-Virus-Scanned: by amavisd-milter (http://amavis.org/) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --ctP54qlpMx3WjD+/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 31, 2002 at 03:23:57PM -0600, Byron L. Hicks wrote: > Is there an announcements-only mailing list I can subscribe to? I don't > really need all the daily play by play, I just want to know when major > releases happen, and why. Is there a list like that? That would be announce@freebsd.org. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --ctP54qlpMx3WjD+/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE89+ubXY6L6fI4GtQRAslUAJ9+C0KkBXBelzKlyS3XmgAmpIXuhwCdHNMl dMhWta+fgjDJBA7VTIh1maw= =+skK -----END PGP SIGNATURE----- --ctP54qlpMx3WjD+/-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 14:54:58 2002 Delivered-To: freebsd-stable@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 3BC0F37B403; Fri, 31 May 2002 14:54:51 -0700 (PDT) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.4.Beta0/8.12.4.Beta0) with ESMTP id g4VLsor7047689 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 31 May 2002 14:54:50 -0700 (PDT) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.4.Beta0/8.12.4.Beta0/Submit) id g4VLsoO2047686; Fri, 31 May 2002 14:54:50 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15607.61738.128410.326284@horsey.gshapiro.net> Date: Fri, 31 May 2002 14:54:50 -0700 From: Gregory Neil Shapiro To: "Louis A. Mamakos" Cc: freebsd-qa@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: dhclient-enter-hooks (was Re: 4.6-RELEASE delayed) In-Reply-To: References: <200205311652.g4VGq5YV004136@intruder.bmah.org> <200205311832.g4VIW8IY091328@whizzo.transsys.com> X-Mailer: VM 7.00 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >>>>> "ume" == Hajimu UMEMOTO writes: ume> Hi, >>>>> On Fri, 31 May 2002 14:32:08 -0400 >>>>> "Louis A. Mamakos" said: louie> You can't configure the "update /etc/resolv.conf" behavior, so I had louie> to manually edit the /sbin/dhclient-script to resolve this issue. ume> You can re-define make_resolv_conf() in /etc/dhclient-enter-hooks to ume> don't update /etc/resolv.conf. Please refer dhclient-script(8) ume> manpage. Here is what I use in mine in case it's useful. Personally, I think it should replace the default make_resolv_conf() in /sbin/dhclient-script as it is more intelligent -- it only replaces /etc/resolv.conf if something changes. make_resolv_conf() { # Don't replace /etc/resolv.conf unless something has changed if [ "$reason" != "RENEW" -o "$new_domain_name" != "$old_domain_name" -o \ "$new_domain_name_servers" != "$old_domain_name_servers" ] then echo search $new_domain_name >/etc/resolv.conf for nameserver in $new_domain_name_servers; do echo nameserver $nameserver >>/etc/resolv.conf done fi } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 15:25:24 2002 Delivered-To: freebsd-stable@freebsd.org Received: from blue.mcneil.com (cpe-66-75-176-109.socal.rr.com [66.75.176.109]) by hub.freebsd.org (Postfix) with ESMTP id 5E23437B404 for ; Fri, 31 May 2002 15:24:12 -0700 (PDT) Received: from mcneil.com (mcneil.com [66.75.176.109]) by blue.mcneil.com (8.12.3/8.12.3) with ESMTP id g4VMOAnR088439; Fri, 31 May 2002 15:24:14 -0700 (PDT) (envelope-from sean@mcneil.com) Subject: RE: new dhcp client causing problems From: Sean McNeil To: tony Cc: "'C J Michaels'" , freebsd-stable@FreeBSD.ORG In-Reply-To: <07f401c208e4$a7a8f9f0$0d00a8c0@celery> References: <07f401c208e4$a7a8f9f0$0d00a8c0@celery> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 31 May 2002 15:24:09 -0700 Message-Id: <1022883854.88347.15.camel@blue.mcneil.com> Mime-Version: 1.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I made an assumption that "New Network Number" is what is trying to be set as an IP. That is probably a wrong assumption. Further, there is only a loose correlation between my dropouts and these bogus messages. I call them bogus because they say "New" although they never change. Sean On Fri, 2002-05-31 at 13:49, tony wrote: > Since updating to 4.6R I seem to be having the same problem > > May 31 03:21:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 03:21:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 08:14:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 08:14:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 13:46:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 13:46:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > root:~# ifconfig -a > xl0: flags=8843 mtu 1500 > options=3 > inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255 > ether 00:50:da:c2:a1:48 > media: Ethernet autoselect (100baseTX ) > status: active > lo0: flags=8049 mtu 16384 > inet 127.0.0.1 netmask 0xff000000 > > Here is a grep just for fun notice it gets a new addy every 5 minutes > most of the time > > root:~# grep dhclient /var/log/messages > May 27 01:02:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:02:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:06:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:06:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:10:24 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:10:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:14:39 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:14:39 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:19:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:19:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:23:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:23:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:27:27 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:27:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:31:27 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:31:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:36:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:36:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:40:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:40:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:45:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:45:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:48:57 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:48:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:53:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:53:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 01:58:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 01:58:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:02:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:02:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:06:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:06:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:10:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:10:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:15:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:15:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:20:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:20:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:25:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:25:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:29:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:29:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:33:40 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:33:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:38:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:38:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:43:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:43:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:48:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:48:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:52:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:52:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 02:57:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 02:57:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:02:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:02:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:06:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:06:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:10:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:10:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:15:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:15:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:19:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:19:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:23:57 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:23:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:28:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:28:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:32:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:32:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:37:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:37:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:42:02 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:42:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:46:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:46:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:51:07 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:51:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:55:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:55:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 03:59:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 03:59:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:04:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:04:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:09:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:09:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:13:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:13:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:18:21 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:18:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:22:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:22:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:26:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:26:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:31:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:31:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:35:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:35:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:40:02 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:40:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:44:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:44:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:48:50 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:48:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:52:50 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:52:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 04:57:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 04:57:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:00:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:00:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:04:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:04:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:09:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:09:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:13:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:13:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:17:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:17:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:21:39 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:21:39 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:25:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:25:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:29:58 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:29:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:33:57 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:33:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:38:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:38:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:43:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:43:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:48:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:48:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:53:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:53:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 05:57:16 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 05:57:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:01:17 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:01:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:05:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:05:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:09:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:09:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:14:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:14:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:19:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:19:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:23:16 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:23:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:27:41 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:27:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:32:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:32:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:36:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:36:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:41:35 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:41:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:45:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:45:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:49:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:49:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:53:44 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:53:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 06:58:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 06:58:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:03:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:03:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:07:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:07:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:11:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:11:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:16:02 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:16:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:20:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:20:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:24:02 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:24:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:28:44 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:28:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:33:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:33:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:38:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:38:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:42:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:42:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:47:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:47:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:51:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:51:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 07:55:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 07:55:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:00:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:00:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:05:16 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:05:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:09:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:09:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:13:57 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:13:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:18:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:18:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:23:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:23:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:27:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:27:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:31:38 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:31:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:36:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:36:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:41:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:41:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:45:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:45:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:49:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:49:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:54:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:54:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 08:58:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 08:58:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:03:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:03:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:08:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:08:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:12:40 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:12:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:17:27 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:17:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:22:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:22:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:25:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:25:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:29:59 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:29:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:34:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:34:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:39:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:39:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:43:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:43:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:48:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:48:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:53:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:53:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 09:58:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 09:58:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:02:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:02:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:07:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:07:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:12:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:12:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:16:17 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:16:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:20:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:20:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:24:35 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:24:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:28:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:28:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:33:24 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:33:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:37:27 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:37:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:41:38 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:41:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:46:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:46:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:50:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:50:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:55:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:55:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 10:59:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 10:59:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:03:24 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:03:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:07:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:07:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:11:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:11:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:16:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:16:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:20:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:20:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:24:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:24:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:29:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:29:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:34:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:34:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:38:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:38:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:42:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:42:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:46:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:46:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:51:35 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:51:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 11:56:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 11:56:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:00:24 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:00:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:05:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:05:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:09:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:09:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:13:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:13:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:18:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:18:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:22:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:22:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:26:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:26:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:31:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:31:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:36:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:36:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:40:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:40:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:44:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:44:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:49:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:49:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:54:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:54:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 12:58:02 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 12:58:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:03:01 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:03:01 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:07:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:07:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:11:16 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:11:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:15:41 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:15:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:20:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:20:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:24:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:24:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:29:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:29:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:33:40 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:33:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:38:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:38:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:43:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:43:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:47:24 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:47:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:52:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:52:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 13:56:44 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 13:56:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:00:35 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:00:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:04:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:04:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:08:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:08:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:13:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:13:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:18:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:18:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:23:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:23:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:27:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:27:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:31:50 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:31:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:36:17 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:36:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:40:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:40:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:45:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:45:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:49:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:49:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:54:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:54:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 14:59:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 14:59:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:03:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:03:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:07:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:07:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:12:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:12:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:16:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:16:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:21:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:21:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:26:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:26:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:30:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:30:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:35:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:35:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:39:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:39:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:43:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:43:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:47:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:47:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:51:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:51:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:55:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:55:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 15:59:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 15:59:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:03:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:03:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:08:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:08:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:11:59 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:11:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:16:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:16:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:21:21 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:21:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:25:16 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:25:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:29:24 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:29:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:33:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:33:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:37:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:37:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:42:35 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:42:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:47:01 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:47:01 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:50:57 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:50:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:54:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:54:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 16:59:16 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 16:59:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:03:57 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:03:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:07:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:07:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:12:38 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:12:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:17:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:17:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:20:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:20:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:25:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:25:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:30:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:30:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:34:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:34:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:38:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:38:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:43:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:43:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:47:50 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:47:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:52:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:52:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 17:56:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 17:56:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:01:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:01:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:05:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:05:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:09:57 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:09:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:13:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:13:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:17:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:17:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:21:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:21:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:25:57 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:25:57 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:30:01 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:30:01 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:34:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:34:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:39:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:39:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:43:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:43:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:47:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:47:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:51:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:51:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 18:56:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 18:56:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:00:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:00:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:05:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:05:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:09:35 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:09:35 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:13:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:13:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:18:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:18:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:23:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:23:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:28:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:28:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:32:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:32:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:36:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:36:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:41:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:41:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:46:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:46:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:50:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:50:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:54:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:54:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 19:58:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 19:58:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:02:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:02:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:06:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:06:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:11:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:11:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:15:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:15:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:19:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:19:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:23:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:23:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:27:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:27:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:31:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:31:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:35:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:35:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:39:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:39:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:43:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:43:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:48:27 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:48:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:52:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:52:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 20:57:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 20:57:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:01:40 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:01:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:05:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:05:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:10:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:10:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:15:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:15:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:19:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:19:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:23:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:23:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:27:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:27:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:31:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:31:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:36:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:36:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:41:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:41:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:45:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:45:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:50:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:50:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:54:58 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:54:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 21:59:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 21:59:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:04:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:04:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:08:50 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:08:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:13:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:13:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:17:39 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:17:39 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:22:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:22:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:26:41 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:26:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:31:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:31:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:36:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:36:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:40:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:40:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:45:07 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:45:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:49:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:49:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:53:07 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:53:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 22:58:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 22:58:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:02:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:02:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:07:27 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:07:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:11:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:11:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:15:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:15:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:20:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:20:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:24:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:24:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:29:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:29:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:34:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:34:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:38:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:38:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:43:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:43:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:47:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:47:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:52:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:52:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 27 23:56:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 27 23:56:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:01:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:01:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:06:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:06:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:11:07 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:11:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:16:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:16:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:20:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:20:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:24:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:24:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:28:58 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:28:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:32:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:32:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:37:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:37:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:41:21 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:41:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:46:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:46:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:50:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:50:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:54:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:54:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 00:59:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 00:59:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:03:41 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:03:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:08:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:08:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:12:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:12:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:17:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:17:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:22:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:22:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:26:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:26:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:30:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:30:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:35:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:35:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:40:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:40:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:44:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:44:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:49:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:49:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:54:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:54:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 01:58:27 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 01:58:27 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:03:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:03:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:07:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:07:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:11:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:11:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:15:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:15:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:20:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:20:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:24:41 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:24:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:28:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:28:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:32:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:32:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:37:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:37:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:42:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:42:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:46:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:46:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:50:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:50:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:54:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:54:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 02:59:44 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 02:59:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:03:40 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:03:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:08:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:08:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:12:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:12:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:17:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:17:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:21:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:21:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:25:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:25:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:30:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:30:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:34:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:34:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:38:44 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:38:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:43:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:43:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:47:21 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:47:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:51:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:51:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 03:56:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 03:56:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:01:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:01:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:05:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:05:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:10:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:10:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:14:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:14:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:18:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:18:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:23:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:23:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:27:38 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:27:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:31:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:31:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:35:59 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:35:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:39:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:39:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:43:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:43:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:48:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:48:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:52:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:52:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 04:57:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 04:57:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:01:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:01:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:06:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:06:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:10:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:10:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:15:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:15:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:19:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:19:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:24:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:24:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:28:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:28:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:33:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:33:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:37:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:37:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:41:24 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:41:24 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:45:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:45:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:49:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:49:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:53:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:53:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 05:57:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 05:57:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:01:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:01:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:05:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:05:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:10:38 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:10:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:15:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:15:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:19:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:19:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:24:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:24:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:28:58 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:28:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:33:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:33:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:38:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:38:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:42:16 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:42:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:47:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:47:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:52:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:52:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 06:56:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 06:56:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:00:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:00:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:04:38 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:04:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:08:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:08:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:12:58 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:12:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:17:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:17:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:20:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:20:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:25:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:25:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:29:41 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:29:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:33:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:33:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:38:38 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:38:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:43:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:43:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:47:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:47:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:51:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:51:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:55:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:55:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 07:59:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 07:59:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:04:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:04:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:07:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:07:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:12:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:12:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:16:20 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:16:20 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:20:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:20:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:25:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:25:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:29:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:29:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:33:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:33:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:37:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:37:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:42:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:42:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:46:41 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:46:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:50:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:50:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:54:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:54:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 08:59:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 08:59:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:04:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:04:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:09:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:09:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:13:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:13:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:18:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:18:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:22:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:22:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:26:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:26:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:31:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:31:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:36:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:36:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:40:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:40:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:44:41 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:44:41 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:49:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:49:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:53:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:53:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 09:58:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 09:58:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:03:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:03:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:07:59 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:07:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:12:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:12:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:16:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:16:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:20:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:20:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:24:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:24:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:28:44 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:28:44 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:32:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:32:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:37:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:37:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:41:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:41:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:46:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:46:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:51:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:51:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:55:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:55:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 10:59:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 10:59:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:03:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:03:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:08:09 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:08:09 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:13:00 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:13:00 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:17:58 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:17:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:22:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:22:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:26:58 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:26:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:31:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:31:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:35:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:35:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:40:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:40:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:44:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:44:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:48:48 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:48:48 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:52:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:52:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 11:56:40 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 11:56:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:01:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:01:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:06:19 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:06:19 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:10:38 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:10:38 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:14:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:14:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:18:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:18:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:23:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:23:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:27:50 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:27:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:31:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:31:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:35:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:35:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:39:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:39:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:43:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:43:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:47:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:47:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:52:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:52:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 12:57:21 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 12:57:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:02:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:02:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:06:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:06:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:11:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:11:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:15:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:15:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:19:34 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:19:34 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:24:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:24:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:28:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:28:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:33:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:33:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:37:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:37:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:41:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:41:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:46:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:46:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:50:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:50:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:54:51 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:54:51 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 13:59:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 13:59:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:03:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:03:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:08:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:08:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:12:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:12:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:17:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:17:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:22:29 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:22:29 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:27:15 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:27:15 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:31:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:31:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:35:40 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:35:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:40:17 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:40:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:44:18 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:44:18 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:49:08 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:49:08 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:53:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:53:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 14:57:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 14:57:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:01:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:01:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:06:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:06:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:11:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:11:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:16:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:16:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:20:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:20:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:25:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:25:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:30:22 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:30:22 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:35:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:35:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:39:43 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:39:43 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:44:21 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:44:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:48:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:48:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:52:52 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:52:52 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 15:57:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 15:57:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:02:30 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:02:30 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:07:12 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:07:12 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:11:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:11:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:15:50 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:15:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:20:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:20:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:24:11 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:24:11 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:28:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:28:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:31:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:31:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:35:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:35:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:39:59 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:39:59 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:44:21 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:44:21 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:48:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:48:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:53:13 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:53:13 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 16:58:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 16:58:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:01:58 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:01:58 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:06:39 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:06:39 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:11:02 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:11:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:15:02 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:15:02 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:18:53 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:18:53 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:22:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:22:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:27:32 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:27:32 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:31:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:31:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:36:17 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:36:17 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:40:26 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:40:26 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:44:14 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:44:14 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:48:07 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:48:07 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:52:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:52:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 17:55:54 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 17:55:54 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:00:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:00:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:04:33 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:04:33 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:08:49 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:08:49 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:13:47 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:13:47 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:18:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:18:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:22:56 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:22:56 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:26:46 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:26:46 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:30:55 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:30:55 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:35:31 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:35:31 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:39:25 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:39:25 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:44:16 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:44:16 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:49:06 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:49:06 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 18:55:37 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 18:55:37 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 20:45:10 tntpro dhclient: New Network Number: 192.168.0.0 > May 28 20:45:10 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 28 20:45:10 tntpro dhclient: New IP Address (xl0): 192.168.0.100 > May 28 20:45:10 tntpro dhclient: New Subnet Mask (xl0): 255.255.255.0 > May 28 20:45:10 tntpro dhclient: New Broadcast Address (xl0): > 192.168.0.255 > May 28 20:45:10 tntpro dhclient: New Routers: 192.168.0.1 > May 29 01:47:45 tntpro dhclient: New Network Number: 192.168.0.0 > May 29 01:47:45 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 29 07:36:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 29 07:36:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 29 12:17:01 tntpro dhclient: New Network Number: 192.168.0.0 > May 29 12:17:01 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 29 16:52:50 tntpro dhclient: New Network Number: 192.168.0.0 > May 29 16:52:50 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 29 21:29:36 tntpro dhclient: New Network Number: 192.168.0.0 > May 29 21:29:36 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 30 02:23:28 tntpro dhclient: New Network Number: 192.168.0.0 > May 30 02:23:28 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 30 07:46:05 tntpro dhclient: New Network Number: 192.168.0.0 > May 30 07:46:05 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 30 12:51:40 tntpro dhclient: New Network Number: 192.168.0.0 > May 30 12:51:40 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 30 17:49:23 tntpro dhclient: New Network Number: 192.168.0.0 > May 30 17:49:23 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 03:21:42 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 03:21:42 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 08:14:03 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 08:14:03 tntpro dhclient: New Broadcast Address: 192.168.0.255 > May 31 13:46:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 13:46:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 > root:~# > > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of C J Michaels > Sent: Friday, May 31, 2002 4:19 PM > To: sean@mcneil.com > Cc: freebsd-stable@FreeBSD.ORG > Subject: Re: new dhcp client causing problems > > > Sean McNeil said: > > Hi, > > > > I've noticed that I occasionally lose connections through my computer > > to the internet. This has been happening because the dhcp client is > > trying to change my ip to something bogus and resetting the ethernet: > > Can you give an example of the 'bogus' ip address it's trying to set? > What you have listed below (without any additional information) appears > to be valid. (Note: no ip address is actually listed.) > > > > > May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 May 30 > > 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 > > Yes, I did note the broadcast address, my dhclient is pulling the same > broadcast addr (RoadRunner) and I have no problems. I believe this may > actually be an issue w/ a mis-configured dhcpd not dhclient. > > > May 31 02:38:07 blue su: sean to root on /dev/ttyp0 > > > > The previous dhcp client in 4.5 did not do this. It is only happening > > > with the 4.6-RC. > > > > Cheers, > > Sean > > -- > Chris > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 16:15:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 33CE537B401; Fri, 31 May 2002 16:15:04 -0700 (PDT) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id SAA22438; Fri, 31 May 2002 18:14:59 -0500 (CDT) (envelope-from jeff-ml@mountin.net) Received: from mke-65-29-139-162.wi.rr.com(65.29.139.162) by peak.mountin.net via smap (V1.3) id sma022436; Fri May 31 18:14:55 2002 Message-Id: <4.3.2.20020531180149.00d10e20@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Version 4.3 Date: Fri, 31 May 2002 18:15:41 -0500 To: bmah@FreeBSD.ORG, freebsd-qa@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: 4.6-RELEASE delayed Cc: re@FreeBSD.ORG In-Reply-To: <200205311652.g4VGq5YV004136@intruder.bmah.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 09:52 AM 5/31/02 -0700, Bruce A. Mah wrote: >Just a note to say that due to some late-breaking issues, 4.6 will be >released about a week later than originally planned. The magic date is >now 8 June 2002...I've just updated the release schedule on the Web >site. > >We'll be doing another release candidate (4.6-RC4...for various reasons >there won't be a 4.6-RC3) on Monday, in which we hope to see the major >remaining issues addressed. We encourage you to see the testing page >for this release at: Then why is there an RC3 on the main ftp site dated around midnight the 28/29th? 8-/ Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 16:34: 9 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by hub.freebsd.org (Postfix) with ESMTP id 3966F37B409; Fri, 31 May 2002 16:34:03 -0700 (PDT) Received: from bmah.dyndns.org ([12.233.149.189]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020531233402.GNBQ29266.sccrmhc01.attbi.com@bmah.dyndns.org>; Fri, 31 May 2002 23:34:02 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.3/8.12.3) with ESMTP id g4VNY1fs075657; Fri, 31 May 2002 16:34:01 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.3/8.12.3/Submit) id g4VNY1d1075643; Fri, 31 May 2002 16:34:01 -0700 (PDT) Message-Id: <200205312334.g4VNY1d1075643@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20020506 with nmh-1.0.4 To: "Jeffrey J. Mountin" Cc: bmah@FreeBSD.ORG, freebsd-qa@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, re@FreeBSD.ORG Subject: Re: 4.6-RELEASE delayed In-reply-to: <4.3.2.20020531180149.00d10e20@207.227.119.2> References: <4.3.2.20020531180149.00d10e20@207.227.119.2> Comments: In-reply-to "Jeffrey J. Mountin" message dated "Fri, 31 May 2002 18:15:41 -0500." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 May 2002 16:34:01 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If memory serves me right, "Jeffrey J. Mountin" wrote: > >We'll be doing another release candidate (4.6-RC4...for various reasons > >there won't be a 4.6-RC3) on Monday, in which we hope to see the major > >remaining issues addressed. We encourage you to see the testing page > >for this release at: > > Then why is there an RC3 on the main ftp site dated around midnight the > 28/29th? 8-/ It got overtaken by other events (including some still-open issues), so murray decided not to bother actually announcing it. These aren't the bits you're looking for. :-) Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 18:14:26 2002 Delivered-To: freebsd-stable@freebsd.org Received: from alicia.nttmcl.com (alicia.nttmcl.com [216.69.69.10]) by hub.freebsd.org (Postfix) with ESMTP id 7410137B404 for ; Fri, 31 May 2002 18:14:23 -0700 (PDT) Received: (from jj@localhost) by alicia.nttmcl.com (8.10.1/8.10.1) id g511Dvq10594; Fri, 31 May 2002 18:13:57 -0700 (PDT) Date: Fri, 31 May 2002 18:13:56 -0700 From: JJ Behrens To: Sean McNeil , "'C J Michaels'" , freebsd-stable@FreeBSD.ORG Subject: Re: new dhcp client causing problems Message-ID: <20020531181356.A2621@alicia.nttmcl.com> Mail-Followup-To: JJ Behrens , Sean McNeil , 'C J Michaels' , freebsd-stable@FreeBSD.ORG References: <07f401c208e4$a7a8f9f0$0d00a8c0@celery> <1022883854.88347.15.camel@blue.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <1022883854.88347.15.camel@blue.mcneil.com>; from sean@mcneil.com on Fri, May 31, 2002 at 03:24:09PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I made an assumption that "New Network Number" is what is trying to be > set as an IP. That is probably a wrong assumption. Further, there is > only a loose correlation between my dropouts and these bogus messages. > I call them bogus because they say "New" although they never change. I may be completely wrong (I must confess, I don't even use DHCP), but I thought the network number was: network_number = ip & netmask; -jj -- Users of C++ should consider hanging themselves rather than shooting their legs off--it's best not to use C++ simply as a better C. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 18:19:35 2002 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 990DA37B406 for ; Fri, 31 May 2002 18:19:27 -0700 (PDT) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id SAA01436; Fri, 31 May 2002 18:19:25 -0700 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda01434; Fri May 31 18:19:18 2002 Received: from cwsys.cwsent.com (cwsys2 [10.1.2.1]) by passer.osg.gov.bc.ca (8.12.3/8.12.3) with ESMTP id g511JCEb013214; Fri, 31 May 2002 18:19:12 -0700 (PDT) (envelope-from cy@cwsent.com) Received: from cwsys (localhost [127.0.0.1]) by cwsys.cwsent.com (8.12.3/8.12.3) with ESMTP id g511JCr1059003; Fri, 31 May 2002 18:19:12 -0700 (PDT) (envelope-from cy@cwsys.cwsent.com) Message-Id: <200206010119.g511JCr1059003@cwsys.cwsent.com> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 Reply-To: Cy Schubert - CITS Open Systems Group From: Cy Schubert - CITS Open Systems Group X-os: FreeBSD X-Sender: cy@cwsent.com To: Ted Sikora Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: new dhcp client causing problems In-Reply-To: Message from Ted Sikora of "Fri, 31 May 2002 17:16:38 EDT." <3CF7E836.742CD559@ntplx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 31 May 2002 18:19:12 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <3CF7E836.742CD559@ntplx.net>, Ted Sikora writes: > C J Michaels wrote: > > > > Sean McNeil said: > > > Hi, > > > > > > I've noticed that I occasionally lose connections through my computer to > > > the internet. This has been happening because the dhcp client is trying > > > to change my ip to something bogus and resetting the ethernet: > > > > Can you give an example of the 'bogus' ip address it's trying to set? > > What you have listed below (without any additional information) appears to > > be valid. (Note: no ip address is actually listed.) > > > > > > > > May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 > > > May 30 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 > > > > Yes, I did note the broadcast address, my dhclient is pulling the same > > broadcast addr (RoadRunner) and I have no problems. I believe this may > > actually be an issue w/ a mis-configured dhcpd not dhclient. > > > > > May 31 02:38:07 blue su: sean to root on /dev/ttyp0 > > > > > > The previous dhcp client in 4.5 did not do this. It is only happening > > > with the 4.6-RC. > > > > > > Cheers, > > > Sean > > The default lease time has changed in the client. Does it on all my dhcp > connected servers with -stable. Maybe adding a line like Cy Schubert > suggested > > send requested-lease-time 172800 > > in dhclient.conf with unlimited lease might be a good idea or a > commented out one explaining why. Nice to have options. The client doesn't have a default lease time. That's determined by the server or more specifically the server's admin person. You might be able to request a longer lease time in your dhclient.conf, however since this is a policy decision made by your service provider, you'll probably have to talk to a person to request a longer lease time. Following is a copy of my current lease from dhclient.leases: lease { interface "dc0"; fixed-address x.x.x.x; option subnet-mask 255.255.252.0; option routers x.x.x.1; option dhcp-lease-time 172800; option dhcp-message-type 5; option domain-name-servers x.x.x.x,y.y.y.y; option dhcp-server-identifier x.x.x.x; option dhcp-renewal-time 86400; option dhcp-rebinding-time 151200; option host-name "hxx-xx-xx-xx"; option domain-name "xx.xxxx.net"; renew 6 2002/6/1 06:50:28; rebind 0 2002/6/2 03:09:34; expire 0 2002/6/2 09:09:34; } I have not requested a lease time of 2 days, but that's what my cable company has given me by default. From time to time they will reduce the lease time to 1 hour. This will last for a day or two, maybe a week, when they do any work on their infrastructure. Usually I can expect outages for a short time following this. My dhclient.conf is pretty basic. It looks like this: timeout 60; reboot 10; retry 60; select-timeout 5; initial-interval 2; interface "dc0" { #this next line is required for @home, a pseudo authentication #it should be something like cx111111-a send host-name "blah-x"; request subnet-mask, broadcast-address, routers, domain-name-servers, domain-name, time-servers; require domain-name-servers; script "/usr/local/etc/dhclient-script"; } IMO, I think that people are wasting their time by looking for DHCP problems within FreeBSD or fiddling with parameters that more than likely their service provider will not allow them to request or change. More than likely the problem is with your service providers DHCP policy and the configuration that stems from their policy. The DHCP support in FreeBSD has been extremely solid for the years I've been connected to the cable company. What more can I say? Just like the Energizer rabbit, it just keeps on working. -- Cheers, Phone: 250-387-8437 Cy Schubert Fax: 250-387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, CITS Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 20: 3:12 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mcp.csh.rit.edu (mcp.csh.rit.edu [129.21.60.9]) by hub.freebsd.org (Postfix) with ESMTP id 4445437B408 for ; Fri, 31 May 2002 20:03:07 -0700 (PDT) Received: from fury.csh.rit.edu (fury.csh.rit.edu [129.21.60.5]) by mcp.csh.rit.edu (Postfix) with ESMTP id DCB7925A for ; Fri, 31 May 2002 23:03:01 -0400 (EDT) Date: Fri, 31 May 2002 23:03:01 -0400 (EDT) From: Nicholas Johnson To: Subject: subscribe Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri May 31 20:57:41 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tntpro.com (dsl-207-5-188-75.gwi.net [207.5.188.75]) by hub.freebsd.org (Postfix) with ESMTP id A154E37B400 for ; Fri, 31 May 2002 20:57:29 -0700 (PDT) Received: from celery (celery.tntpro.com [192.168.0.13]) by tntpro.com (8.12.3/8.12.3) with ESMTP id g513u831006321; Fri, 31 May 2002 23:56:08 -0400 (EDT) (envelope-from tony@tntpro.com) From: "tony" To: "'Cy Schubert - CITS Open Systems Group'" , "'Ted Sikora'" Cc: Subject: RE: new dhcp client causing problems Date: Fri, 31 May 2002 23:57:45 -0400 Message-ID: <07fe01c20920$7cf3ef80$0d00a8c0@celery> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <200206010119.g511JCr1059003@cwsys.cwsent.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm just wondering why my /var/log/messages is filling with May 31 19:21:04 tntpro dhclient: New Network Number: 192.168.0.0 May 31 19:21:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of Cy Schubert - CITS Open Systems Group Sent: Friday, May 31, 2002 9:19 PM To: Ted Sikora Cc: freebsd-stable@FreeBSD.ORG Subject: Re: new dhcp client causing problems In message <3CF7E836.742CD559@ntplx.net>, Ted Sikora writes: > C J Michaels wrote: > > > > Sean McNeil said: > > > Hi, > > > > > > I've noticed that I occasionally lose connections through my > > > computer to the internet. This has been happening because the > > > dhcp client is trying to change my ip to something bogus and > > > resetting the ethernet: > > > > Can you give an example of the 'bogus' ip address it's trying to > > set? What you have listed below (without any additional information) > > appears to be valid. (Note: no ip address is actually listed.) > > > > > > > > May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 May > > > 30 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 > > > > Yes, I did note the broadcast address, my dhclient is pulling the > > same broadcast addr (RoadRunner) and I have no problems. I believe > > this may actually be an issue w/ a mis-configured dhcpd not > > dhclient. > > > > > May 31 02:38:07 blue su: sean to root on /dev/ttyp0 > > > > > > The previous dhcp client in 4.5 did not do this. It is only > > > happening with the 4.6-RC. > > > > > > Cheers, > > > Sean > > The default lease time has changed in the client. Does it on all my > dhcp connected servers with -stable. Maybe adding a line like Cy Schubert > suggested > > send requested-lease-time 172800 > > in dhclient.conf with unlimited lease might be a good idea or a > commented out one explaining why. Nice to have options. The client doesn't have a default lease time. That's determined by the server or more specifically the server's admin person. You might be able to request a longer lease time in your dhclient.conf, however since this is a policy decision made by your service provider, you'll probably have to talk to a person to request a longer lease time. Following is a copy of my current lease from dhclient.leases: lease { interface "dc0"; fixed-address x.x.x.x; option subnet-mask 255.255.252.0; option routers x.x.x.1; option dhcp-lease-time 172800; option dhcp-message-type 5; option domain-name-servers x.x.x.x,y.y.y.y; option dhcp-server-identifier x.x.x.x; option dhcp-renewal-time 86400; option dhcp-rebinding-time 151200; option host-name "hxx-xx-xx-xx"; option domain-name "xx.xxxx.net"; renew 6 2002/6/1 06:50:28; rebind 0 2002/6/2 03:09:34; expire 0 2002/6/2 09:09:34; } I have not requested a lease time of 2 days, but that's what my cable company has given me by default. From time to time they will reduce the lease time to 1 hour. This will last for a day or two, maybe a week, when they do any work on their infrastructure. Usually I can expect outages for a short time following this. My dhclient.conf is pretty basic. It looks like this: timeout 60; reboot 10; retry 60; select-timeout 5; initial-interval 2; interface "dc0" { #this next line is required for @home, a pseudo authentication #it should be something like cx111111-a send host-name "blah-x"; request subnet-mask, broadcast-address, routers, domain-name-servers, domain-name, time-servers; require domain-name-servers; script "/usr/local/etc/dhclient-script"; } IMO, I think that people are wasting their time by looking for DHCP problems within FreeBSD or fiddling with parameters that more than likely their service provider will not allow them to request or change. More than likely the problem is with your service providers DHCP policy and the configuration that stems from their policy. The DHCP support in FreeBSD has been extremely solid for the years I've been connected to the cable company. What more can I say? Just like the Energizer rabbit, it just keeps on working. -- Cheers, Phone: 250-387-8437 Cy Schubert Fax: 250-387-5766 Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca Open Systems Group, CITS Ministry of Management Services Province of BC FreeBSD UNIX: cy@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 4:33:29 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id 1E60437B408 for ; Sat, 1 Jun 2002 04:33:26 -0700 (PDT) Received: from merlin.emma.line.org (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 7CF77A3831 for ; Sat, 1 Jun 2002 13:33:24 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 7926430228; Sat, 1 Jun 2002 13:33:21 +0200 (CEST) Date: Sat, 1 Jun 2002 13:33:21 +0200 From: Matthias Andree To: freebsd-stable@FreeBSD.ORG Subject: Re: 4.6-RELEASE delayed Message-ID: <20020601113321.GC15739@merlin.emma.line.org> References: <200205311652.g4VGq5YV004136@intruder.bmah.org> <200205312119.g4VLJm7d008902@intruder.bmah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200205312119.g4VLJm7d008902@intruder.bmah.org> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 31 May 2002, Bruce A. Mah wrote: > > My main board, a Gigabyte 7ZX-R rev. 1.0, offers four ATA channels. Two > > are driven by the south bridge, VIA KT133 (VT82C686 stuff), the other > > two are driven by a Promise PDC-20265R (in UDMA/100 mode). IIRC, this > > Promise chip is in the "doesn't to tags, but freezes" blacklist. VIA > > chips are not blacklisted, and AFAICS, tagged queueing not working on my > > system is a regression over 4.5-RELEASE which had working tagged > > queueing. > > "blacklist" isn't really the right word here (it implies some > deliberate malice). I get your point though, you have working tagged > queueing on 4.5 but not on 4.6. I wasn't aware of a "negative" or "malicious" connotation of "black list", I just saw it as a list that said "do not dare tagged queueing on these chips". > After much discussion between soren and murray, the conclusion was that > soren probably won't be able to fix this in time for the release. (We > offered to hold it a few days.) So unless something miraculous happens > in the next few days, 4.6-RELEASE will ship with the ata(4) system as it > sits today. OK. > Please note that: ATA tagged queueing is disabled by default (you need > to enable it explicitly). There's also only a few drives (as I > understand it) that even support this feature. I tried to capture this > in the release notes for 4.6. Yes, it sucks if you happen to use this > feature. In 4.5, tagged queueing was tried on IBM DPTA*, DTLA* and IC35L* drives (see this as shell pattern). Some more drives offer tagged queueing, for example, some Western Digital like my AC420400D, but FreeBSD won't work with them (I tried putting my drive on the list of "good" drives for tagged queueing, but it didn't work out.) It seems as though this drive had a working implementation from what the Linux IDE folk say, but I must yet test this under load before I can claim "it will work". > The alternative (according to soren) is to back out the entire MFC of > the ata(4) system, which means we'd lose support for new controllers, > atacontrol(8), lots of ATA raid support, and other bugfixes and features > I've lost track of. We thought this was a lose, so we're proceeding. Ok. > Holding up the release indefinitely is not really an alternative. Our > calendar from 2002 includes the following releases and snapshots: > 4.5-RELEASE, 5.0-DP1, 4.6-RELEASE, 5.0-DP2, 4.7-RELEASE, 5.0-RELEASE. > Put another way, the same people trying to get 4.6-RELEASE out the door > now are going to try to bring the 5.0-DP2 snapshot to you twenty-six > days from today. [1] Yup. I'm just wondering if a bugfix would be committed to 4.6-STABLE (that usually should only receive security fixes). -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 7:43:46 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sccrmhc01.attbi.com (sccrmhc01.attbi.com [204.127.202.61]) by hub.freebsd.org (Postfix) with ESMTP id 5A2BB37B416 for ; Sat, 1 Jun 2002 07:43:29 -0700 (PDT) Received: from bmah.dyndns.org ([12.233.149.189]) by sccrmhc01.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020601144328.UMCA29266.sccrmhc01.attbi.com@bmah.dyndns.org>; Sat, 1 Jun 2002 14:43:28 +0000 Received: from intruder.bmah.org (localhost [IPv6:::1]) by bmah.dyndns.org (8.12.3/8.12.3) with ESMTP id g51EhRfs027659; Sat, 1 Jun 2002 07:43:27 -0700 (PDT) (envelope-from bmah@intruder.bmah.org) Received: (from bmah@localhost) by intruder.bmah.org (8.12.3/8.12.3/Submit) id g51EhRb1027658; Sat, 1 Jun 2002 07:43:27 -0700 (PDT) Message-Id: <200206011443.g51EhRb1027658@intruder.bmah.org> X-Mailer: exmh version 2.5+ 20020506 with nmh-1.0.4 To: Matthias Andree Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 4.6-RELEASE delayed In-reply-to: <20020601113321.GC15739@merlin.emma.line.org> References: <200205311652.g4VGq5YV004136@intruder.bmah.org> <200205312119.g4VLJm7d008902@intruder.bmah.org> <20020601113321.GC15739@merlin.emma.line.org> Comments: In-reply-to Matthias Andree message dated "Sat, 01 Jun 2002 13:33:21 +0200." From: "Bruce A. Mah" Reply-To: bmah@FreeBSD.ORG X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Image-Url: http://www.employees.org/~bmah/Images/bmah-cisco-small.gif X-Url: http://www.employees.org/~bmah/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Jun 2002 07:43:27 -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG If memory serves me right, Matthias Andree wrote: > > Holding up the release indefinitely is not really an alternative. Our > > calendar from 2002 includes the following releases and snapshots: > > 4.5-RELEASE, 5.0-DP1, 4.6-RELEASE, 5.0-DP2, 4.7-RELEASE, 5.0-RELEASE. > > Put another way, the same people trying to get 4.6-RELEASE out the door > > now are going to try to bring the 5.0-DP2 snapshot to you twenty-six > > days from today. [1] > > Yup. I'm just wondering if a bugfix would be committed to 4.6-STABLE > (that usually should only receive security fixes). I think you may be a little confused here. The 4-STABLE development branch (with the CVS tag RELENG_4) will take on various names during its lifetime, including 4.6-STABLE, 4.7-PRERELEASE, and 4.7-RC. It will eventually be the basis of 4.7. It will definitely get the bugfix, once one is created. The 4.6 release/security branch (with the CVS tag RELENG_4_6) will have version numbers of the form 4.6-RELEASE, 4.6-RELEASE-p1, 4.6-RELEASE-p2, and so forth. It normally only gets security fixes and critical system bugfixes. I think it's *way* too early to be thinking about applying an ATA tagged queueing bugfix to this branch, since the bugfix in question doesn't even exist yet. (Neither does the branch, for that matter.) Hope this helps, Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 8:20: 6 2002 Delivered-To: freebsd-stable@freebsd.org Received: from 12-222-67-235.client.insightBB.com (12-222-67-235.client.insightBB.com [12.222.67.235]) by hub.freebsd.org (Postfix) with ESMTP id 3A26337B406 for ; Sat, 1 Jun 2002 08:20:01 -0700 (PDT) Received: from 12-222-67-235.client.insightBB.com (localhost.client.insightBB.com [127.0.0.1]) by 12-222-67-235.client.insightBB.com (8.12.3/8.12.3) with ESMTP id g51FJpgd061742; Sat, 1 Jun 2002 10:19:52 -0500 (EST) (envelope-from mikes@12-222-67-235.client.insightBB.com) Received: (from mikes@localhost) by 12-222-67-235.client.insightBB.com (8.12.3/8.12.3/Submit) id g51FJl8W061741; Sat, 1 Jun 2002 10:19:47 -0500 (EST) (envelope-from mikes) From: Mike Squires Message-Id: <200206011519.g51FJl8W061741@12-222-67-235.client.insightBB.com> Subject: Re: new dhcp client causing problems In-Reply-To: <07fe01c20920$7cf3ef80$0d00a8c0@celery> "from tony at May 31, 2002 11:57:45 pm" To: tony Date: Sat, 1 Jun 2002 10:19:47 -0500 (EST) Cc: FreeBSD Stable X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG tony > I'm just wondering why my /var/log/messages is filling with > May 31 19:21:04 tntpro dhclient: New Network Number: 192.168.0.0 > May 31 19:21:04 tntpro dhclient: New Broadcast Address: 192.168.0.255 The same messages started appearing in my logs after upgrading to 4.6-PRE: May 31 10:19:20 99-992-67-235 dhclient: DHCPREQUEST on fxp0 to 99.993.2.34 port 67 May 31 10:19:20 99-992-67-235 dhclient: DHCPACK from 99.993.2.34 May 31 10:19:20 99-992-67-235 dhclient: New Network Number: 99.992.64.0 May 31 10:19:20 99-992-67-235 dhclient: New Broadcast Address: 255.255.255.255 May 31 10:19:20 99-992-67-235 dhclient: bound to 99.992.67.235 -- renewal in 155695 seconds. which I interpret as bogus responses from the DHCP server (the reponses for hostname and netmask are definitely bogus, although these may be just a crude attempt by the ISP to prevent client systems from running services.) They appear every few days. Mike Squires UN*X at home since 1985 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 8:41:19 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by hub.freebsd.org (Postfix) with ESMTP id C9C9E37B403 for ; Sat, 1 Jun 2002 08:41:15 -0700 (PDT) Received: from merlin.emma.line.org (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 9860BA3831 for ; Sat, 1 Jun 2002 17:41:14 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id D694634190; Sat, 1 Jun 2002 17:41:11 +0200 (CEST) Date: Sat, 1 Jun 2002 17:41:11 +0200 From: Matthias Andree To: freebsd-stable@FreeBSD.ORG Subject: Re: 4.6-RELEASE delayed Message-ID: <20020601154111.GB7019@merlin.emma.line.org> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <200205311652.g4VGq5YV004136@intruder.bmah.org> <200205312119.g4VLJm7d008902@intruder.bmah.org> <20020601113321.GC15739@merlin.emma.line.org> <200206011443.g51EhRb1027658@intruder.bmah.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200206011443.g51EhRb1027658@intruder.bmah.org> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 01 Jun 2002, Bruce A. Mah wrote: > > Yup. I'm just wondering if a bugfix would be committed to 4.6-STABLE > > (that usually should only receive security fixes). > > I think you may be a little confused here. > > The 4-STABLE development branch (with the CVS tag RELENG_4) will take on > various names during its lifetime, including 4.6-STABLE, 4.7-PRERELEASE, > and 4.7-RC. It will eventually be the basis of 4.7. It will definitely > get the bugfix, once one is created. Please apologize for not naming it 4.6-RELEASE (which is what I meant, but did not write). > The 4.6 release/security branch (with the CVS tag RELENG_4_6) will have > version numbers of the form 4.6-RELEASE, 4.6-RELEASE-p1, 4.6-RELEASE-p2, > and so forth. It normally only gets security fixes and critical system > bugfixes. I think it's *way* too early to be thinking about applying an > ATA tagged queueing bugfix to this branch, since the bugfix in question > doesn't even exist yet. (Neither does the branch, for that matter.) Indeed, "security fixes and critical system bugfixes" is the key word I was asking for. So it's possible, if the bugfix is isolated and directed enough that it might get in. Let's hope for the best for the ATA stuff. -- Matthias Andree To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 9:13:49 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.27in.tv (roc-24-169-198-248.rochester.rr.com [24.169.198.248]) by hub.freebsd.org (Postfix) with ESMTP id B5C6637B408 for ; Sat, 1 Jun 2002 09:13:43 -0700 (PDT) Received: (from root@localhost) by mail.27in.tv (8.12.3/8.11.6) id g51GDg9x053590; Sat, 1 Jun 2002 12:13:42 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from maxpower (maxpower.lan.27in.tv [10.0.0.20]) by mail.27in.tv (8.12.3/8.11.6av) with SMTP id g51GDaTI053576; Sat, 1 Jun 2002 12:13:37 -0400 (EDT) (envelope-from cjm2@earthling.net) From: "C J Michaels" To: "Sean McNeil" Cc: "tony" , , Subject: RE: new dhcp client causing problems Date: Sat, 1 Jun 2002 12:13:52 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <1022883675.88347.8.camel@blue.mcneil.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG No, it would say New IP Address if it were giving you a new IP address. As JJ mentioned in another e-mail. The network address is a function of and'ing your IP and Subnet Mask. Even if your actual IP address changed every 5 minutes, I wouldn't expect your Network Address to change very often, unless you were moved to a different subnet. I looked at my /var/log/messages and it is logging the 'new network number' message every 3-5hrs. (Mind you I'm not having any dropout problems) If you look through your /var/db/dhclient.leases, the 'New Network Number' messages should correspond with the 'renew' timestamps. I believe the only real 'issue' here is that dhclient should be silently renewing the lease (since nothing changes), but is (for some reason) displaying these messages. I was looking through /sbin/dhclient-script but it's going to take some time for _me_ to figured it out. Maybe someone else on the list with a bit more experience can help. (As for why Tony's are renewing every 5 minutes, even tho his lease renewal times are hrs apart, I haven't figured out yet. Tony, is your /etc/resolv.conf writable by the dhclient process?) --Chris > -----Original Message----- > From: Sean McNeil [mailto:sean@mcneil.com] > Sent: Friday, May 31, 2002 6:21 PM > To: C J Michaels > Subject: Re: new dhcp client causing problems > > > I'm sorry, maybe I'm misreading. It actually says New Network Number. > Isn't this what the dhcp is saying is an IP for me? These messages are > actually bogus in that they are always the same and never change. So > They aren't really "New" :) > > I had assumed that some of my dropouts are with respect to these > messages. They have some correlation, but it isn't verified. > > Sean > > On Fri, 2002-05-31 at 13:18, C J Michaels wrote: > > Sean McNeil said: > > > Hi, > > > > > > I've noticed that I occasionally lose connections through my > computer to > > > the internet. This has been happening because the dhcp > client is trying > > > to change my ip to something bogus and resetting the ethernet: > > > > Can you give an example of the 'bogus' ip address it's trying to set? > > What you have listed below (without any additional information) > appears to > > be valid. (Note: no ip address is actually listed.) > > > > > > > > May 30 23:44:17 blue dhclient: New Network Number: 66.75.176.0 > > > May 30 23:44:17 blue dhclient: New Broadcast Address: 255.255.255.255 > > > > Yes, I did note the broadcast address, my dhclient is pulling the same > > broadcast addr (RoadRunner) and I have no problems. I believe this may > > actually be an issue w/ a mis-configured dhcpd not dhclient. > > > > > May 31 02:38:07 blue su: sean to root on /dev/ttyp0 > > > > > > The previous dhcp client in 4.5 did not do this. It is only happening > > > with the 4.6-RC. > > > > > > Cheers, > > > Sean > > > > -- > > Chris > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 9:23:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.27in.tv (roc-24-169-198-248.rochester.rr.com [24.169.198.248]) by hub.freebsd.org (Postfix) with ESMTP id AD27437B408 for ; Sat, 1 Jun 2002 09:23:45 -0700 (PDT) Received: (from root@localhost) by mail.27in.tv (8.12.3/8.11.6) id g51GNjhM053722; Sat, 1 Jun 2002 12:23:45 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from maxpower (cjm2@maxpower.lan.27in.tv [10.0.0.20]) by mail.27in.tv (8.12.3/8.11.6av) with SMTP id g51GNgTI053701; Sat, 1 Jun 2002 12:23:43 -0400 (EDT) (envelope-from cjm2@earthling.net) From: "C J Michaels" To: "Cy Schubert - CITS Open Systems Group" Cc: Subject: RE: new dhcp client causing problems Date: Sat, 1 Jun 2002 12:23:59 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <200206010119.g511JCr1059003@cwsys.cwsent.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Cy Schubert - CITS > Open Systems Group > Sent: Friday, May 31, 2002 9:19 PM <<...snip...>> > > > IMO, I think that people are wasting their time by looking for DHCP > problems within FreeBSD or fiddling with parameters that more than > likely their service provider will not allow them to request or change. > More than likely the problem is with your service providers DHCP > policy and the configuration that stems from their policy. The DHCP > support in FreeBSD has been extremely solid for the years I've been > connected to the cable company. What more can I say? Just like the > Energizer rabbit, it just keeps on working. That opinion, of course, is your perrogative. I do agree that the high frequency of renewals in tony's case is probably due to some (mis)configuration on the dhcpd side. Although, why dhclient should now log this useless information is beyond me. I consider it to be a minor bug. BUT, I don't agree with saying that just because a component of FreeBSD has worked in the past, means it should always work. Esp a component that has been MFC'd reciently. An MFC that has produced at least one legitimate bug thus far. Ok, I'm done. Thanks for putting up with me. :) > > > -- > Cheers, Phone: 250-387-8437 > Cy Schubert Fax: 250-387-5766 > Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca > Open Systems Group, CITS > Ministry of Management Services > Province of BC > FreeBSD UNIX: cy@FreeBSD.org --Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 9:23:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.27in.tv (roc-24-169-198-248.rochester.rr.com [24.169.198.248]) by hub.freebsd.org (Postfix) with ESMTP id 00B2C37B409 for ; Sat, 1 Jun 2002 09:23:46 -0700 (PDT) Received: (from root@localhost) by mail.27in.tv (8.12.3/8.11.6) id g51GNjSb053726; Sat, 1 Jun 2002 12:23:45 -0400 (EDT) (envelope-from cjm2@earthling.net) Received: from maxpower (cjm2@maxpower.lan.27in.tv [10.0.0.20]) by mail.27in.tv (8.12.3/8.11.6av) with SMTP id g51GNgTK053701; Sat, 1 Jun 2002 12:23:43 -0400 (EDT) (envelope-from cjm2@earthling.net) From: "C J Michaels" To: Cc: Subject: RE: dhclient on ro filesystems [Was: 4.6-RELEASE delayed] Date: Sat, 1 Jun 2002 12:23:59 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <2432.216.153.201.118.1022875377.squirrel@www.27in.tv> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG bin/38778 > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of C J Michaels > Sent: Friday, May 31, 2002 4:03 PM > To: ume@mahoroba.org > Cc: louie@transsys.com; freebsd-stable@FreeBSD.ORG > Subject: dhclient on ro filesystems [Was: 4.6-RELEASE delayed] > > > Hajimu UMEMOTO said: > > Hi, > > > >>>>>> On Fri, 31 May 2002 14:32:08 -0400 > >>>>>> "Louis A. Mamakos" said: > > > > louie> You can't configure the "update /etc/resolv.conf" behavior, so I > > had louie> to manually edit the /sbin/dhclient-script to resolve this > > issue. > > I ran the exact same problem about a week ago. In retro-spect I should > have put in a PR (sorry about that). I'll try and put one together this > weekend if there isn't already one. (Did you submit one Louie?) > > > > > You can re-define make_resolv_conf() in /etc/dhclient-enter-hooks to > > don't update /etc/resolv.conf. Please refer dhclient-script(8) > > manpage. > > While this would be a short-term fix. This problem should be treated as a > bug. If /etc/resolv.conf isn't writable, dhclient should print an error > and exit (previous behavior). Not get stuck in an infinite loop, > requesting a new lease every ~5 seconds. > > > > > Sincerely, > > > > -- > > Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan > > ume@mahoroba.org ume@bisd.hitachi.co.jp ume@{,jp.}FreeBSD.org > > http://www.imasy.org/~ume/ > > > -- > Chris > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 13:35:34 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id E5A3C37B404 for ; Sat, 1 Jun 2002 13:35:27 -0700 (PDT) Received: (qmail 3855 invoked by uid 0); 1 Jun 2002 20:35:19 -0000 Received: from acb236cf.ipt.aol.com (HELO bowman.gmx.net) (172.178.54.207) by mail.gmx.net (mp001-rz3) with SMTP; 1 Jun 2002 20:35:19 -0000 Message-Id: <5.1.0.14.0.20020601223424.00a13090@pop.gmx.net> X-Sender: 12223972@pop.gmx.net X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 01 Jun 2002 22:35:09 +0200 To: freebsd-stable@FreeBSD.ORG From: Daniel Geske Subject: Re: auth 650a995d unsubscribe freebsd-stable danielgeske@gmx.net In-Reply-To: <001001c208c5$109142d0$0801a8c0@arnold> References: <5.1.0.14.0.20020531155904.00a07cd0@pop.gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Uh! Sorry. ;-) At 07:03 PM 5/31/02 +0200, you wrote: >You might want to sent this to majordomo instead of to the list itself. >:-) > >----- Original Message ----- >From: "Daniel Geske" >To: >Sent: Friday, May 31, 2002 3:59 PM >Subject: auth 650a995d unsubscribe freebsd-stable danielgeske@gmx.net > > > > auth 650a995d unsubscribe freebsd-stable danielgeske@gmx.net > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 17: 6: 2 2002 Delivered-To: freebsd-stable@freebsd.org Received: from lota.izhcom.ru (lota.izhcom.ru [213.24.0.2]) by hub.freebsd.org (Postfix) with ESMTP id C504737B407; Sat, 1 Jun 2002 17:05:24 -0700 (PDT) Received: from jhynt (D052.dialup.udm.net [213.59.63.52]) by lota.izhcom.ru (8.11.6/8.11.6/Izhcom-V1.1m) with SMTP id g5204Wf57562; Sun, 2 Jun 2002 05:04:33 +0500 (SAMST) Message-Id: <200206020004.g5204Wf57562@lota.izhcom.ru> From: infocom To: "" <> Subject: Èíôîðìàöèÿ Organization: infocom Reply-To: mail@infobase.com.ru X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-Priority: 3 X-MSMail-Priority: Normal Mime-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Date: Sun, 2 Jun 2002 05:04:34 +0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Áàçû äàííûõ ôèðì è e-mail http://infobase.com.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 19:57:53 2002 Delivered-To: freebsd-stable@freebsd.org Received: from tntpro.com (dsl-207-5-188-75.gwi.net [207.5.188.75]) by hub.freebsd.org (Postfix) with ESMTP id DF3AB37B400 for ; Sat, 1 Jun 2002 19:57:44 -0700 (PDT) Received: from celery (celery.tntpro.com [192.168.0.13]) by tntpro.com (8.12.3/8.12.3) with ESMTP id g522uP31012917; Sat, 1 Jun 2002 22:56:25 -0400 (EDT) (envelope-from tony@tntpro.com) From: "tony" To: "'C J Michaels'" , "'Cy Schubert - CITS Open Systems Group'" Cc: Subject: RE: new dhcp client causing problems Date: Sat, 1 Jun 2002 22:58:14 -0400 Message-ID: <082001c209e1$56c6dcc0$0d00a8c0@celery> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This box is behind my freebsd 4.3 firewall running isc-dhcp-2.0.3 Here is my dhpcd.conf on my firewall (192.168.0.1) if there is some misconfiguratino maybe we can find it here? root:/usr/local/etc# more dhcpd.conf subnet 192.168.0.0 netmask 255.255.255.0 { range 192.168.0.200 192.168.0.210; option domain-name "tntpro.com"; option domain-name-servers 192.168.0.1; option routers 192.168.0.1; } host tony { hardware ethernet 00:60:b0:eb:21:dc; fixed-address 192.168.0.10; } host metal { hardware ethernet 00:a0:cc:52:21:41; fixed-address 192.168.0.11; } host lunar { hardware ethernet 00:50:da:c2:a1:78; fixed-address 192.168.0.100; } host celery { hardware ethernet 00:a0:cc:66:5f:ce; fixed-address 192.168.0.13; } root:/usr/local/etc# -----Original Message----- From: owner-freebsd-stable@FreeBSD.ORG [mailto:owner-freebsd-stable@FreeBSD.ORG] On Behalf Of C J Michaels Sent: Saturday, June 01, 2002 12:24 PM To: Cy Schubert - CITS Open Systems Group Cc: freebsd-stable@FreeBSD.ORG Subject: RE: new dhcp client causing problems > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Cy Schubert - > CITS Open Systems Group > Sent: Friday, May 31, 2002 9:19 PM <<...snip...>> > > > IMO, I think that people are wasting their time by looking for DHCP > problems within FreeBSD or fiddling with parameters that more than > likely their service provider will not allow them to request or > change. More than likely the problem is with your service providers > DHCP policy and the configuration that stems from their policy. The > DHCP support in FreeBSD has been extremely solid for the years I've > been connected to the cable company. What more can I say? Just like > the Energizer rabbit, it just keeps on working. That opinion, of course, is your perrogative. I do agree that the high frequency of renewals in tony's case is probably due to some (mis)configuration on the dhcpd side. Although, why dhclient should now log this useless information is beyond me. I consider it to be a minor bug. BUT, I don't agree with saying that just because a component of FreeBSD has worked in the past, means it should always work. Esp a component that has been MFC'd reciently. An MFC that has produced at least one legitimate bug thus far. Ok, I'm done. Thanks for putting up with me. :) > > > -- > Cheers, Phone: 250-387-8437 > Cy Schubert Fax: 250-387-5766 > Team Leader, Sun/Alpha Team Email: Cy.Schubert@osg.gov.bc.ca > Open Systems Group, CITS > Ministry of Management Services > Province of BC > FreeBSD UNIX: cy@FreeBSD.org --Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Jun 1 20:37:34 2002 Delivered-To: freebsd-stable@freebsd.org Received: from iguana.simplexity.net (adsl-216-103-84-145.dsl.snfc21.pacbell.net [216.103.84.145]) by hub.freebsd.org (Postfix) with ESMTP id D654B37B407 for ; Sat, 1 Jun 2002 20:37:21 -0700 (PDT) Received: from localhost (localhost.skymind.com [127.0.0.1]) by iguana.simplexity.net (8.12.3/8.11.1) with ESMTP id g523bLvi079628 for ; Sat, 1 Jun 2002 20:37:21 -0700 (PDT) (envelope-from ocrow@simplexity.net) Date: Sat, 1 Jun 2002 20:37:21 -0700 (PDT) From: Oliver Crow To: freebsd-stable@freebsd.org Subject: Clockwork 24 hour crash in 4.5-RELEASE-p5 Message-ID: <20020601195808.F79494-100000@iguana.simplexity.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have a FreeBSD 4.5-p5 system that's crashing reliably every 24 hours +/- a few minutes. It's been doing this ever since I compiled a 4.5-p4 kernel on March 25th. I cvsup'd to 4.5-p5 and recompiled, but it's still crashing. It was initially showing nmbd as the current process at the time of crash. I disabled samba, thinking that it might be the culprit. It continued to crash, now showing the crash process as named. In both cases the kernel crashed whilst processing an ioctl (according to the crash dump). My problem seems somewhat similar to this one: http://spitfire.velocet.net/pipermail/freebsd-stable/2002-March/027982.html Has anyone else seen this? Any theories? Or fixes?! Here's the details: # gdb -k /var/crash/kernel.4 /var/crash/vmcore.4 ... IdlePTD at phsyical address 0x0049c000 initial pcb at physical address 0x003e11e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x13f5fde fault code = supervisor read, page not present instruction pointer = 0x8:0xc01fee8f stack pointer = 0x10:0xcdda1d9c frame pointer = 0x10:0xcdda1e24 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 70 (named) interrupt mask = none trap number = 12 panic: page fault syncing disks... done Uptime: 1d0h0m7s ... (kgdb) where #0 0xc01bbd36 in dumpsys () #1 0xc01bbb4b in boot () #2 0xc01bbf2c in poweroff_wait () #3 0xc0334382 in trap_fatal () #4 0xc0334055 in trap_pfault () #5 0xc0333c13 in trap () #6 0xc01fee8f in ifconf () #7 0xc01fe6b1 in ifioctl () #8 0xc01cdc0e in soo_ioctl () #9 0xc01cac92 in ioctl () #10 0xc0334631 in syscall2 () #11 0xc0325955 in Xint0x80_syscall () #12 0x8077234 in ?? () #13 0x8086e09 in ?? () #14 0x805fc7b in ?? () #15 0x804b3c1 in ?? () # last -f /var/log/wtmp.1 reboot reboot ~ Tue Apr 30 20:17 reboot ~ Mon Apr 29 20:17 reboot ~ Sun Apr 28 20:19 reboot ~ Sat Apr 27 20:19 reboot ~ Fri Apr 26 20:19 reboot ~ Fri Apr 26 19:49 reboot ~ Tue Apr 16 11:10 reboot ~ Tue Apr 16 11:03 reboot ~ Mon Apr 15 18:33 reboot ~ Sun Apr 14 18:37 reboot ~ Sat Apr 13 18:41 reboot ~ Fri Apr 12 18:45 reboot ~ Thu Apr 11 18:48 reboot ~ Thu Apr 11 18:00 reboot ~ Tue Apr 9 19:50 reboot ~ Mon Apr 8 19:54 reboot ~ Sun Apr 7 19:58 reboot ~ Sat Apr 6 19:00 reboot ~ Fri Apr 5 18:58 reboot ~ Thu Apr 4 18:58 reboot ~ Wed Apr 3 19:02 reboot ~ Tue Apr 2 19:00 reboot ~ Mon Apr 1 19:00 ## kernel options (diff vs GENERIC) maxusers 128 makeoptions DEBUG=-g device apm0 at nexus? flags 0x20 pseudo-device gif 4 # IPv6 and IPv4 tunneling ## dmesg FreeBSD 4.5-RELEASE-p5 #6: Mon May 27 23:37:35 PDT 2002 ocrow@gecko.in.simplexity.net:/usr/src/sys/compile/CURRENT Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (664.51-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 267124736 (260864K bytes) avail memory = 255328256 (249344K bytes) Preloaded elf kernel "kernel" at 0xc047d000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 10 entries at 0xc00f3230 apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 1.0 irq 11 pcib1: at device 30.0 on pci0 pci1: on pcib1 fxp0: port 0xde80-0xdebf mem 0xff700000-0xff7 fffff,0xff8fe000-0xff8fefff irq 9 at device 1.0 on pci1 fxp0: Ethernet address 00:d0:b7:ac:46:c1 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pci1: (vendor=0x1274, dev=0x1371) at 7.0 irq 10 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xef80-0xef9f irq 9 at device 31.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: (vendor=0x8086, dev=0x2413) at 31.3 irq 0 orm0: