From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 00:34:28 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9439316A41F for ; Sun, 21 Aug 2005 00:34:28 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe04.swip.net [212.247.154.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08A9643D46 for ; Sun, 21 Aug 2005 00:34:27 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-204-116.daxnet.no ([193.217.204.116] verified) by mailfe04.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 445139323 for freebsd-hackers@freebsd.org; Sun, 21 Aug 2005 02:34:25 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Sun, 21 Aug 2005 02:35:16 +0200 User-Agent: KMail/1.7 References: <200508200359.j7K3xoHF015718@ambrisko.com> <200508201230.37976.hselasky@c2i.net> <20050820.171238.122195775.imp@bsdimp.com> In-Reply-To: <20050820.171238.122195775.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508210235.17608.hselasky@c2i.net> Subject: Re: Parking disk drive heads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 00:34:28 -0000 On Sunday 21 August 2005 01:12, M. Warner Losh wrote: > In message: <200508201230.37976.hselasky@c2i.net> > > Hans Petter Selasky writes: > : On Saturday 20 August 2005 10:18, Mike Silbersack wrote: > : > On Fri, 19 Aug 2005, Doug Ambrisko wrote: > : > > Flash is nice but it has some issues. Atleast dropping it isn't one! > : > > > : > > Doug A. > : > > : > I'd be really happy if I could get a USB flash drive to last more than > : > 8 months. Luckily, I started weekly backups after the first failure. > : > That helped a lot when the second failure happened. > : > : Flash drives does usually not last more than 10000 writes, per bit, from > : what I know. Probably you need some kind of special file-system that > : moves the files around as the write quoute gets used up! Eventually the > : size of the disk will reach zero, and you have to move the files > : elsewhere :-) But this is probably off topic. > > Actually, 10,000 writes per bit is one or two orders of magnitude too > low these days. It was more typical for the Linear Flash PCMCIA cards > from 10 years ago. Today, typically flash devices are good for more > like 100,000 or 500,000 writes per cell, and all the fobs you'd buy > these days have built-in wear averaging. I've tried three times now > to wear out a flash by writing an incrementing counter to a single > location only to give up after weeks of hammering due to external > factors (power failure, network failure, etc). Are you sure that the flash drive is not caching the writes in RAM? --HPS From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 00:37:36 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E36E716A41F for ; Sun, 21 Aug 2005 00:37:36 +0000 (GMT) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 633E243D45 for ; Sun, 21 Aug 2005 00:37:36 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: Y1QAsIk9O44SO+J/q9KNyQ== Received: from mp-217-204-116.daxnet.no ([193.217.204.116] verified) by mailfe06.swip.net (CommuniGate Pro SMTP 4.3.4) with ESMTP id 435416966 for freebsd-hackers@freebsd.org; Sun, 21 Aug 2005 02:37:34 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Sun, 21 Aug 2005 02:38:30 +0200 User-Agent: KMail/1.7 References: <200508201638.43821.hselasky@c2i.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508210238.32067.hselasky@c2i.net> Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hselasky@c2i.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 00:37:37 -0000 On Saturday 20 August 2005 17:29, Mike Adewole wrote: > > I am just wondering, but will you be using QT 4.0 for this project? > > > > I might be interrested, though I am very comfortable with blackbox, it > > might > > > be nice with some icons, as long as it doesn't take forever to start. > > > > --HPS > > We'll be reimplementing TurboVision (C++) for the project so we can release > under a BSD compatible license. It's almost done and it looks quite nice > with overlapping windows and drag n drop. Maybe I misunderstood you, but will this be running under X or in some text terminal? --HPS From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 02:44:23 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CFA416A41F for ; Sun, 21 Aug 2005 02:44:23 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B56743D46 for ; Sun, 21 Aug 2005 02:44:22 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.23] (andersonbox3.centtech.com [192.168.42.23]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j7L2i1Z2000961; Sat, 20 Aug 2005 21:44:01 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4307EA82.7040108@centtech.com> Date: Sat, 20 Aug 2005 21:44:18 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.10) Gecko/20050815 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200508200359.j7K3xoHF015718@ambrisko.com> <20050820031508.A73274@odysseus.silby.com> <200508201230.37976.hselasky@c2i.net> <20050820.171238.122195775.imp@bsdimp.com> In-Reply-To: <20050820.171238.122195775.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1034/Thu Aug 18 15:07:58 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, hselasky@c2i.net Subject: Re: Parking disk drive heads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 02:44:23 -0000 M. Warner Losh wrote: > In message: <200508201230.37976.hselasky@c2i.net> > Hans Petter Selasky writes: > : On Saturday 20 August 2005 10:18, Mike Silbersack wrote: > : > On Fri, 19 Aug 2005, Doug Ambrisko wrote: > : > > Flash is nice but it has some issues. Atleast dropping it isn't one! > : > > > : > > Doug A. > : > > : > I'd be really happy if I could get a USB flash drive to last more than 8 > : > months. Luckily, I started weekly backups after the first failure. That > : > helped a lot when the second failure happened. > : > > : > : Flash drives does usually not last more than 10000 writes, per bit, from what > : I know. Probably you need some kind of special file-system that moves the > : files around as the write quoute gets used up! Eventually the size of the > : disk will reach zero, and you have to move the files elsewhere :-) But this > : is probably off topic. > > Actually, 10,000 writes per bit is one or two orders of magnitude too > low these days. It was more typical for the Linear Flash PCMCIA cards > from 10 years ago. Today, typically flash devices are good for more > like 100,000 or 500,000 writes per cell, and all the fobs you'd buy > these days have built-in wear averaging. I've tried three times now > to wear out a flash by writing an incrementing counter to a single > location only to give up after weeks of hammering due to external > factors (power failure, network failure, etc). As a data point, I've been using 64mb compact flash cards (rated at 100k writes) in about 100 Soekris boxes (running FreeBSD) for about 4 years, and they are all still working, except for one. Now, most compact flash cards are rated at 1 million writes. And yes, I'm logging to the card and everything.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 04:00:53 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F15B16A420 for ; Sun, 21 Aug 2005 04:00:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BAE643D48 for ; Sun, 21 Aug 2005 04:00:52 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j7L3lQuO026864; Sat, 20 Aug 2005 21:47:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 20 Aug 2005 21:47:30 -0600 (MDT) Message-Id: <20050820.214730.56826446.imp@bsdimp.com> To: anderson@centtech.com From: "M. Warner Losh" In-Reply-To: <4307EA82.7040108@centtech.com> References: <200508201230.37976.hselasky@c2i.net> <20050820.171238.122195775.imp@bsdimp.com> <4307EA82.7040108@centtech.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.village.org [127.0.0.1]); Sat, 20 Aug 2005 21:47:31 -0600 (MDT) Cc: freebsd-hackers@freebsd.org, hselasky@c2i.net Subject: Re: Parking disk drive heads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 04:00:53 -0000 In message: <4307EA82.7040108@centtech.com> Eric Anderson writes: : M. Warner Losh wrote: : > In message: <200508201230.37976.hselasky@c2i.net> : > Hans Petter Selasky writes: : > : On Saturday 20 August 2005 10:18, Mike Silbersack wrote: : > : > On Fri, 19 Aug 2005, Doug Ambrisko wrote: : > : > > Flash is nice but it has some issues. Atleast dropping it isn't one! : > : > > : > : > > Doug A. : > : > : > : > I'd be really happy if I could get a USB flash drive to last more than 8 : > : > months. Luckily, I started weekly backups after the first failure. That : > : > helped a lot when the second failure happened. : > : > : > : : > : Flash drives does usually not last more than 10000 writes, per bit, from what : > : I know. Probably you need some kind of special file-system that moves the : > : files around as the write quoute gets used up! Eventually the size of the : > : disk will reach zero, and you have to move the files elsewhere :-) But this : > : is probably off topic. : > : > Actually, 10,000 writes per bit is one or two orders of magnitude too : > low these days. It was more typical for the Linear Flash PCMCIA cards : > from 10 years ago. Today, typically flash devices are good for more : > like 100,000 or 500,000 writes per cell, and all the fobs you'd buy : > these days have built-in wear averaging. I've tried three times now : > to wear out a flash by writing an incrementing counter to a single : > location only to give up after weeks of hammering due to external : > factors (power failure, network failure, etc). : : As a data point, I've been using 64mb compact flash cards (rated at 100k : writes) in about 100 Soekris boxes (running FreeBSD) for about 4 years, : and they are all still working, except for one. Now, most compact flash : cards are rated at 1 million writes. : : And yes, I'm logging to the card and everything.. The biggest failure mode of CF cards that we've seen in our boxes is static zapage. We get more CF cards back that didn't fsck due to a power failure, etc than we do worn out cards, or even static zapped ones. The static zapping usually happens when we're popping the old one out and a new one in... We think we may have seen one power surge related failure, but we're unsure. We've fielded about 1000 CF cards over the past 6 years... Warner From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 04:30:47 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A48FD16A420 for ; Sun, 21 Aug 2005 04:30:47 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 263AA43D46 for ; Sun, 21 Aug 2005 04:30:46 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.23] (andersonbox3.centtech.com [192.168.42.23]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j7L4Ucw2079760; Sat, 20 Aug 2005 23:30:38 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4308037F.3000906@centtech.com> Date: Sat, 20 Aug 2005 23:30:55 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.10) Gecko/20050815 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200508201230.37976.hselasky@c2i.net> <20050820.171238.122195775.imp@bsdimp.com> <4307EA82.7040108@centtech.com> <20050820.214730.56826446.imp@bsdimp.com> In-Reply-To: <20050820.214730.56826446.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, hselasky@c2i.net Subject: Re: Parking disk drive heads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 04:30:47 -0000 M. Warner Losh wrote: > In message: <4307EA82.7040108@centtech.com> > Eric Anderson writes: > : M. Warner Losh wrote: > : > In message: <200508201230.37976.hselasky@c2i.net> > : > Hans Petter Selasky writes: > : > : On Saturday 20 August 2005 10:18, Mike Silbersack wrote: > : > : > On Fri, 19 Aug 2005, Doug Ambrisko wrote: > : > : > > Flash is nice but it has some issues. Atleast dropping it isn't one! > : > : > > > : > : > > Doug A. > : > : > > : > : > I'd be really happy if I could get a USB flash drive to last more than 8 > : > : > months. Luckily, I started weekly backups after the first failure. That > : > : > helped a lot when the second failure happened. > : > : > > : > : > : > : Flash drives does usually not last more than 10000 writes, per bit, from what > : > : I know. Probably you need some kind of special file-system that moves the > : > : files around as the write quoute gets used up! Eventually the size of the > : > : disk will reach zero, and you have to move the files elsewhere :-) But this > : > : is probably off topic. > : > > : > Actually, 10,000 writes per bit is one or two orders of magnitude too > : > low these days. It was more typical for the Linear Flash PCMCIA cards > : > from 10 years ago. Today, typically flash devices are good for more > : > like 100,000 or 500,000 writes per cell, and all the fobs you'd buy > : > these days have built-in wear averaging. I've tried three times now > : > to wear out a flash by writing an incrementing counter to a single > : > location only to give up after weeks of hammering due to external > : > factors (power failure, network failure, etc). > : > : As a data point, I've been using 64mb compact flash cards (rated at 100k > : writes) in about 100 Soekris boxes (running FreeBSD) for about 4 years, > : and they are all still working, except for one. Now, most compact flash > : cards are rated at 1 million writes. > : > : And yes, I'm logging to the card and everything.. > > The biggest failure mode of CF cards that we've seen in our boxes is > static zapage. We get more CF cards back that didn't fsck due to a > power failure, etc than we do worn out cards, or even static zapped > ones. The static zapping usually happens when we're popping the old > one out and a new one in... We think we may have seen one power surge > related failure, but we're unsure. We've fielded about 1000 CF cards > over the past 6 years... Cool, great info - thanks. If I may, what are these cards doing? (anything cool?) - or at least, what company are you working for that uses this many for some purpose? (simply curiousity) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 04:45:18 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CB5116A420 for ; Sun, 21 Aug 2005 04:45:18 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC5D043D48 for ; Sun, 21 Aug 2005 04:45:17 +0000 (GMT) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id j7L4ihEg028916; Sat, 20 Aug 2005 21:44:47 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200508210444.j7L4ihEg028916@gw.catspoiler.org> Date: Sat, 20 Aug 2005 21:44:43 -0700 (PDT) From: Don Lewis To: anderson@centtech.com In-Reply-To: <4307EA82.7040108@centtech.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-hackers@FreeBSD.org, hselasky@c2i.net Subject: Re: Parking disk drive heads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 04:45:18 -0000 On 20 Aug, Eric Anderson wrote: > As a data point, I've been using 64mb compact flash cards (rated at 100k > writes) in about 100 Soekris boxes (running FreeBSD) for about 4 years, > and they are all still working, except for one. Now, most compact flash > cards are rated at 1 million writes. > > And yes, I'm logging to the card and everything.. I've been using a laptop drive in my firewall and mail relay box for noise and power consumption reasons. The drive specs only give an expected lifetime of a few years when running 24x7, and I just had to replace a drive that had been in service about four years. I've given some thought to using flash, but I'm concerned about the number of writes, especially since a mail relay (maybe 1K messages/day) is going to be somewhat write intensive. What would be nice is a flash-backed md device that would flush its contents to flash on power fail. From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 04:53:36 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EEC7016A41F; Sun, 21 Aug 2005 04:53:36 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EE6B43D48; Sun, 21 Aug 2005 04:53:36 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.23] (andersonbox3.centtech.com [192.168.42.23]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j7L4rYns080124; Sat, 20 Aug 2005 23:53:34 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <430808DF.1000405@centtech.com> Date: Sat, 20 Aug 2005 23:53:51 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.10) Gecko/20050815 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Don Lewis References: <200508210444.j7L4ihEg028916@gw.catspoiler.org> In-Reply-To: <200508210444.j7L4ihEg028916@gw.catspoiler.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, hselasky@c2i.net Subject: Re: Parking disk drive heads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 04:53:37 -0000 Don Lewis wrote: > On 20 Aug, Eric Anderson wrote: > > >>As a data point, I've been using 64mb compact flash cards (rated at 100k >>writes) in about 100 Soekris boxes (running FreeBSD) for about 4 years, >>and they are all still working, except for one. Now, most compact flash >>cards are rated at 1 million writes. >> >>And yes, I'm logging to the card and everything.. > > > I've been using a laptop drive in my firewall and mail relay box for > noise and power consumption reasons. The drive specs only give an > expected lifetime of a few years when running 24x7, and I just had to > replace a drive that had been in service about four years. I've given > some thought to using flash, but I'm concerned about the number of > writes, especially since a mail relay (maybe 1K messages/day) is going > to be somewhat write intensive. What would be nice is a flash-backed md > device that would flush its contents to flash on power fail. If you are running 6.0 or 7.0-CURRENT, you should check out gjournal recently released from a SoC project. It can do some of this. Maybe another possible solution would be a memory backed md device unioned over a flash device? Anyhow, a cheap solution would be 2 flash devices mirrored with gmirror. By the time it burns up, you'll be able to swap it with the same size for half the price, and if you put them on different IDE channels or use usb, you can do it live. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 06:36:58 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C662D16A41F for ; Sun, 21 Aug 2005 06:36:58 +0000 (GMT) (envelope-from adewole@sympatico.ca) Received: from BAYC1-PASMTP02.bayc1.hotmail.com (bayc1-pasmtp02.bayc1.hotmail.com [65.54.191.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 865C643D45 for ; Sun, 21 Aug 2005 06:36:58 +0000 (GMT) (envelope-from adewole@sympatico.ca) Message-ID: X-Originating-IP: [64.231.252.56] X-Originating-Email: [adewole@sympatico.ca] Received: from newton ([64.231.252.56]) by BAYC1-PASMTP02.bayc1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Sat, 20 Aug 2005 23:36:57 -0700 Message-ID: <004801c5a61b$dab3ee40$6501a8c0@newton> From: "Mike Adewole" To: "Tom Norris" References: <43078D2C.4020000@trancegeek.net> Date: Sun, 21 Aug 2005 02:44:59 -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.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-OriginalArrivalTime: 21 Aug 2005 06:36:57.0668 (UTC) FILETIME=[BA683840:01C5A61A] Cc: freebsd-hackers@freebsd.org Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 06:36:58 -0000 From: "Tom Norris" To: "Mike Adewole" Sent: Saturday, August 20, 2005 4:06 PM Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop > > So if you love the BSD console and would like to see it sport a complete > > desktop environment, the bsdvision project can really use your support. And > > since this project developed from an attempt to do a cleanroom > > implementation of libh, we'll be using the old libh mailing list until we > > have another one. Come help us make *BSD a truly complete platform with the > > best console desktop environment in the universe :-) > > I would be willing to test that out and I might be able to help with > code. (School starting again, and I have a feeling there's going to be a > LOT of work coming from my physics classes) > > > - Tom > Hey Tom, thanks a lot for volunteering ! I've added you to the list of people willing to help with testing and will contact you as soon as we have enough people to get going. Thanks again. Cheers From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 06:51:40 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF3B316A41F for ; Sun, 21 Aug 2005 06:51:40 +0000 (GMT) (envelope-from adewole@sympatico.ca) Received: from BAYC1-PASMTP03.bayc1.hotmail.com (bayc1-pasmtp03.bayc1.hotmail.com [65.54.191.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 69DB643D45 for ; Sun, 21 Aug 2005 06:51:40 +0000 (GMT) (envelope-from adewole@sympatico.ca) Message-ID: X-Originating-IP: [64.231.252.56] X-Originating-Email: [adewole@sympatico.ca] Received: from newton ([64.231.252.56]) by BAYC1-PASMTP03.bayc1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Sat, 20 Aug 2005 23:51:39 -0700 Message-ID: <007401c5a61d$e8a75530$6501a8c0@newton> From: "Mike Adewole" To: , References: <200508201638.43821.hselasky@c2i.net> <200508210238.32067.hselasky@c2i.net> Date: Sun, 21 Aug 2005 02:59:42 -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.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-OriginalArrivalTime: 21 Aug 2005 06:51:40.0028 (UTC) FILETIME=[C855ABC0:01C5A61C] Cc: Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 06:51:40 -0000 From: "Hans Petter Selasky" To: Sent: Saturday, August 20, 2005 8:38 PM Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop > On Saturday 20 August 2005 17:29, Mike Adewole wrote: > > > I am just wondering, but will you be using QT 4.0 for this project? > > > > > > I might be interrested, though I am very comfortable with blackbox, it > > > > might > > > > > be nice with some icons, as long as it doesn't take forever to start. > > > > > > --HPS > > > > We'll be reimplementing TurboVision (C++) for the project so we can release > > under a BSD compatible license. It's almost done and it looks quite nice > > with overlapping windows and drag n drop. > > Maybe I misunderstood you, but will this be running under X or in some text > terminal? > > --HPS > It will be running on a virtual console in text or graphics mode like TurboVision used to, but we are focusing on text mode for now. As I just wrote to someone else, the main idea is to enable BSD programs to have a nice console (textual and graphical) interface with and without any windows system. So I could have a standalone program that looks like an X program for example but runs on a virtual console without X. Or I could have the program run in a desktop environment with other programs without changing a single line of code or recompiling the program. Cheers From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 06:58:42 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BDA816A41F for ; Sun, 21 Aug 2005 06:58:42 +0000 (GMT) (envelope-from adewole@sympatico.ca) Received: from BAYC1-PASMTP03.bayc1.hotmail.com (bayc1-pasmtp03.bayc1.hotmail.com [65.54.191.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 387CB43D45 for ; Sun, 21 Aug 2005 06:58:42 +0000 (GMT) (envelope-from adewole@sympatico.ca) Message-ID: X-Originating-IP: [64.231.252.56] X-Originating-Email: [adewole@sympatico.ca] Received: from newton ([64.231.252.56]) by BAYC1-PASMTP03.bayc1.hotmail.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Sat, 20 Aug 2005 23:58:10 -0700 Message-ID: <009801c5a61e$d1a63e90$6501a8c0@newton> From: "Mike Adewole" To: "Julian H. Stacey" References: <200508201203.j7KC3s2g005892@fire.jhs.private> Date: Sun, 21 Aug 2005 03:06:13 -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.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-OriginalArrivalTime: 21 Aug 2005 06:58:10.0911 (UTC) FILETIME=[B151AEF0:01C5A61D] Cc: freebsd-hackers@freebsd.org Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 06:58:42 -0000 > "Mike Adewole" wrote: > cc: freebsd-hackers@freebsd.org, freebsd-libh@freebsd.org > I reduced to freebsd-hackers@freebsd.org tp avoid cross posting > (OK, libh might be more appropriate, but I'm not sub'd to that) > > > I'm looking for is people to maintain a community infrastructure (web site, > > mailing list, online forum, webcvs/svn, etc) which a community project like > > this needs in order to appeal to as many people as possible. > > > implementation of libh, we'll be using the old libh mailing list until we > > have another one. Come help us make *BSD a truly complete platform with the > > best console desktop environment in the universe :-) > > postmaster@freebsd.org would be best to approach if you just need another > mail list. If for some reason that's not appropriate I could host a list > under majordomo@berklix.org (sometime I'll convert to mailman). > > I could later also perhaps host CVS, I've got the space, > traffic & config I'd need to think about. > -- > Julian Stacey Consultant Systems Engineer, Munich. http://berklix.com > Mail in Ascii (Html = Spam). Ihr Rauch = mein allergischer Kopfschmerz. > Hey Julian, thanks for your interest in project bsdvision ! I may ask postmaster for a new mailing list if enough people show interest in the project; otherwise, I'll gladly accept your offer. I'm waiting for someone to volunteer to develop/maintain a community website at www.bsdvision.com since I don't have the time/resources/expertise to do it all by myself. Will let you know when we have enough people to get going. Thanks a lot & Cheers From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 07:12:21 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BC1916A41F for ; Sun, 21 Aug 2005 07:12:21 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [69.17.104.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31E4F43D45 for ; Sun, 21 Aug 2005 07:12:21 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [69.17.104.113]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id j7L7C8aY049944; Sun, 21 Aug 2005 03:12:20 -0400 (EDT) (envelope-from mdodd@FreeBSD.ORG) Date: Sun, 21 Aug 2005 03:12:08 -0400 (EDT) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: m.ehinger@ltur.de In-Reply-To: Message-ID: <20050821025614.O84830@sasami.jurai.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [69.17.104.113]); Sun, 21 Aug 2005 03:12:20 -0400 (EDT) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Parking disk drive heads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 07:12:21 -0000 On Wed, 17 Aug 2005 m.ehinger@ltur.de wrote: > which is the correct way to park the hd head? The documentation will refer to this operation as "Unload". Standby (0xE2) or Standby Immediate (0xE0) would be the only way I can see to do this. (Sleep performs an unload as well, but is not useful for your purposes.) Some of the low power idle modes supported by the Hitachi 5k100 mention head retraction to the ramp position, which might be of use provided the feature is widely supported on new hardware. Many drives support an "Emergency Unload" but it only appears to be activated by power failure. Anyhow, here is a snippet that should get you going (on 6.x/CURRENT): %%% #include ... struct ata_ioc_request req; int fd; fd = open("/dev/ad0", O_RDONLY); memset(&req, 0, sizeof(struct ata_ioc_request)); req.u.ata.command = ATA_STANDBY_IMMEDIATE; req.flags = ATA_CMD_CONTROL; req.timeout = 5; ioctl(fd, IOCATAREQUEST, &req); close(fd); -- 10 40 80 C0 00 FF FF FF FF C0 00 00 00 00 10 AA AA 03 00 00 00 08 00 From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 07:45:59 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBB8C16A41F for ; Sun, 21 Aug 2005 07:45:59 +0000 (GMT) (envelope-from lists@nbux.com) Received: from smtp12.wanadoo.fr (smtp12.wanadoo.fr [193.252.22.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAE7B43D48 for ; Sun, 21 Aug 2005 07:45:56 +0000 (GMT) (envelope-from lists@nbux.com) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1206.wanadoo.fr (SMTP Server) with ESMTP id 2F6441C000A3 for ; Sun, 21 Aug 2005 09:45:55 +0200 (CEST) Received: from daneel.nbux.com (LNeuilly-152-22-15-131.w82-127.abo.wanadoo.fr [82.127.94.131]) by mwinf1206.wanadoo.fr (SMTP Server) with ESMTP id 06AC21C000A0; Sun, 21 Aug 2005 09:45:54 +0200 (CEST) X-ME-UUID: 20050821074555274.06AC21C000A0@mwinf1206.wanadoo.fr Received: from [192.168.42.2] (daneel.nbux.com [192.168.42.2]) by daneel.nbux.com (Postfix) with ESMTP id 2EC0F1C32F0; Sun, 21 Aug 2005 09:45:54 +0200 (CEST) Message-ID: <43083131.4010407@nbux.com> Date: Sun, 21 Aug 2005 09:45:53 +0200 From: Christophe Yayon Organization: nbux.com User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christophe Yayon References: <4306DA96.8000904@nbux.com> In-Reply-To: <4306DA96.8000904@nbux.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Eischen , freebsd-hackers@freebsd.org Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 07:46:00 -0000 Hi again, I just upgraded again to FreeBSD5.4-Stable of August 20 and, i just killed a nagios loop process which consume 100% of CPU... The problem seems to persist again... How do think about this ? Thanks in advance. Christophe Yayon wrote: > Daniel, > > > But i am in stable '5.4-STABLE FreeBSD 5.4-STABLE #4: Tue Jul 5 > 11:18:14 CEST 2005' and i have again the problem ... > The post is from Jun 22... I don't understant why i have again the > problem ? > Could u help me, please ? > > Thanks. > > Daniel Eischen wrote: > >> On Fri, 19 Aug 2005, Christophe Yayon wrote: >> >> >>> Hi all >>> >>> You should know about freebsd and nagios 2.0b threads issues (100% cpu >>> use by a forked process, lost check result, some pause of nagios main >>> process in certains obscursives conditions...). >>> >>> Some Nagios developpers says that the problem is in FreeBSD and some >>> other says that the problem is in nagios pthreads implementation, here a >>> resume of our discussions : >>> From >>> >>> http://www.opengroup.org/onlinepubs/009695399/functions/pthread_atfork.html >>> >>> >>> "It is suggested that programs that use fork() call an exec function >>> very soon afterwards in the child process, thus resetting all >>> states. In >>> the meantime, only a short list of async-signal-safe library routines >>> are promised to be available." >>> >>> Note *suggested*. This is a recommendation to protect against a shoddy >>> pthread-implementation. The thread specifications rule that only the >>> thread calling fork() is duplicated, which initially leads to the >>> recommendation (other threads holding locks aren't around to release >>> them in the new execution context). >> >> >> >> They choose to quote a weak reference to the actual requirement. >> The standard says (in the fork() section): >> >> A process shall be created with a single thread. If a >> multi-threaded process calls fork(), the new process shall >> contain a replica of the calling thread and its entire address >> space, possibly including the states of mutexes and other >> resources. Consequently, to avoid errors, the child process may >> only execute async-signal-safe operations until such time as one >> of the exec functions is called. Fork handlers may be >> established by means of the pthread_atfork() function in order >> to maintain application invariants across fork() calls. >> > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 08:39:22 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 505E016A41F for ; Sun, 21 Aug 2005 08:39:22 +0000 (GMT) (envelope-from kamalpr@yahoo.com) Received: from web52713.mail.yahoo.com (web52713.mail.yahoo.com [206.190.48.236]) by mx1.FreeBSD.org (Postfix) with SMTP id 710C543D53 for ; Sun, 21 Aug 2005 08:39:21 +0000 (GMT) (envelope-from kamalpr@yahoo.com) Received: (qmail 4676 invoked by uid 60001); 21 Aug 2005 08:39:20 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=x2kowY1e7yUjSgREXWcQyWE+MB753WgFbP5XGQAjzzrNrjf5Z4LUXxx2od5yP+48ooMmAI1+VxiAvAIkW5Z7Yqcl+9hqPh2ZIa2/PrBF0YTcQWtBk1FtG6UNc9+VHQstugyb3BDJus1m7TMdhIzZcViTeHP7CBtBIt8JGncJvdY= ; Message-ID: <20050821083920.4674.qmail@web52713.mail.yahoo.com> Received: from [221.128.128.154] by web52713.mail.yahoo.com via HTTP; Sun, 21 Aug 2005 01:39:20 PDT Date: Sun, 21 Aug 2005 01:39:20 -0700 (PDT) From: "Kamal R. Prasad" To: Mike Adewole , hselasky@c2i.net, freebsd-hackers@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kamalp@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 08:39:22 -0000 > It will be running on a virtual console in text or > graphics mode like > TurboVision used to, but we are focusing on text > mode for now. As I just > wrote to someone else, the main idea is to enable > BSD programs to have a > nice console (textual and graphical) interface with > and without any windows > system. So I could have a standalone program that Thst would be great to have and extend to a full-fledged GUI interface as X is overkill for lots of people. BTW -does it use drivers for graphics accelerator cards? thanks -kamal > looks like an X program > for example but runs on a virtual console without X. > Or I could have the > program run in a desktop environment with other > programs without changing a > single line of code or recompiling the program. > > Cheers > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org" > ------------------------------------------------------------ Kamal R. Prasad UNIX systems consultant http://www.kamalprasad.com/ kamalp@acm.org In theory, there is no difference between theory and practice. In practice, there is. ------------------------------------------------------------ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 09:48:53 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 87A0116A41F for ; Sun, 21 Aug 2005 09:48:53 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id EED7243D46 for ; Sun, 21 Aug 2005 09:48:52 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.4/8.13.3) with ESMTP id j7L9mn0q079972 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sun, 21 Aug 2005 11:48:49 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id j7L9mnhn079971 for hackers@freebsd.org; Sun, 21 Aug 2005 11:48:49 +0200 (CEST) Date: Sun, 21 Aug 2005 11:48:49 +0200 From: Divacky Roman To: hackers@freebsd.org Message-ID: <20050821094849.GA79907@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 Cc: Subject: number of simultanously opened files X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 09:48:53 -0000 hi I wrote this: witten /tmp# cat x.c #include #include #include #define MAX 100000 main() { int i = MAX; for (; i>0; i--) { if (open("/dev/null", O_RDONLY) == -1) { printf("FUCK: %i\n", MAX-i); printf("FUCK: %i\n", i); break; } } getchar(); } set: witten ~# sysctl kern.maxfiles=100000 kern.maxfiles: 100000 -> 100000 witten ~# sysctl kern.maxfilesperproc=100000 kern.maxfilesperproc: 100000 -> 100000 witten ~# but I still cannot open more than 7319 files simultaneously. pls can you tell me why? thnx roman From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 10:26:39 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E66A416A41F for ; Sun, 21 Aug 2005 10:26:38 +0000 (GMT) (envelope-from victor.cruceru@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FA3443D45 for ; Sun, 21 Aug 2005 10:26:38 +0000 (GMT) (envelope-from victor.cruceru@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so830179wra for ; Sun, 21 Aug 2005 03:26:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=SRyZCvQ85Z4qVRGUsSvMeEKIQJfFCLbeuX7uJKXOPvta2eW/MgsuQB4za2RdJ8vLfC2I7td7sf80U59j7mA6P/s+0zzz0lOr2lFTrg5XKfYUWYfx59cdDiaa/DXd6n7ekPbpVTGKcqv3vFibFT70V0cmSO5t713WsfcdCmnrsCA= Received: by 10.54.147.16 with SMTP id u16mr915647wrd; Sun, 21 Aug 2005 03:26:37 -0700 (PDT) Received: by 10.54.91.20 with HTTP; Sun, 21 Aug 2005 03:26:37 -0700 (PDT) Message-ID: <4940255050821032669f7b13a@mail.gmail.com> Date: Sun, 21 Aug 2005 13:26:37 +0300 From: victor cruceru To: Divacky Roman In-Reply-To: <20050821094849.GA79907@stud.fit.vutbr.cz> Mime-Version: 1.0 References: <20050821094849.GA79907@stud.fit.vutbr.cz> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: hackers@freebsd.org Subject: Re: number of simultanously opened files X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: soc-victor@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 10:26:39 -0000 And errno (from a failed open) is ....? On 8/21/05, Divacky Roman wrote: >=20 > hi >=20 > I wrote this: > witten /tmp# cat x.c > #include > #include > #include >=20 > #define MAX 100000 > main() > { > int i =3D MAX; >=20 > for (; i>0; i--) { > if (open("/dev/null", O_RDONLY) =3D=3D -1) { > printf("FUCK: %i\n", MAX-i); > printf("FUCK: %i\n", i); > break; > } > } > getchar(); > } >=20 > set: >=20 > witten ~# sysctl kern.maxfiles=3D100000 > kern.maxfiles: 100000 -> 100000 > witten ~# sysctl kern.maxfilesperproc=3D100000 > kern.maxfilesperproc: 100000 -> 100000 > witten ~# >=20 > but I still cannot open more than 7319 files simultaneously. pls can you= =20 > tell > me why? >=20 > thnx >=20 > roman > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org= " > From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 11:50:16 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5269B16A41F for ; Sun, 21 Aug 2005 11:50:16 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F3CB43D46 for ; Sun, 21 Aug 2005 11:50:15 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.4/8.13.3) with ESMTP id j7LBoBmr082033 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 21 Aug 2005 13:50:11 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id j7LBoBc1082032; Sun, 21 Aug 2005 13:50:11 +0200 (CEST) Date: Sun, 21 Aug 2005 13:50:11 +0200 From: Divacky Roman To: victor cruceru Message-ID: <20050821115011.GA81983@stud.fit.vutbr.cz> References: <20050821094849.GA79907@stud.fit.vutbr.cz> <4940255050821032669f7b13a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4940255050821032669f7b13a@mail.gmail.com> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 Cc: hackers@freebsd.org Subject: Re: number of simultanously opened files X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 11:50:16 -0000 On Sun, Aug 21, 2005 at 01:26:37PM +0300, victor cruceru wrote: > And errno (from a failed open) is ....? sorry for not mentioning it... of course its: Too many open files (obtained by perror()) From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 12:57:44 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6F5A16A41F for ; Sun, 21 Aug 2005 12:57:44 +0000 (GMT) (envelope-from misha@onet.ru) Received: from mail.onet.ru (mail.onet.ru [213.85.10.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCECF43D45 for ; Sun, 21 Aug 2005 12:57:43 +0000 (GMT) (envelope-from misha@onet.ru) Received: from mail.onet.ru (localhost [127.0.0.1]) by mail.onet.ru (Postfix) with ESMTP id 666E045217 for ; Sun, 21 Aug 2005 16:57:41 +0400 (MSD) Received: by mail.onet.ru (Postfix, from userid 1003) id 4311F45211; Sun, 21 Aug 2005 16:57:41 +0400 (MSD) Received: from [213.85.50.124] (pppoe-50-124.onet.ru [213.85.50.124]) by mail.onet.ru (Postfix) with ESMTP id E46C1453F0 for ; Sun, 21 Aug 2005 16:57:30 +0400 (MSD) Message-ID: <43087A39.7000106@onet.ru> Date: Sun, 21 Aug 2005 16:57:29 +0400 From: Michael User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.onet.ru X-Spam-Level: X-Spam-Status: No, score=-3.5 required=2.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.4 X-AV-Checked: ClamAV using ClamSMT Subject: MAC Biba policy. High marked process can't write to high marked file. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 12:57:44 -0000 Hello, hackers. First of all have to apologize for english, sorry. I was playing with Mandatory Access Control, all have been done like it described in handbook: I have added 'insecure' class with "label=partition/13,mls/5,biba/low". Then created 'mactest' user and placed it there. I have turned on multilable support on /usr FS. All MAC policies are loaded at boot time from /boot/loader.conf. But I come into collision with problem. According to man page (mac_biba(4)), no write up and no read down allowed. If object and subject have equal (high and high, or low and low) markers it means "as Biba protections were not in place." Some of my testings goes below, and I have stumbled at writing high->high (it gives me "permission denied"). Low->low works perfect. The question is: what I'm doing wrong? Is it just misunderstanding of handbook or something else? %getfmac test test: biba/high,mls/equal # Make sure, that MLS won't bother us %setfmac biba/low test %setpmac biba/high echo 1 > test # 'high' can write to 'low'... %setpmac biba/high cat test cat: test: Permission denied # ...but can't read (o.k.) %setpmac biba/low cat test # equal levels (low and low) can do everything 1 %setpmac biba/low echo 1 >> test %setpmac biba/low cat test # it either can write to file 1 1 %setfmac biba/high test # set to file 'high' ticket %setpmac biba/high echo 1 >> test # bah! test: Permission denied. %setpmac biba/high ls -lZ test -rw-r--r-- 1 mactest wheel biba/high,mls/equal 4 Aug 21 16:30 test From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 13:30:56 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3A3116A41F for ; Sun, 21 Aug 2005 13:30:56 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from bloodwood.hunterlink.net.au (smtp-local.hunterlink.net.au [203.12.144.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3912C43D49 for ; Sun, 21 Aug 2005 13:30:55 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from ppp2A47.dyn.pacific.net.au (ppp2A47.dyn.pacific.net.au [61.8.42.71]) by bloodwood.hunterlink.net.au (8.12.8/8.12.8) with ESMTP id j7LDSZTh026783; Sun, 21 Aug 2005 23:28:36 +1000 From: Sam Lawrance To: Divacky Roman In-Reply-To: <20050821094849.GA79907@stud.fit.vutbr.cz> References: <20050821094849.GA79907@stud.fit.vutbr.cz> Content-Type: text/plain Date: Sun, 21 Aug 2005 23:31:01 +1000 Message-Id: <1124631061.38048.14.camel@dirk.no.domain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: number of simultanously opened files X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 13:30:56 -0000 On Sun, 2005-08-21 at 11:48 +0200, Divacky Roman wrote: > hi > > I wrote this: > witten /tmp# cat x.c > #include > #include > #include > > #define MAX 100000 > main() > { > int i = MAX; > > for (; i>0; i--) { > if (open("/dev/null", O_RDONLY) == -1) { > printf("FUCK: %i\n", MAX-i); > printf("FUCK: %i\n", i); > break; > } > } > getchar(); > } > > set: > > witten ~# sysctl kern.maxfiles=100000 > kern.maxfiles: 100000 -> 100000 > witten ~# sysctl kern.maxfilesperproc=100000 > kern.maxfilesperproc: 100000 -> 100000 > witten ~# > > but I still cannot open more than 7319 files simultaneously. pls can you tell > me why? Possibly because maximum open files is a per-process value that is set at process creation, and also inherited, so you won't see the change in existing processes. Try setting it before boot, or maybe restarting a login on a vty might work. Cheers Sam Sam Lawrance lawrance@FreeBSD.org ph +61 0425 228 579 boris@brooknet.com.au From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 13:45:24 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8154416A41F for ; Sun, 21 Aug 2005 13:45:24 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 286E543D48 for ; Sun, 21 Aug 2005 13:45:24 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j7LDjMqm006589; Sun, 21 Aug 2005 09:45:23 -0400 (EDT) Date: Sun, 21 Aug 2005 09:45:22 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Christophe Yayon In-Reply-To: <43083131.4010407@nbux.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 13:45:24 -0000 On Sun, 21 Aug 2005, Christophe Yayon wrote: > Hi again, > > I just upgraded again to FreeBSD5.4-Stable of August 20 and, i just > killed a nagios loop process which consume 100% of CPU... > The problem seems to persist again... > > How do think about this ? > Thanks in advance. Go ask the nagios guys. If they are doing things after a fork() from a threaded application that are not allowed by POSIX, then they need to address it. > >> They choose to quote a weak reference to the actual requirement. > >> The standard says (in the fork() section): > >> > >> A process shall be created with a single thread. If a > >> multi-threaded process calls fork(), the new process shall > >> contain a replica of the calling thread and its entire address > >> space, possibly including the states of mutexes and other > >> resources. Consequently, to avoid errors, the child process may > >> only execute async-signal-safe operations until such time as one > >> of the exec functions is called. Fork handlers may be > >> established by means of the pthread_atfork() function in order > >> to maintain application invariants across fork() calls. -- DE From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 13:57:25 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EBD716A420 for ; Sun, 21 Aug 2005 13:57:25 +0000 (GMT) (envelope-from lists@nbux.com) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A9E043D45 for ; Sun, 21 Aug 2005 13:57:24 +0000 (GMT) (envelope-from lists@nbux.com) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1107.wanadoo.fr (SMTP Server) with ESMTP id D08121C0008F for ; Sun, 21 Aug 2005 15:57:22 +0200 (CEST) Received: from daneel.nbux.com (LNeuilly-152-22-15-131.w82-127.abo.wanadoo.fr [82.127.94.131]) by mwinf1107.wanadoo.fr (SMTP Server) with ESMTP id 9321D1C0008D; Sun, 21 Aug 2005 15:57:22 +0200 (CEST) X-ME-UUID: 20050821135722602.9321D1C0008D@mwinf1107.wanadoo.fr Received: from [192.168.42.2] (daneel.nbux.com [192.168.42.2]) by daneel.nbux.com (Postfix) with ESMTP id 013F91C353D; Sun, 21 Aug 2005 15:57:21 +0200 (CEST) Message-ID: <43088841.4090709@nbux.com> Date: Sun, 21 Aug 2005 15:57:21 +0200 From: Christophe Yayon Organization: nbux.com User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 13:57:25 -0000 I have already asked them... here is a resume of our conversation (me and other freebsd guys) : ------- The thread I started is here: http://marc.theaimsgroup.com/?t=111930118000001&r=1&w=2 There are some very interesting replies, a few in particular note that Nagios may be breaking POSIX spec in how it spawns/destroys threads: http://marc.theaimsgroup.com/?l=freebsd-hackers&m=111944526323754&w=2 http://marc.theaimsgroup.com/?l=freebsd-hackers&m=111945035012258&w=2 Anyhow, I"m sure if Ethan were to post some more specific info to freebsd-hackers@fr... (it"s an open list, no need to sub), this issue could get banged out pretty quickly. Shortly after this thread, I found another where the issue was brought up by another curious poster, and he was using 5.4, which uses a newer threading library: http://marc.theaimsgroup.com/?t=112119712600002&r=1&w=2 This post again brings up the "fork without exec or exit" possibly not following spec: http://marc.theaimsgroup.com/?l=freebsd-hackers&m=112125883804481&w=2 "I don"t know what Nagios does just after fork(2), it would be worth to check. It appears that fork(2)ing without exec(2)ing or _exit(2)ing in a pthreaded program is not a "valid" behaviour, regarding to SUSv3 [1]. I don"t want to avoid admitting there is a problem in FreeBSD threading library, I don"t know how other OSes handle this, but Nagios folks should really avoid doing what is explicitely dissuaded in SUSv3." -------- -------- As the problem isn't in Nagios and noone seems to have an authoritative answer on what exactly is causing it, I'd say you would be better off switching to a GNU/Linux system, with at least Linux 2.4.29 and glibc-2.3 (a lot work was put into thread-safeness on glibc-2.3). -------- -------- From http://www.opengroup.org/onlinepubs/009695399/functions/pthread_atfork.html "It is suggested that programs that use fork() call an exec function very soon afterwards in the child process, thus resetting all states. In the meantime, only a short list of async-signal-safe library routines are promised to be available." Note *suggested*. This is a recommendation to protect against a shoddy pthread-implementation. The thread specifications rule that only the thread calling fork() is duplicated, which initially leads to the recommendation (other threads holding locks aren't around to release them in the new execution context). That said, Nagios would most likely benefit greatly from a different means of checking things than fork()'ing twice and sending the results through several tiers of FIFO's. Several different methods have already been benchmarked. For server machines (or at least cans with a lot of memory and quite regularly multiple CPU's), the best way seems to be to create a new thread for each check to run. popen() causes a fork() and execve(), so that should be safe enough. What limits this imposes I don't know, but the NPTL library in use on most modern linux systems today handles 10.000 threads without barfing, so the limit would probably be sysconf(_SC_MAX_FILES), or ulimit -n, which is required by posix to be at least 256. Note that half this value (give or take 5 or so for stdin and such) represents the number of checks that can run simultaneously at any given time. When one of them completes another can kick in. -------- in others words, somebody says that this a nagios problem and others says it is a freebsd problem ... Daniel Eischen wrote: > On Sun, 21 Aug 2005, Christophe Yayon wrote: > > >>Hi again, >> >>I just upgraded again to FreeBSD5.4-Stable of August 20 and, i just >>killed a nagios loop process which consume 100% of CPU... >>The problem seems to persist again... >> >>How do think about this ? >>Thanks in advance. > > > Go ask the nagios guys. If they are doing things after a fork() > from a threaded application that are not allowed by POSIX, then > they need to address it. > > >>>>They choose to quote a weak reference to the actual requirement. >>>>The standard says (in the fork() section): >>>> >>>> A process shall be created with a single thread. If a >>>> multi-threaded process calls fork(), the new process shall >>>> contain a replica of the calling thread and its entire address >>>> space, possibly including the states of mutexes and other >>>> resources. Consequently, to avoid errors, the child process may >>>> only execute async-signal-safe operations until such time as one >>>> of the exec functions is called. Fork handlers may be >>>> established by means of the pthread_atfork() function in order >>>> to maintain application invariants across fork() calls. > > From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 15:34:36 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CB3816A41F for ; Sun, 21 Aug 2005 15:34:36 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id D035243D48 for ; Sun, 21 Aug 2005 15:34:35 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id 04AAA46B4B; Sun, 21 Aug 2005 11:34:25 -0400 (EDT) Date: Sun, 21 Aug 2005 16:39:24 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Michael In-Reply-To: <43087A39.7000106@onet.ru> Message-ID: <20050821163830.D44147@fledge.watson.org> References: <43087A39.7000106@onet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org Subject: Re: MAC Biba policy. High marked process can't write to high marked file. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 15:34:36 -0000 On Sun, 21 Aug 2005, Michael wrote: > %setpmac biba/high echo 1 >> test # bah! > test: Permission denied. Remember that the '>>' is evaluated in the parent shell context, not the execution context set up by setpmac. Try doing "setpmac biba/high csh" and see how that changes the results when you run the complete command in that context? Robert N M Watson From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 15:38:06 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E9C516A41F for ; Sun, 21 Aug 2005 15:38:06 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7443343D45 for ; Sun, 21 Aug 2005 15:38:04 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 87CE95C99; Sun, 21 Aug 2005 17:38:03 +0200 (CEST) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 51791-01; Sun, 21 Aug 2005 17:37:57 +0200 (CEST) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id 340E75C96; Sun, 21 Aug 2005 17:37:57 +0200 (CEST) Received: from 192.168.1.20 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Sun, 21 Aug 2005 17:37:57 +0200 (CEST) Message-ID: <59274.192.168.1.20.1124638677.squirrel@webmail.thilelli.net> In-Reply-To: References: <42F93030.2050509@thesnodgrass.com> <10303.145.248.192.30.1123662749.squirrel@webmail.thilelli.net> <57189.145.248.192.30.1123665610.squirrel@webmail.thilelli.net> Date: Sun, 21 Aug 2005 17:37:57 +0200 (CEST) From: "Julien Gabel" To: "Dmitry Mityugov" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Cc: freebsd-hackers@freebsd.org Subject: Re: Realtek RTL8169 on FreeBSD 5.4: no carrier. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpeg@thilelli.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 15:38:06 -0000 >>>> Regrettably, i always encountered this problem. I spoke about that >>>> since the middle of 2004, and didn't really receive feedback on this. >>>> I try a lot of things but none worked better than the other. >>>> >>>> To not forget about it, i filled a bug report on this particular >>>> problem, see PR kern/80005 for more details. >>>> >>>> The last thing i want to give another try is to upgrade to RELENG_6, >>>> since i currently follow the RELENG_5 branch. But i am not *very* >>>> confident about that... >>>> >>>> Sorry not to have better answer to give you. >>> IIRC, I have a RTL8169S-based D-Link gigabit network card at home and >>> it works with FreeBSD just fine. >> Yes, i know it simply works for a lot of users. It doesn't mean that it >> is the case for all users... i am of those. > Just realized that with ACPI disabled, this card does not work with > FreeBSD 5.4 (at least in my machine), with ACPI enabled - it does. > Hope this information will help somebody. With or without ACPI support, it doesn't chang anything here. Under RELENG_6 now, i always get the problem with these (lot of) kernel messages at boot time: - re0: 2 link states coalesced - re0: link state changed to DOWN - re0: link state changed to UP Note 1: It is a little better though, since the DHCP client can wait in foreground the link to come up then only continue the boot, making network related stuff relatively happy (ntpdate, ntpd, etc.). Note 2: Just try to disable APIC but leave ACPI enable (as this helped me in an other situation and for an other problem, see PR usb/74989)... this leads me to a LOR follow by a panic (try this 3 times) at boot time. So, it seems a very bad idea here :\ Thanks, -- -jpeg. From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 15:38:10 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D94E16A42D for ; Sun, 21 Aug 2005 15:38:10 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from smtp.thilelli.net (smtp.thilelli.net [213.41.129.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9F0343D48 for ; Sun, 21 Aug 2005 15:38:08 +0000 (GMT) (envelope-from jpeg@thilelli.net) Received: from localhost (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id DD87A5C9A; Sun, 21 Aug 2005 17:38:07 +0200 (CEST) Received: from bento.thilelli.net ([127.0.0.1]) by localhost (bento.thilelli.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 50673-06; Sun, 21 Aug 2005 17:38:02 +0200 (CEST) Received: from webmail.thilelli.net (localhost [127.0.0.1]) by bento.thilelli.net (Postfix) with ESMTP id B0A2C5C98; Sun, 21 Aug 2005 17:38:02 +0200 (CEST) Received: from 192.168.1.20 (SquirrelMail authenticated user jgabel) by webmail.thilelli.net with HTTP; Sun, 21 Aug 2005 17:38:02 +0200 (CEST) Message-ID: <59274.192.168.1.20.1124638682.squirrel@webmail.thilelli.net> In-Reply-To: <20050820225029.GF5673@gargantuan.com> References: <42F93030.2050509@thesnodgrass.com> <10303.145.248.192.30.1123662749.squirrel@webmail.thilelli.net> <57189.145.248.192.30.1123665610.squirrel@webmail.thilelli.net> <20050820225029.GF5673@gargantuan.com> Date: Sun, 21 Aug 2005 17:38:02 +0200 (CEST) From: "Julien Gabel" To: "Dmitry Mityugov" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: amavisd-new at thilelli.net Cc: freebsd-hackers@freebsd.org Subject: Re: Realtek RTL8169 on FreeBSD 5.4: no carrier. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jpeg@thilelli.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 15:38:10 -0000 >>>>> Regrettably, i always encountered this problem. I spoke about that >>>>> since the middle of 2004, and didn't really receive feedback on this. >>>>> I try a lot of things but none worked better than the other. >>>>> >>>>> To not forget about it, i filled a bug report on this particular >>>>> problem, see PR kern/80005 for more details. >>>>> >>>>> The last thing i want to give another try is to upgrade to RELENG_6, >>>>> since i currently follow the RELENG_5 branch. But i am not *very* >>>>> confident about that... >>>>> >>>>> Sorry not to have better answer to give you. >>>> IIRC, I have a RTL8169S-based D-Link gigabit network card at home and >>>> it works with FreeBSD just fine. >>> Yes, i know it simply works for a lot of users. It doesn't mean that >>> it is the case for all users... i am of those. >> Just realized that with ACPI disabled, this card does not work with >> FreeBSD 5.4 (at least in my machine), with ACPI enabled - it does. >> Hope this information will help somebody. I just replied to this on an other post. > I have RTL8169S in my laptop, and have seen the same up/down/up/down > etc. behavior that is noted in PR 80005. I am running 7-CURRENT about a > day old. I switched from my custom kernel back to GENERIC and the > problem went away, so I started adding things from my custom config file > into GENERIC to see what finally broke it, and it turned out to be: > > options ACPI_DEBUG > > Just thought that I would mention it... Certainly, thanks... very interesting! Although it doesn't seems to be the problem, since i didn't set this kernel option. On the other hand, i am currently testing RELENG_6, not -CURRENT: maybe is this problem finally fixed on HEAD (i will give it a try in a near future, if i can). Thank you, -- -jpeg. From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 21:55:42 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A56416A41F; Sun, 21 Aug 2005 21:55:42 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (afields.ca [216.194.67.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id C362443D46; Sun, 21 Aug 2005 21:55:41 +0000 (GMT) (envelope-from afields@afields.ca) Received: from afields.ca (localhost.afields.ca [127.0.0.1]) by afields.ca (8.12.11/8.12.11) with ESMTP id j7LLtfSM081489; Sun, 21 Aug 2005 17:55:41 -0400 (EDT) (envelope-from afields@afields.ca) Received: (from afields@localhost) by afields.ca (8.12.11/8.12.11/Submit) id j7LLteS7081488; Sun, 21 Aug 2005 17:55:40 -0400 (EDT) (envelope-from afields) Date: Sun, 21 Aug 2005 17:55:40 -0400 From: Allan Fields To: Mike Adewole Message-ID: <20050821215540.GC58723@afields.ca> References: <00d101c5a570$7b322050$6501a8c0@newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00d101c5a570$7b322050$6501a8c0@newton> User-Agent: Mutt/1.4i Cc: freebsd-libh@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 21:55:42 -0000 On Sat, Aug 20, 2005 at 06:18:13AM -0400, Mike Adewole wrote: > For many people who spend a lot of time on the *BSD console and would love > to have a desktop environment comparable to KDE/GNOME, I'm starting a > project called BSDVISION to develop such an environment. Please don't ask if > such an environment is really needed or not; the important thing is that > some people like me need it badly enough to want to develop it. And here I thought you were talking about a desktop for us vt220 fans. There is already screen or emacs on that front. What about twin for example? What exactly is meant by a "console" desktop anyway other than something similar to early Windows that runs w/o X11? Can you also make a Unicode console for *BSD please? ;) > As a matter of fact, it has been in development for some time now and I > think it's getting to the point where it makes sense to ask for community > involvement. But I'm not looking for developers because development will > continue to be done by myself with the assistance of paid contractors. What > I'm looking for is people to maintain a community infrastructure (web site, > mailing list, online forum, webcvs/svn, etc) which a community project like > this needs in order to appeal to as many people as possible. > > So if you love the BSD console and would like to see it sport a complete > desktop environment, the bsdvision project can really use your support. And > since this project developed from an attempt to do a cleanroom > implementation of libh, we'll be using the old libh mailing list until we > have another one. Come help us make *BSD a truly complete platform with the > best console desktop environment in the universe :-) -- Allan Fields From owner-freebsd-hackers@FreeBSD.ORG Sun Aug 21 23:12:50 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B03816A41F for ; Sun, 21 Aug 2005 23:12:50 +0000 (GMT) (envelope-from thib@mi.is) Received: from quasar.skima.is (quasar.skima.is [212.30.200.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 901CB43D45 for ; Sun, 21 Aug 2005 23:12:49 +0000 (GMT) (envelope-from thib@mi.is) Received: from caulfield ([85.220.68.246] [85.220.68.246]) by quasar.skima.is; Sun, 21 Aug 2005 23:12:47 Z Date: Sun, 21 Aug 2005 23:12:47 +0000 From: "Thordur I. Bjornsson" To: hackers@freebsd.org Message-Id: <20050821231247.567b9c2f.thib@mi.is> Organization: n/a X-Mailer: Sylpheed version 1.0.5 (GTK+ 1.2.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Sun__21_Aug_2005_23_12_47_+0000_zdzsde=exJt6uwzc" Cc: Subject: xl driver proplem. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Aug 2005 23:12:50 -0000 This is a multi-part message in MIME format. --Multipart=_Sun__21_Aug_2005_23_12_47_+0000_zdzsde=exJt6uwzc Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hello list. I had this proplem with the xl driver: Aug 21 22:45:38 caulfield kernel: taskqueue_drain with the following non-sleepable locks held: Aug 21 22:45:38 caulfield kernel: exclusive sleep mutex xl0 (network driver) r = 0 (0xc23c00a4) locked @ /usr/src/sys/pci/if_xl.c:2796 Aug 21 22:45:38 caulfield kernel: KDB: stack backtrace: Aug 21 22:45:38 caulfield kernel: witness_warn(2,0,c071f440,c23aa600,ed0baa80) at witness_warn+0x5d6 Aug 21 22:45:38 caulfield kernel: taskqueue_drain(c2287800,c23c00c8,c072a962,cc7,c23ac400) at taskqueue_drain+0x2e Aug 21 22:45:38 caulfield kernel: xl_stop(c23c00a4,1,c072a962,af9,c07c50d0) at xl_stop+0x56 Aug 21 22:45:38 caulfield kernel: xl_init_locked(c23c00a4,8,c072a962,aec,c23ac400) at xl_init_locked+0x47 Aug 21 22:45:38 caulfield kernel: xl_init(c23be000,740,c072eec1,8020690c,c23be000) at xl_init+0x3c Aug 21 22:45:38 caulfield kernel: ether_ioctl(c23ac400,8020690c,c2577e00,c055b96a,c0779dc0) at ether_ioctl+0xa4 Aug 21 22:45:38 caulfield kernel: xl_ioctl(c23ac400,8020690c,c2577e00,504,c2577e7c) at xl_ioctl+0xc8 Aug 21 22:45:38 caulfield kernel: in_ifinit(c2560350,0,0,0,ed0bab98) at in_ifinit+0xa6 Aug 21 22:45:38 caulfield kernel: in_control(c25e2de8,8040691a,c2560340,c23ac400,c23aa600) at in_control+0xe84 Aug 21 22:45:38 caulfield kernel: ifioctl(c25e2de8,8040691a,c2560340,c23aa600,2) at ifioctl+0x12d Aug 21 22:45:38 caulfield kernel: soo_ioctl(c2570438,8040691a,c2560340,c2286d00,c23aa600) at soo_ioctl+0x2c9 Aug 21 22:45:38 caulfield kernel: ioctl(c23aa600,ed0bad04,c,422,3) at ioctl+0x118 Aug 21 22:45:38 caulfield kernel: syscall(3b,3b,3b,8058900,0) at syscall+0x13b Aug 21 22:45:38 caulfield kernel: Xint0x80_syscall() at Xint0x80_syscall+0x1f Aug 21 22:45:38 caulfield kernel: --- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d9593, esp = 0xbfbfe5fc, ebp = 0xbfbfee68 --- According to http://lists.freebsd.org/pipermail/freebsd-current/2005-May/050526.html taskqueue_drain() can not be called while holding a lock. I made a simple change to pull taskqueue_drain() out of xl_stop() and call it before the lock is taken in xl_init() This made the "proplem go away (TM)" and I have not noticed any proplems e.g. performance,uptime (on the NIC) &c. Still, when I reboot/shutdown the machine I see some funkyness but it scrolls by too fast, I'm currently on my why to the garage to make myself a null-modem cable and to some debugging ;) Attached is the diff. -- Thordur I. Humppa! --Multipart=_Sun__21_Aug_2005_23_12_47_+0000_zdzsde=exJt6uwzc Content-Type: text/plain; name="if_xl.diff" Content-Disposition: attachment; filename="if_xl.diff" Content-Transfer-Encoding: 7bit *** if_xl.c.ORIG Sun Aug 21 21:56:20 2005 --- if_xl.c Sun Aug 21 23:05:33 2005 *************** *** 2792,2798 **** xl_init(void *xsc) { struct xl_softc *sc = xsc; ! XL_LOCK(sc); xl_init_locked(sc); XL_UNLOCK(sc); --- 2792,2804 ---- xl_init(void *xsc) { struct xl_softc *sc = xsc; ! ! /* XXX ! * taskqueue_drain() can not be called while holding a lock. ! * Appers to be working fine. Is this the right thing todo (TM) ? ! */ ! taskqueue_drain(taskqueue_swi, &sc->xl_task); ! XL_LOCK(sc); xl_init_locked(sc); XL_UNLOCK(sc); *************** *** 3274,3281 **** #ifdef DEVICE_POLLING ether_poll_deregister(ifp); #endif /* DEVICE_POLLING */ - - taskqueue_drain(taskqueue_swi, &sc->xl_task); CSR_WRITE_2(sc, XL_COMMAND, XL_CMD_RX_DISABLE); CSR_WRITE_2(sc, XL_COMMAND, XL_CMD_STATS_DISABLE); --- 3280,3285 ---- --Multipart=_Sun__21_Aug_2005_23_12_47_+0000_zdzsde=exJt6uwzc-- From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 04:36:55 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 273A916A41F for ; Mon, 22 Aug 2005 04:36:55 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail06.syd.optusnet.com.au (mail06.syd.optusnet.com.au [211.29.132.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82EC043D45 for ; Mon, 22 Aug 2005 04:36:50 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail06.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j7M4am1f029292 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 22 Aug 2005 14:36:48 +1000 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id j7M4amSR037262 for ; Mon, 22 Aug 2005 14:36:48 +1000 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id j7M4alGx037261 for hackers@freebsd.org; Mon, 22 Aug 2005 14:36:47 +1000 (EST) (envelope-from pjeremy) Date: Mon, 22 Aug 2005 14:36:47 +1000 From: Peter Jeremy To: hackers@freebsd.org Message-ID: <20050822043647.GB37107@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i Cc: Subject: Locating obsolete ports distfiles X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 04:36:55 -0000 I currently have just over 8GB is /usr/ports/distfiles. Some of these files are more than 10 years old and long obsolete. Does anyone have any suggestions on how to identify which files are no longer referenced by current ports? Doing a 'make checksum' on every installed port and then looking at the atimes is one approach but this doesn't handle: - ports that I don't currently have installed but might need - ports installed on systems that mount /usr/ports readonly -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 04:41:49 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6220016A41F for ; Mon, 22 Aug 2005 04:41:49 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: from mail3out.barnet.com.au (mail3out.barnet.com.au [202.83.176.17]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1B9043D45 for ; Mon, 22 Aug 2005 04:41:48 +0000 (GMT) (envelope-from edwin@mavetju.org) Received: by mail3out.barnet.com.au (Postfix, from userid 27) id 03B4F877C8C; Mon, 22 Aug 2005 14:41:45 +1000 (EST) X-Viruscan-Id: <43095788000090B75C9DD0@BarNet> Received: from mail3-auth.barnet.com.au (mail3.barnet.com.au [202.83.176.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.barnet.com.au", Issuer "BarNet Root Certificate Authority" (verified OK)) by mail3.barnet.com.au (Postfix) with ESMTP id D0456877C58; Mon, 22 Aug 2005 14:41:44 +1000 (EST) Received: from k7.mavetju (edwin-3.int.barnet.com.au [10.10.12.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "edwin.adsl.barnet.com.au", Issuer "BarNet Root Certificate Authority" (not verified)) by mail3-auth.barnet.com.au (Postfix) with ESMTP id 5B01C877C54; Mon, 22 Aug 2005 14:41:44 +1000 (EST) Received: by k7.mavetju (Postfix, from userid 1001) id A18EB6154; Mon, 22 Aug 2005 14:41:42 +1000 (EST) Date: Mon, 22 Aug 2005 14:41:42 +1000 From: Edwin Groothuis To: Peter Jeremy Message-ID: <20050822044142.GA1172@k7.mavetju> References: <20050822043647.GB37107@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050822043647.GB37107@cirb503493.alcatel.com.au> User-Agent: Mutt/1.5.9i Cc: hackers@freebsd.org Subject: Re: Locating obsolete ports distfiles X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 04:41:49 -0000 On Mon, Aug 22, 2005 at 02:36:47PM +1000, Peter Jeremy wrote: > I currently have just over 8GB is /usr/ports/distfiles. Some of these > files are more than 10 years old and long obsolete. Does anyone have > any suggestions on how to identify which files are no longer referenced > by current ports? Try portsclean and the --distclean option. portsclean is part of the portupgrade port. Edwin -- Edwin Groothuis | Personal website: http://www.mavetju.org edwin@mavetju.org | Weblog: http://weblog.barnet.com.au/edwin/ From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 04:43:15 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3575E16A41F for ; Mon, 22 Aug 2005 04:43:15 +0000 (GMT) (envelope-from mwm-keyword-hackers.e471b2@mired.org) Received: from delight.idiom.com (delight.idiom.com [216.240.32.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF25743D48 for ; Mon, 22 Aug 2005 04:43:14 +0000 (GMT) (envelope-from mwm-keyword-hackers.e471b2@mired.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 527C921D242 for ; Sun, 21 Aug 2005 21:43:14 -0700 (PDT) Received: from mired.org (mwm@idiom [216.240.32.1]) by idiom.com (8.12.11/8.12.11) with SMTP id j7M4h9SU047486 for ; Sun, 21 Aug 2005 21:43:11 -0700 (PDT) (envelope-from mwm-keyword-hackers.e471b2@mired.org) Received: (qmail 29859 invoked by uid 1001); 22 Aug 2005 04:43:35 -0000 Received: by localhost.mired.org (tmda-sendmail, from uid 1001); Mon, 22 Aug 2005 00:43:35 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17161.22518.896293.529642@bhuda.mired.org> Date: Mon, 22 Aug 2005 00:43:34 -0400 To: Peter Jeremy In-Reply-To: <20050822043647.GB37107@cirb503493.alcatel.com.au> References: <20050822043647.GB37107@cirb503493.alcatel.com.au> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Mike Meyer Cc: hackers@freebsd.org Subject: Re: Locating obsolete ports distfiles X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 04:43:15 -0000 In <20050822043647.GB37107@cirb503493.alcatel.com.au>, Peter Jeremy typed: > I currently have just over 8GB is /usr/ports/distfiles. Some of these > files are more than 10 years old and long obsolete. Does anyone have > any suggestions on how to identify which files are no longer referenced > by current ports? > > Doing a 'make checksum' on every installed port and then looking at > the atimes is one approach but this doesn't handle: > - ports that I don't currently have installed but might need > - ports installed on systems that mount /usr/ports readonly Install sysutils/portupgrade, and do a "portsclean -D". That will remove all the distfiles that aren't referenced by any port in the tree. Do "portsclean -DD" and it'll remove all distfiles not used by an installed port. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 04:47:21 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E944916A41F for ; Mon, 22 Aug 2005 04:47:21 +0000 (GMT) (envelope-from caelian@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82BF043D45 for ; Mon, 22 Aug 2005 04:47:21 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by zproxy.gmail.com with SMTP id z6so640035nzd for ; Sun, 21 Aug 2005 21:47:20 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=FwwOj1HtMA6A9UJ6shobR2cCfATQfk/Plc5QOzeTT6QFAdOe3lJTevMt57DBgt46TTmAkZCiObrBAPnsb+dk8JP6KuXPb58N3JYSeQnCKyz+BmJGy+NRkUvaeBNJjL9AilDZlAgTKqRls/mMj+0g0SE4gJjUKNxycG7Yhdy1ekI= Received: by 10.36.247.20 with SMTP id u20mr3299878nzh; Sun, 21 Aug 2005 21:47:20 -0700 (PDT) Received: from ?192.168.15.102? ([68.190.230.198]) by mx.gmail.com with ESMTP id p4sm3038143nzc.2005.08.21.21.47.20; Sun, 21 Aug 2005 21:47:20 -0700 (PDT) From: Pascal Hofstee To: Peter Jeremy In-Reply-To: <20050822043647.GB37107@cirb503493.alcatel.com.au> References: <20050822043647.GB37107@cirb503493.alcatel.com.au> Content-Type: text/plain Date: Sun, 21 Aug 2005 21:47:18 -0700 Message-Id: <1124686038.834.0.camel@synergy.charterpipeline.net.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.3.7 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: hackers@freebsd.org Subject: Re: Locating obsolete ports distfiles X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 04:47:22 -0000 On Mon, 2005-08-22 at 14:36 +1000, Peter Jeremy wrote: > I currently have just over 8GB is /usr/ports/distfiles. Some of these > files are more than 10 years old and long obsolete. Does anyone have > any suggestions on how to identify which files are no longer referenced > by current ports? > > Doing a 'make checksum' on every installed port and then looking at > the atimes is one approach but this doesn't handle: > - ports that I don't currently have installed but might need > - ports installed on systems that mount /usr/ports readonly sysutils/portupgrade (specifically .. portsclean -D) -- Pascal Hofstee From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 04:54:46 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2AC0616A41F; Mon, 22 Aug 2005 04:54:46 +0000 (GMT) (envelope-from avesnin@mirknigi.ru) Received: from mx1.mirknigi.ru (mx1.mirknigi.ru [217.114.33.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59F9043D46; Mon, 22 Aug 2005 04:54:44 +0000 (GMT) (envelope-from avesnin@mirknigi.ru) Received: from dummy.name; Mon, 22 Aug 2005 08:54:40 +0400 Message-ID: <004301c5a6d5$811662e0$260210ac@win> From: "Alexey Vesnin" To: "Daniel Eischen" References: Date: Mon, 22 Aug 2005 08:53:57 +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.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Cc: freebsd-hackers@freebsd.org Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 04:54:46 -0000 ----- Original Message ----- From: "Daniel Eischen" To: "Christophe Yayon" Cc: Sent: Friday, August 19, 2005 11:03 PM Subject: Re: nagios and freebsd threads issue : help please ... > On Fri, 19 Aug 2005, Christophe Yayon wrote: > > > Hi all > > > > You should know about freebsd and nagios 2.0b threads issues (100% cpu > > use by a forked process, lost check result, some pause of nagios main > > process in certains obscursives conditions...). > > > > Some Nagios developpers says that the problem is in FreeBSD and some > > other says that the problem is in nagios pthreads implementation, here a > > resume of our discussions : > > See http://www.freebsd.org/cgi/getmsg.cgi?fetch=340959+344806+/usr/local/www/db/ text/2005/freebsd-hackers/20050703.freebsd-hackers > > -- > DE > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > This is a common problem with more common salvation : use ports/devel/pth library. It will solve this problem COMPLETELY AT ALL. I'm currently running FreeBSD-4-STABLE build, upgradin' my kernel weekly and has no sign of such a problem. Always remember the main benefit of OpenSource - source is just a subject to work with... You may use defaults and they must work, but there's no guarantee that this will work fine and 100%-fast for YOUR hardware/software environment. Don't be shy to make modifications - developers aren't the ones who must do all the job for you. It's up toy you personally. Post Scriptum. 5.4 is not GOOD. It must be used ONLY if you don't have another way. It's memory leak is horrible.... From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 04:54:48 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77ECB16A41F; Mon, 22 Aug 2005 04:54:48 +0000 (GMT) (envelope-from avesnin@mirknigi.ru) Received: from mx1.mirknigi.ru (mx1.mirknigi.ru [217.114.33.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8BAF43D46; Mon, 22 Aug 2005 04:54:47 +0000 (GMT) (envelope-from avesnin@mirknigi.ru) Received: from dummy.name; Mon, 22 Aug 2005 08:54:45 +0400 Message-ID: <004401c5a6d5$83da8bf0$260210ac@win> From: "Alexey Vesnin" To: "Daniel Eischen" References: Date: Mon, 22 Aug 2005 08:53:59 +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.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Cc: freebsd-hackers@freebsd.org Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 04:54:48 -0000 ----- Original Message ----- From: "Daniel Eischen" To: "Christophe Yayon" Cc: Sent: Friday, August 19, 2005 11:03 PM Subject: Re: nagios and freebsd threads issue : help please ... > On Fri, 19 Aug 2005, Christophe Yayon wrote: > > > Hi all > > > > You should know about freebsd and nagios 2.0b threads issues (100% cpu > > use by a forked process, lost check result, some pause of nagios main > > process in certains obscursives conditions...). > > > > Some Nagios developpers says that the problem is in FreeBSD and some > > other says that the problem is in nagios pthreads implementation, here a > > resume of our discussions : > > See http://www.freebsd.org/cgi/getmsg.cgi?fetch=340959+344806+/usr/local/www/db/ text/2005/freebsd-hackers/20050703.freebsd-hackers > > -- > DE > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > This is a common problem with more common salvation : use ports/devel/pth library. It will solve this problem COMPLETELY AT ALL. I'm currently running FreeBSD-4-STABLE build, upgradin' my kernel weekly and has no sign of such a problem. Always remember the main benefit of OpenSource - source is just a subject to work with... You may use defaults and they must work, but there's no guarantee that this will work fine and 100%-fast for YOUR hardware/software environment. Don't be shy to make modifications - developers aren't the ones who must do all the job for you. It's up toy you personally. Post Scriptum. 5.4 is not GOOD. It must be used ONLY if you don't have another way. It's memory leak is horrible.... From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 05:38:18 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D24016A41F for ; Mon, 22 Aug 2005 05:38:18 +0000 (GMT) (envelope-from lists@nbux.com) Received: from smtp3.wanadoo.fr (smtp3.wanadoo.fr [193.252.22.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 768CF43D48 for ; Mon, 22 Aug 2005 05:38:17 +0000 (GMT) (envelope-from lists@nbux.com) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0303.wanadoo.fr (SMTP Server) with ESMTP id 532EB1C003E2 for ; Mon, 22 Aug 2005 07:38:16 +0200 (CEST) Received: from daneel.nbux.com (LNeuilly-152-22-15-131.w82-127.abo.wanadoo.fr [82.127.94.131]) by mwinf0303.wanadoo.fr (SMTP Server) with ESMTP id 2D16C1C003D9; Mon, 22 Aug 2005 07:38:16 +0200 (CEST) X-ME-UUID: 20050822053816184.2D16C1C003D9@mwinf0303.wanadoo.fr Received: from [192.168.42.2] (daneel.nbux.com [192.168.42.2]) by daneel.nbux.com (Postfix) with ESMTP id 980A41C489D; Mon, 22 Aug 2005 07:38:15 +0200 (CEST) Message-ID: <430964C7.8060103@nbux.com> Date: Mon, 22 Aug 2005 07:38:15 +0200 From: Christophe Yayon Organization: nbux.com User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexey Vesnin References: <004301c5a6d5$811662e0$260210ac@win> In-Reply-To: <004301c5a6d5$811662e0$260210ac@win> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Daniel Eischen , freebsd-hackers@freebsd.org Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 05:38:18 -0000 Thank you very much Alexey for your help ! Just a little last question, how could i say to nagios to use it ? Do i need to recompile it (i suppose) but is there a configure param or a Makefile modification ? Sorry but i am not a developper... Thanks. Alexey Vesnin wrote: > ----- Original Message ----- > From: "Daniel Eischen" > To: "Christophe Yayon" > Cc: > Sent: Friday, August 19, 2005 11:03 PM > Subject: Re: nagios and freebsd threads issue : help please ... > > > >>On Fri, 19 Aug 2005, Christophe Yayon wrote: >> >> >>>Hi all >>> >>>You should know about freebsd and nagios 2.0b threads issues (100% cpu >>>use by a forked process, lost check result, some pause of nagios main >>>process in certains obscursives conditions...). >>> >>>Some Nagios developpers says that the problem is in FreeBSD and some >>>other says that the problem is in nagios pthreads implementation, here a >>>resume of our discussions : >> >>See > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=340959+344806+/usr/local/www/db/ > text/2005/freebsd-hackers/20050703.freebsd-hackers > >>-- >>DE >> >>_______________________________________________ >>freebsd-hackers@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > > > This is a common problem with more common salvation : use ports/devel/pth > library. It will solve this problem COMPLETELY AT ALL. I'm currently running > FreeBSD-4-STABLE build, upgradin' my kernel weekly and has no sign of such a > problem. Always remember the main benefit of OpenSource - source is just a > subject to work with... You may use defaults and they must work, but there's > no guarantee that this will work fine and 100%-fast for YOUR > hardware/software environment. Don't be shy to make modifications - > developers aren't the ones who must do all the job for you. It's up toy you > personally. > > Post Scriptum. 5.4 is not GOOD. It must be used ONLY if you don't have > another way. It's memory leak is horrible.... > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 06:58:57 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3E4816A420 for ; Mon, 22 Aug 2005 06:58:57 +0000 (GMT) (envelope-from kamalpr@yahoo.com) Received: from web52714.mail.yahoo.com (web52714.mail.yahoo.com [206.190.48.237]) by mx1.FreeBSD.org (Postfix) with SMTP id 1B01E43D48 for ; Mon, 22 Aug 2005 06:58:54 +0000 (GMT) (envelope-from kamalpr@yahoo.com) Received: (qmail 13782 invoked by uid 60001); 22 Aug 2005 06:58:54 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=bPLlTt5nyVo9qAYZjwEgdojT3w0g5/D4/YK9iqpNVuu/0ZGTUEnXd1NTEl/15FLVCSWTpQ/DvjpTPzgHTtatiy1c/ujBlv529l8Qym+EKfF+DZFawMLp/a2gf6u2gWbKTLzjc8cwmSdSPIBaf2PhhyNL1RLtf1YnvASSoCdNF+Y= ; Message-ID: <20050822065854.13780.qmail@web52714.mail.yahoo.com> Received: from [221.128.128.140] by web52714.mail.yahoo.com via HTTP; Sun, 21 Aug 2005 23:58:54 PDT Date: Sun, 21 Aug 2005 23:58:54 -0700 (PDT) From: "Kamal R. Prasad" To: Allan Fields , Mike Adewole In-Reply-To: <20050821215540.GC58723@afields.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-libh@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kamalp@acm.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 06:58:58 -0000 > > And here I thought you were talking about a desktop > for us vt220 fans. > There is already screen or emacs on that front. A GUI has more than what emacs provides. > What about twin > for example? > close to what they are doing. > What exactly is meant by a "console" desktop anyway > other than > something similar to early Windows that runs w/o > X11? > It presumes the resources are present on the same machine rather than across the network as envisaged by the athena project. > Can you also make a Unicode console for *BSD please? > ;) If they get to developing their own fonts -they might. regards -kamal ------------------------------------------------------------ Kamal R. Prasad UNIX systems consultant http://www.kamalprasad.com/ kamalp@acm.org In theory, there is no difference between theory and practice. In practice, there is. ------------------------------------------------------------ __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 07:00:37 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 779A816A431 for ; Mon, 22 Aug 2005 07:00:37 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD56B43D70 for ; Mon, 22 Aug 2005 07:00:22 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j7M6vh43041622; Mon, 22 Aug 2005 00:57:48 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 Aug 2005 00:57:50 -0600 (MDT) Message-Id: <20050822.005750.56564930.imp@bsdimp.com> To: hselasky@c2i.net From: "M. Warner Losh" In-Reply-To: <200508210235.17608.hselasky@c2i.net> References: <200508201230.37976.hselasky@c2i.net> <20050820.171238.122195775.imp@bsdimp.com> <200508210235.17608.hselasky@c2i.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.village.org [127.0.0.1]); Mon, 22 Aug 2005 00:57:48 -0600 (MDT) Cc: freebsd-hackers@freebsd.org Subject: Re: Parking disk drive heads X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 07:00:37 -0000 In message: <200508210235.17608.hselasky@c2i.net> Hans Petter Selasky writes: : On Sunday 21 August 2005 01:12, M. Warner Losh wrote: : > In message: <200508201230.37976.hselasky@c2i.net> : > : > Hans Petter Selasky writes: : > : On Saturday 20 August 2005 10:18, Mike Silbersack wrote: : > : > On Fri, 19 Aug 2005, Doug Ambrisko wrote: : > : > > Flash is nice but it has some issues. Atleast dropping it isn't one! : > : > > : > : > > Doug A. : > : > : > : > I'd be really happy if I could get a USB flash drive to last more than : > : > 8 months. Luckily, I started weekly backups after the first failure. : > : > That helped a lot when the second failure happened. : > : : > : Flash drives does usually not last more than 10000 writes, per bit, from : > : what I know. Probably you need some kind of special file-system that : > : moves the files around as the write quoute gets used up! Eventually the : > : size of the disk will reach zero, and you have to move the files : > : elsewhere :-) But this is probably off topic. : > : > Actually, 10,000 writes per bit is one or two orders of magnitude too : > low these days. It was more typical for the Linear Flash PCMCIA cards : > from 10 years ago. Today, typically flash devices are good for more : > like 100,000 or 500,000 writes per cell, and all the fobs you'd buy : > these days have built-in wear averaging. I've tried three times now : > to wear out a flash by writing an incrementing counter to a single : > location only to give up after weeks of hammering due to external : > factors (power failure, network failure, etc). : : Are you sure that the flash drive is not caching the writes in RAM? Yes. I'm 100% positive. These devices do not have RAM. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 07:00:38 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67F1816A422 for ; Mon, 22 Aug 2005 07:00:38 +0000 (GMT) (envelope-from misha@onet.ru) Received: from mail.onet.ru (mail.onet.ru [213.85.10.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6482D43D45 for ; Mon, 22 Aug 2005 07:00:37 +0000 (GMT) (envelope-from misha@onet.ru) Received: from mail.onet.ru (localhost [127.0.0.1]) by mail.onet.ru (Postfix) with ESMTP id A1FC245259 for ; Mon, 22 Aug 2005 11:00:34 +0400 (MSD) Received: by mail.onet.ru (Postfix, from userid 1003) id 7FF9045258; Mon, 22 Aug 2005 11:00:34 +0400 (MSD) Received: from [213.85.50.90] (pppoe-50-90.onet.ru [213.85.50.90]) by mail.onet.ru (Postfix) with ESMTP id 6F1334524A for ; Mon, 22 Aug 2005 11:00:30 +0400 (MSD) Message-ID: <4309780D.1070607@onet.ru> Date: Mon, 22 Aug 2005 11:00:29 +0400 From: Michael User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <43087A39.7000106@onet.ru> <20050821163830.D44147@fledge.watson.org> In-Reply-To: <20050821163830.D44147@fledge.watson.org> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.onet.ru X-Spam-Level: X-Spam-Status: No, score=-3.3 required=2.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.4 X-AV-Checked: ClamAV using ClamSMT Subject: Re: MAC Biba policy. High marked process can't write to high marked file. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 07:00:38 -0000 Robert Watson wrote: >> test: Permission denied. > > %setpmac biba/high echo 1 >> test # bah! > > Remember that the '>>' is evaluated in the parent shell context, not > the execution context set up by setpmac. Try doing "setpmac biba/high > csh" and see how that changes the results when you run the complete > command in that context? Yeah, seem it was just my misinterpretation of handbook, I really appreciate for help ;-) From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 07:21:00 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 966E216A41F; Mon, 22 Aug 2005 07:21:00 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0ABD43D55; Mon, 22 Aug 2005 07:20:59 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j7M7KA7k041796; Mon, 22 Aug 2005 01:20:10 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 Aug 2005 01:20:17 -0600 (MDT) Message-Id: <20050822.012017.22502074.imp@bsdimp.com> To: lists@nbux.com From: "M. Warner Losh" In-Reply-To: <43088841.4090709@nbux.com> References: <43088841.4090709@nbux.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.village.org [127.0.0.1]); Mon, 22 Aug 2005 01:20:10 -0600 (MDT) Cc: deischen@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 07:21:00 -0000 In message: <43088841.4090709@nbux.com> Christophe Yayon writes: : http://www.opengroup.org/onlinepubs/009695399/functions/pthread_atfork.html : : "It is suggested that programs that use fork() call an exec function : very soon afterwards in the child process, thus resetting all states. In : the meantime, only a short list of async-signal-safe library routines : are promised to be available." : : Note *suggested*. This is a recommendation to protect against a shoddy : pthread-implementation. The thread specifications rule that only the : thread calling fork() is duplicated, which initially leads to the : recommendation (other threads holding locks aren't around to release : them in the new execution context). Here's what nagios does after a fork: in base/util.c: (1) Become the process group leader by calling setpgid(0, 0); (2) something called set_all_macro_environemt_vars(TRUE). This calls snprintf a bunch, as well as set variables by saving them to malloced memory. This save is done with strcpy and strcat. setenv is then called to try to export them. memory is then freed with free(3). (3) All signal handlers are reset (4) The right part of the pipe is closed (5) sigalarm handler is created and an alarm set. (6) Checks to see if it executing an embedded perl script, then tries to execute it if so. This has the feel of being too much after the fork. (7) Calls popen on the command if not. (8) Reads the output of the command using fgets. (9) closes the other end of the pipe (10) unsets all env vars. (11) Calls _exit() in base/checks.c (1) set_all_macro_environment_vars(TRUE) (2) forks again (3) granchild: resets handler, setpgid, etc. if perl script, do embedded perl, otherwise popen. lots of read/write to pipe. likewise in base/commands.c fork is also called for similar things. There's other places that also call popen. So, if any of these things is an issue, and you can point to a posix things that says it is an issue, then I think that the problem can be resolved. Looks complicated to actually setup, but in my experience, popen + threads is asking for trouble. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 11:03:26 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB06016A41F for ; Mon, 22 Aug 2005 11:03:26 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D73CE43D96 for ; Mon, 22 Aug 2005 11:03:06 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j7MB2vWX008329; Mon, 22 Aug 2005 07:02:58 -0400 (EDT) Date: Mon, 22 Aug 2005 07:02:57 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "M. Warner Losh" In-Reply-To: <20050822.012017.22502074.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org, lists@nbux.com Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 11:03:27 -0000 On Mon, 22 Aug 2005, M. Warner Losh wrote: > In message: <43088841.4090709@nbux.com> > Christophe Yayon writes: > : http://www.opengroup.org/onlinepubs/009695399/functions/pthread_atfork.html > : > : "It is suggested that programs that use fork() call an exec function > : very soon afterwards in the child process, thus resetting all states. In > : the meantime, only a short list of async-signal-safe library routines > : are promised to be available." > : > : Note *suggested*. This is a recommendation to protect against a shoddy > : pthread-implementation. The thread specifications rule that only the > : thread calling fork() is duplicated, which initially leads to the > : recommendation (other threads holding locks aren't around to release > : them in the new execution context). > > Here's what nagios does after a fork: > > in base/util.c: > > (1) Become the process group leader by calling setpgid(0, 0); > (2) something called set_all_macro_environemt_vars(TRUE). > This calls snprintf a bunch, as well as set variables > by saving them to malloced memory. This save is done > with strcpy and strcat. setenv is then called to try to > export them. memory is then freed with free(3). > (3) All signal handlers are reset > (4) The right part of the pipe is closed > (5) sigalarm handler is created and an alarm set. > (6) Checks to see if it executing an embedded perl script, > then tries to execute it if so. This has the feel of > being too much after the fork. > (7) Calls popen on the command if not. > (8) Reads the output of the command using fgets. > (9) closes the other end of the pipe > (10) unsets all env vars. > (11) Calls _exit() > > > in base/checks.c > > (1) set_all_macro_environment_vars(TRUE) > (2) forks again > (3) granchild: > resets handler, setpgid, etc. > if perl script, do embedded perl, otherwise popen. > lots of read/write to pipe. > > likewise in base/commands.c fork is also called for similar > things. > > There's other places that also call popen. > > So, if any of these things is an issue, and you can point to a posix > things that says it is an issue, then I think that the problem can be > resolved. You can only execute async-signal-safe functions after a fork() from a threaded application. free(), malloc(), popen(), fgets(), are not async-signal-safe. The list of async-signal-safe functions are here: http://www.opengroup.org/onlinepubs/009695399/nframe.html The restriction on fork() is here (20th bullet down): http://www.opengroup.org/onlinepubs/009695399/nframe.html -- DE From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 11:36:45 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D8E116A41F for ; Mon, 22 Aug 2005 11:36:45 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id D37BC43D45 for ; Mon, 22 Aug 2005 11:36:44 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A6C92.dip.t-dialin.net [84.154.108.146]) (authenticated bits=0) by tower.berklix.org (8.12.9p2/8.12.9) with ESMTP id j7MBaexr084791; Mon, 22 Aug 2005 13:36:41 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id j7MBaciC002023; Mon, 22 Aug 2005 13:36:38 +0200 (CEST) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id j7MBb2pu049495; Mon, 22 Aug 2005 13:37:02 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200508221137.j7MBb2pu049495@fire.jhs.private> To: Peter Jeremy In-Reply-To: Message from Peter Jeremy of "Mon, 22 Aug 2005 14:36:47 +1000." <20050822043647.GB37107@cirb503493.alcatel.com.au> Date: Mon, 22 Aug 2005 13:37:02 +0200 From: "Julian H. Stacey" Cc: hackers@freebsd.org Subject: Re: Locating obsolete ports distfiles X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 11:36:45 -0000 Peter Jeremy wrote: > I currently have just over 8GB is /usr/ports/distfiles. Some of these > files are more than 10 years old and long obsolete. > Does anyone have > any suggestions on how to identify which files are no longer referenced > by current ports? > > Doing a 'make checksum' on every installed port and then looking at > the atimes is one approach but this doesn't handle: > - ports that I don't currently have installed but might need > - ports installed on systems that mount /usr/ports readonly I have 22 Gig, but none so long unused. I run numerous machines with different releases, & dump distfiles belonging only to some old release each time I've upgraded the last old host, I sub divide distfiles by release, like this: Periodicly (eg for new relases) I move my distfiles to a directory named by release, & add the new directory name to a fetch list in make.conf, eg http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/jhs/etc/make.conf & run cd /usr/ports ; make fetch BATCH=YES ; make fetch INTERACTIVE=yes I strip fetched duplicates with my http://berklix.com/~jhs/bin/.sh/distfiles_cmpd http://berklix.com/~jhs/src/bsd/jhs/bin/public/cmpd/ Advantages: Lowered paranoia :-) Never deleted all distfiles. Easier to copy release related stuff to laptops about to lose net connectivity. Disadvantages: Slow. Would also need lots of space temporarily, except I run distfiles_cmpd in a while loop, parallel to the fetch. Not a `standard solution'. -- Julian Stacey Consultant Systems Engineer, Munich. http://berklix.com Mail in Ascii (Html = Spam). Ihr Rauch = mein allergischer Kopfschmerz. From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 12:06:51 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1FF316A420 for ; Mon, 22 Aug 2005 12:06:51 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2283743D45 for ; Mon, 22 Aug 2005 12:06:50 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 3EC66617E; Mon, 22 Aug 2005 14:06:34 +0200 (CEST) Received: from xps.des.no (des.no [80.203.228.37]) by tim.des.no (Postfix) with ESMTP id 2D89E6147; Mon, 22 Aug 2005 14:06:34 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 7D4FF33D44; Mon, 22 Aug 2005 14:06:45 +0200 (CEST) To: Divacky Roman References: <20050821094849.GA79907@stud.fit.vutbr.cz> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Mon, 22 Aug 2005 14:06:45 +0200 In-Reply-To: <20050821094849.GA79907@stud.fit.vutbr.cz> (Divacky Roman's message of "Sun, 21 Aug 2005 11:48:49 +0200") Message-ID: <86slx25g6i.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Tests: ALL_TRUSTED,AWL,BAYES_00 X-Spam-Learn: ham X-Spam-Score: -5.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on tim.des.no Cc: hackers@freebsd.org Subject: Re: number of simultanously opened files X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 12:06:51 -0000 Divacky Roman writes: > witten ~# sysctl kern.maxfiles=3D100000 > kern.maxfiles: 100000 -> 100000 > witten ~# sysctl kern.maxfilesperproc=3D100000 > kern.maxfilesperproc: 100000 -> 100000 > witten ~# > > but I still cannot open more than 7319 files simultaneously. pls can > you tell me why? man ulimit DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 08:08:41 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 60F8916A41F for ; Mon, 22 Aug 2005 08:08:41 +0000 (GMT) (envelope-from m.ehinger@ltur.de) Received: from posty.gateway-inter.net (posty.gateway-inter.net [213.144.19.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF7443D45 for ; Mon, 22 Aug 2005 08:08:40 +0000 (GMT) (envelope-from m.ehinger@ltur.de) To: freebsd-hackers@freebsd.org Message-ID: From: m.ehinger@ltur.de Date: Mon, 22 Aug 2005 10:08:01 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Mailman-Approved-At: Mon, 22 Aug 2005 12:08:33 +0000 Subject: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 08:08:41 -0000 Hi, what would be the best approach to implement aps on FreeBSD? I got an Accelerometer driver which will deliver data. First Version is available at https://sourceforge.net/project/showfiles.php?group_id=138242&package_id=160977 We have to poll the device for information quiet often to detect a possible shock early enough to park disk drive heads. What else must be done to prevent a possible data loss? There is also an discussion about that concerning linux. http://sourceforge.net/mailarchive/forum.php?forum=hdaps-devel Would an daemon be sufficient for that? Reaction time? What about an kernel thread? Other solutions? thanks in advance Maik From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 14:03:43 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A25716A41F for ; Mon, 22 Aug 2005 14:03:43 +0000 (GMT) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id B292543D58 for ; Mon, 22 Aug 2005 14:03:41 +0000 (GMT) (envelope-from fli+freebsd-hackers@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id C4E421A741; Mon, 22 Aug 2005 16:03:38 +0200 (CEST) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (manticore.shapeshifter.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10388-18; Mon, 22 Aug 2005 16:03:37 +0200 (CEST) Received: from [192.168.0.100] (h4n2fls31o270.telia.com [217.208.199.4]) by mx1.h3q.net (Postfix) with ESMTP id EF15C1A73F; Mon, 22 Aug 2005 16:03:36 +0200 (CEST) Message-ID: <4309DB36.2090203@shapeshifter.se> Date: Mon, 22 Aug 2005 16:03:34 +0200 From: Fredrik Lindberg User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050816) X-Accept-Language: en-us, en MIME-Version: 1.0 To: m.ehinger@ltur.de References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: at mail.hamnpolare.net Cc: freebsd-hackers@freebsd.org Subject: Re: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 14:03:43 -0000 m.ehinger@ltur.de wrote: > Hi, > > what would be the best approach to implement aps on FreeBSD? > > I got an Accelerometer driver which will deliver data. First Version is available at > https://sourceforge.net/project/showfiles.php?group_id=138242&package_id=160977 > > We have to poll the device for information quiet often to detect a possible shock early enough to park disk drive heads. > What else must be done to prevent a possible data loss? > > There is also an discussion about that concerning linux. > http://sourceforge.net/mailarchive/forum.php?forum=hdaps-devel > > > Would an daemon be sufficient for that? Reaction time? What about an kernel thread? > > Other solutions? > > thanks in advance > > Maik > This is just some wild ideas... 1) Keeping everything inside the kernel. Will yield fast response time, it will be able to park the head but nothing else. All policy decisions will have to be made through sysctl(3) or similar interface. 2) Let the kernel do all the polling and send asynchronous events through devctl(4). A userland daemon (running mlock(2)ed) catches these events and parks the head (and possibly other actions aswell). A threshold setting could be avaiable through sysctl(3) so that only potential dangerous values are reported to the userland daemon. The biggest problem is probably that devctl(4) only can have one reader, which at the moment is devd(8). If devd is swapped out the response time would suffer, which means that devd must run mlock'ed too?. 3) A userland daemon does the polling. Not sure about the response time, but there will be alot of data transfer between the kernel and userland which usually is expensive. Fredrik Lindberg From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 14:11:55 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3282416A420; Mon, 22 Aug 2005 14:11:55 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 748D443D48; Mon, 22 Aug 2005 14:11:54 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j7ME9V7s048738; Mon, 22 Aug 2005 08:09:31 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 Aug 2005 08:09:38 -0600 (MDT) Message-Id: <20050822.080938.95905450.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <20050822.012017.22502074.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.village.org [127.0.0.1]); Mon, 22 Aug 2005 08:09:31 -0600 (MDT) Cc: freebsd-hackers@freebsd.org, lists@nbux.com Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 14:11:55 -0000 So there's something in the list, I've gone through and done a call tree analysis to show the extensive and pervastive nature of the functions that nagios calls after fork. I don't know if these are all problems or not, since I don't know if some of these functions might be called before the first thread is created with pthread_create. However, any that are called after that clearly have undefined behavior. In message: Daniel Eischen writes: : > So, if any of these things is an issue, and you can point to a posix : > things that says it is an issue, then I think that the problem can be : > resolved. : : You can only execute async-signal-safe functions after a fork() : from a threaded application. free(), malloc(), popen(), fgets(), : are not async-signal-safe. The list of async-signal-safe functions : are here: : : http://www.opengroup.org/onlinepubs/009695399/nframe.html This can really be found at: http://www.opengroup.org/onlinepubs/009695399/functions/chap02_04.html The following table defines a set of functions that shall be either reentrant or non-interruptible by signals and shall be async-signal-safe. Therefore applications may invoke them, without restriction, from signal-catching functions: _Exit, _exit, abort, accept, access, aio_error, aio_return, aio_suspend, alarm, bind, cfgetispeed, cfgetospeed, cfsetispeed, cfsetospeed, chdir, chmod, chown, clock_gettime, close, connect, creat, dup, dup2, execle, execve, fchmod, fchown, fcntl, fdatasync, fork, fpathconf, fstat, fsync, ftruncate, getegid, geteuid, getgid, getgroups, getpeername, getpgrp, getpid, getppid, getsockname, getsockopt, getuid, kill, link, listen, lseek, lstat, mkdir, mkfifo, open, pathconf, pause, pipe, poll, posix_trace_event, pselect, raise, read, readlink, recv, recvfrom, recvmsg, rename, rmdir, select, sem_post, send, sendmsg, sendto, setgid, setpgid, setsid, setsockopt, setuid, shutdown, sigaction, sigaddset, sigdelset, sigemptyset, sigfillset, sigismember, sleep, signal, sigpause, sigpending, sigprocmask, sigqueue, sigset, sigsuspend, sockatmark, socket, socketpair, stat, symlink, sysconf, tcdrain, tcflow, tcflush, tcgetattr, tcgetpgrp, tcsendbreak, tcsetattr, tcsetpgrp, time, timer_getoverrun, timer_gettime, timer_settime, times, umask, uname, unlink, utime, wait, waitpid, write [[Note, I reformatted the above ]]. : The restriction on fork() is here (20th bullet down): : : http://www.opengroup.org/onlinepubs/009695399/nframe.html http://www.opengroup.org/onlinepubs/009695399/functions/fork.html # A process shall be created with a single thread. If a multi-threaded process calls fork(), the new process shall contain a replica of the calling thread and its entire address space, possibly including the states of mutexes and other resources. Consequently, to avoid errors, the child process may only execute async-signal-safe operations until such time as one of the exec functions is called. [THR] [Option Start] Fork handlers may be established by means of the pthread_atfork() function in order to maintain application invariants across fork() calls. [Option End] When the application calls fork() from a signal handler and any of the fork handlers registered by pthread_atfork() calls a function that is not asynch-signal-safe, the behavior is undefined. Later, in the informative section, we have: When a programmer is writing a multi-threaded program, the first described use of fork(), creating new threads in the same program, is provided by the pthread_create() function. The fork() function is thus used only to run new programs, and the effects of calling functions that require certain resources between the call to fork() and the call to an exec function are undefined. Note, the 'certain resources' here means non-async-signal-safe functions. This means that the following functions that nagios calls are unsafe: In set_macro_environment_var: malloc, strcpy, strcat, setenv, unsetenv, free In set_argv_macro_environment: snprintf In free_memory (only used in the USE_MEMORY_PERFORMANCE_TWEAKS): free In my_system: alarm, (in the EMBEDDEDPERL case: anything that perl can call, strncpy, printf) popen, strcpy, fgets, functions called by set_macro_environment_var, set_argv_macro_environment, free_memory In daemon_init: snprintf, getrlimit, setrlimit, sprintf and anything else that's done as part of the daemon after daemon_init (I didn't do a call graph analysis on this). write_to_logs_and_console cleanup broker_program_state write_to_logs_and_console: strlen, write_to_all_logs, write_to_console write_to_log fopen, fprintf, fclose write_to_console write_to_syslog write_to_all_logs write_to_syslog, write_to_log write_to_syslog syslog (in the DEBUG0 defined case: printf for nearly all functions) From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 14:34:12 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9604F16A41F for ; Mon, 22 Aug 2005 14:34:12 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5479843D48 for ; Mon, 22 Aug 2005 14:34:10 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from stealth.local (pcp09741457pcs.goosck01.sc.comcast.net [69.241.83.8]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id j7MEY7sh085875; Mon, 22 Aug 2005 07:34:09 -0700 (PDT) (envelope-from lists@jnielsen.net) From: John Nielsen To: freebsd-hackers@freebsd.org Date: Mon, 22 Aug 2005 10:34:01 -0400 User-Agent: KMail/1.8.1 References: <20050822043647.GB37107@cirb503493.alcatel.com.au> <17161.22518.896293.529642@bhuda.mired.org> In-Reply-To: <17161.22518.896293.529642@bhuda.mired.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508221034.01620.lists@jnielsen.net> X-Virus-Scanned: ClamAV 0.85.1/1035/Mon Aug 22 04:37:18 2005 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Peter Jeremy Subject: Re: Locating obsolete ports distfiles X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 14:34:12 -0000 On Monday 22 August 2005 12:43 am, Mike Meyer wrote: > In <20050822043647.GB37107@cirb503493.alcatel.com.au>, Peter Jeremy typed: > > I currently have just over 8GB is /usr/ports/distfiles. Some of these > > files are more than 10 years old and long obsolete. Does anyone have > > any suggestions on how to identify which files are no longer referenced > > by current ports? > > > > Doing a 'make checksum' on every installed port and then looking at > > the atimes is one approach but this doesn't handle: > > - ports that I don't currently have installed but might need > > - ports installed on systems that mount /usr/ports readonly > > Install sysutils/portupgrade, and do a "portsclean -D". That will > remove all the distfiles that aren't referenced by any port in the > tree. Do "portsclean -DD" and it'll remove all distfiles not used by > an installed port. Alternatively there is the distclean.sh script in ports/Tools/scripts. Run it with the -f switch to delete outdated distfiles without confirmation. JN From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 15:00:04 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 482E816A41F for ; Mon, 22 Aug 2005 15:00:04 +0000 (GMT) (envelope-from lists@nbux.com) Received: from smtp6.wanadoo.fr (smtp6.wanadoo.fr [193.252.22.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2690E43D5C for ; Mon, 22 Aug 2005 14:59:58 +0000 (GMT) (envelope-from lists@nbux.com) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0612.wanadoo.fr (SMTP Server) with ESMTP id 70BBE1C00151 for ; Mon, 22 Aug 2005 16:59:57 +0200 (CEST) Received: from daneel.nbux.com (LNeuilly-152-22-15-131.w82-127.abo.wanadoo.fr [82.127.94.131]) by mwinf0612.wanadoo.fr (SMTP Server) with ESMTP id 28A3F1C00137; Mon, 22 Aug 2005 16:59:56 +0200 (CEST) X-ME-UUID: 20050822145957166.28A3F1C00137@mwinf0612.wanadoo.fr Received: from webmail.nbux.com (daneel.nbux.com [192.168.42.2]) by daneel.nbux.com (Postfix) with ESMTP id 10D4A1C4C89; Mon, 22 Aug 2005 16:59:56 +0200 (CEST) Received: from 194.51.215.62 (SquirrelMail authenticated user lists) by webmail.nbux.com with HTTP; Mon, 22 Aug 2005 16:59:56 +0200 (CEST) Message-ID: <40176.194.51.215.62.1124722796.squirrel@webmail.nbux.com> In-Reply-To: <20050822.080938.95905450.imp@bsdimp.com> References: <20050822.012017.22502074.imp@bsdimp.com> <20050822.080938.95905450.imp@bsdimp.com> Date: Mon, 22 Aug 2005 16:59:56 +0200 (CEST) From: "Christophe Yayon" To: "M. Warner Losh" User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: deischen@freebsd.org, freebsd-hackers@freebsd.org, lists@nbux.com Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 15:00:04 -0000 Very good analysis ! In conclusion, it's clear that there bad functions calls in Nagios, i think i will copy/paste some lines from these mails and resume them to nagios-devel mailling list, i hope it will help nagios developper... Are you all ok for this ? > So there's something in the list, I've gone through and done a call > tree analysis to show the extensive and pervastive nature of the > functions that nagios calls after fork. I don't know if these are all > problems or not, since I don't know if some of these functions might > be called before the first thread is created with pthread_create. > However, any that are called after that clearly have undefined > behavior. > > In message: > Daniel Eischen writes: > : > So, if any of these things is an issue, and you can point to a posix > : > things that says it is an issue, then I think that the problem can be > : > resolved. > : > : You can only execute async-signal-safe functions after a fork() > : from a threaded application. free(), malloc(), popen(), fgets(), > : are not async-signal-safe. The list of async-signal-safe functions > : are here: > : > : http://www.opengroup.org/onlinepubs/009695399/nframe.html > > This can really be found at: > http://www.opengroup.org/onlinepubs/009695399/functions/chap02_04.html > > > The following table defines a set of functions that shall be either > reentrant or non-interruptible by signals and shall be > async-signal-safe. Therefore applications may invoke them, without > restriction, from signal-catching functions: > > _Exit, _exit, abort, accept, access, aio_error, aio_return, > aio_suspend, alarm, bind, cfgetispeed, cfgetospeed, cfsetispeed, > cfsetospeed, chdir, chmod, chown, clock_gettime, close, connect, > creat, dup, dup2, execle, execve, fchmod, fchown, fcntl, fdatasync, > fork, fpathconf, fstat, fsync, ftruncate, getegid, geteuid, getgid, > getgroups, getpeername, getpgrp, getpid, getppid, getsockname, > getsockopt, getuid, kill, link, listen, lseek, lstat, mkdir, mkfifo, > open, pathconf, pause, pipe, poll, posix_trace_event, pselect, raise, > read, readlink, recv, recvfrom, recvmsg, rename, rmdir, select, > sem_post, send, sendmsg, sendto, setgid, setpgid, setsid, setsockopt, > setuid, shutdown, sigaction, sigaddset, sigdelset, sigemptyset, > sigfillset, sigismember, sleep, signal, sigpause, sigpending, > sigprocmask, sigqueue, sigset, sigsuspend, sockatmark, socket, > socketpair, stat, symlink, sysconf, tcdrain, tcflow, tcflush, > tcgetattr, tcgetpgrp, tcsendbreak, tcsetattr, tcsetpgrp, time, > timer_getoverrun, timer_gettime, timer_settime, times, umask, uname, > unlink, utime, wait, waitpid, write > > [[Note, I reformatted the above ]]. > > : The restriction on fork() is here (20th bullet down): > : > : http://www.opengroup.org/onlinepubs/009695399/nframe.html > > http://www.opengroup.org/onlinepubs/009695399/functions/fork.html > > # A process shall be created with a single thread. If a multi-threaded > process calls fork(), the new process shall contain a replica of the > calling thread and its entire address space, possibly including the > states of mutexes and other resources. Consequently, to avoid > errors, the child process may only execute async-signal-safe > operations until such time as one of the exec functions is > called. [THR] [Option Start] Fork handlers may be established by > means of the pthread_atfork() function in order to maintain > application invariants across fork() calls. [Option End] > > When the application calls fork() from a signal handler and any of > the fork handlers registered by pthread_atfork() calls a function that > is not asynch-signal-safe, the behavior is undefined. > > Later, in the informative section, we have: > > When a programmer is writing a multi-threaded program, the first > described use of fork(), creating new threads in the same program, > is provided by the pthread_create() function. The fork() function is > thus used only to run new programs, and the effects of calling > functions that require certain resources between the call to fork() > and the call to an exec function are undefined. > > Note, the 'certain resources' here means non-async-signal-safe > functions. > > This means that the following functions that nagios calls are unsafe: > > In set_macro_environment_var: > malloc, strcpy, strcat, setenv, unsetenv, free > In set_argv_macro_environment: > snprintf > In free_memory (only used in the USE_MEMORY_PERFORMANCE_TWEAKS): > free > > In my_system: > alarm, > (in the EMBEDDEDPERL case: > anything that perl can call, > strncpy, > printf) > popen, > strcpy, > fgets, > functions called by set_macro_environment_var, > set_argv_macro_environment, free_memory > > In daemon_init: > snprintf, getrlimit, setrlimit, sprintf and anything else > that's done as part of the daemon after daemon_init (I didn't > do a call graph analysis on this). > write_to_logs_and_console > cleanup > broker_program_state > > write_to_logs_and_console: > strlen, write_to_all_logs, write_to_console > > write_to_log > fopen, fprintf, fclose > > write_to_console > write_to_syslog > > write_to_all_logs > write_to_syslog, write_to_log > > write_to_syslog > syslog > > (in the DEBUG0 defined case: printf for nearly all functions) > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 15:26:25 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D65F16A41F for ; Mon, 22 Aug 2005 15:26:25 +0000 (GMT) (envelope-from sos@FreeBSD.org) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id B12B343D58 for ; Mon, 22 Aug 2005 15:26:24 +0000 (GMT) (envelope-from sos@FreeBSD.org) Received: from [194.192.25.136] (mac.deepcore.dk [194.192.25.136]) by spider.deepcore.dk (8.13.3/8.13.3) with ESMTP id j7MFO301078859; Mon, 22 Aug 2005 17:24:03 +0200 (CEST) (envelope-from sos@FreeBSD.org) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Date: Mon, 22 Aug 2005 17:26:17 +0200 To: m.ehinger@ltur.de X-Mailer: Apple Mail (2.734) X-mail-scanned: by DeepCore Virus & Spam killer v1.12 Cc: freebsd-hackers@FreeBSD.org Subject: Re: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 15:26:25 -0000 On 22/08/2005, at 10:08, m.ehinger@ltur.de wrote: > what would be the best approach to implement aps on FreeBSD? > > I got an Accelerometer driver which will deliver data. First =20 > Version is available at > https://sourceforge.net/project/showfiles.php?=20 > group_id=3D138242&package_id=3D160977 > > We have to poll the device for information quiet often to detect a =20 > possible shock early enough to park disk drive heads. Urhm, what type of "accidents" is it we want to protect against here ? It will take several tens of mS to get the heads parked if not =20 hundreds, and the worst case scenario would be that the "accident" =20 will happen just as the heads are on the way to the parking zone =20 which would *really* destroy data on there, unless the disk has =20 special HW to just quickly lift the heads or something. > What else must be done to prevent a possible data loss? I think this will need to be tailored to the exact type of "mishap" =20 one wants to protect against. If this is a way to protect against dropping a notebook on the floor =20 then there won't be time for much else than trying to rush the heads =20 to the parking zone. In other setups a flush of buffers (OS level as well as HW level) =20 could be preferred if power loss or HW failure was imminent. - S=F8ren From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 15:36:26 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74ED016A41F for ; Mon, 22 Aug 2005 15:36:26 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1679D43D48 for ; Mon, 22 Aug 2005 15:36:25 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.4/8.13.4/NETPLEX) with ESMTP id j7MFaNLr015006; Mon, 22 Aug 2005 11:36:23 -0400 (EDT) Date: Mon, 22 Aug 2005 11:36:23 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: "M. Warner Losh" In-Reply-To: <20050822.080938.95905450.imp@bsdimp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-hackers@freebsd.org, lists@nbux.com Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 15:36:26 -0000 On Mon, 22 Aug 2005, M. Warner Losh wrote: > So there's something in the list, I've gone through and done a call > tree analysis to show the extensive and pervastive nature of the > functions that nagios calls after fork. I don't know if these are all > problems or not, since I don't know if some of these functions might > be called before the first thread is created with pthread_create. > However, any that are called after that clearly have undefined > behavior. Note that we (David Xu and myself) took a different approach to handling fork() in libpthread (and probably libthr) than was done in libc_r. We thought it better not to try and reinitialize libpthread (and to some extent libc) because it is messy and to expose non-portable applications. -- DE From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 15:47:47 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E020D16A41F; Mon, 22 Aug 2005 15:47:47 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id C721243D49; Mon, 22 Aug 2005 15:47:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j7MFlJGP049809; Mon, 22 Aug 2005 09:47:19 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 Aug 2005 09:47:27 -0600 (MDT) Message-Id: <20050822.094727.48529585.imp@bsdimp.com> To: lists@nbux.com From: "M. Warner Losh" In-Reply-To: <40176.194.51.215.62.1124722796.squirrel@webmail.nbux.com> References: <20050822.080938.95905450.imp@bsdimp.com> <40176.194.51.215.62.1124722796.squirrel@webmail.nbux.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.village.org [127.0.0.1]); Mon, 22 Aug 2005 09:47:20 -0600 (MDT) Cc: deischen@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 15:47:48 -0000 In message: <40176.194.51.215.62.1124722796.squirrel@webmail.nbux.com> "Christophe Yayon" writes: : Very good analysis ! : In conclusion, it's clear that there bad functions calls in Nagios, : i think i will copy/paste some lines from these mails and resume them to : nagios-devel mailling list, i hope it will help nagios developper... : : Are you all ok for this ? Please do try to do so in a sensitive manner. Otherwise, sure. I'm just tired of someone bad talking an implementation as being non-compliant when, in fact, it is compliant. Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 15:47:56 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C515E16A43E; Mon, 22 Aug 2005 15:47:56 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F00B43D62; Mon, 22 Aug 2005 15:47:54 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j7MFjvBY049786; Mon, 22 Aug 2005 09:45:58 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 Aug 2005 09:46:04 -0600 (MDT) Message-Id: <20050822.094604.112623156.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <20050822.080938.95905450.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.village.org [127.0.0.1]); Mon, 22 Aug 2005 09:45:58 -0600 (MDT) Cc: freebsd-hackers@freebsd.org, lists@nbux.com Subject: Re: nagios and freebsd threads issue : help please ... X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 15:47:56 -0000 In message: Daniel Eischen writes: : On Mon, 22 Aug 2005, M. Warner Losh wrote: : : > So there's something in the list, I've gone through and done a call : > tree analysis to show the extensive and pervastive nature of the : > functions that nagios calls after fork. I don't know if these are all : > problems or not, since I don't know if some of these functions might : > be called before the first thread is created with pthread_create. : > However, any that are called after that clearly have undefined : > behavior. : : Note that we (David Xu and myself) took a different approach : to handling fork() in libpthread (and probably libthr) than : was done in libc_r. We thought it better not to try and : reinitialize libpthread (and to some extent libc) because : it is messy and to expose non-portable applications. Is there some way to flip a switch and get an abort in all the non-async-safe-safe functions in libc :-) Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 15:55:47 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0449916A420; Mon, 22 Aug 2005 15:55:47 +0000 (GMT) (envelope-from borjamar@sarenet.es) Received: from sollube.sarenet.es (mx1.sarenet.es [194.30.0.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 962B343D46; Mon, 22 Aug 2005 15:55:46 +0000 (GMT) (envelope-from borjamar@sarenet.es) Received: from [127.0.0.1] (borja.sarenet.es [192.148.167.77]) by sollube.sarenet.es (Postfix) with ESMTP id E2A25DF3; Mon, 22 Aug 2005 17:55:44 +0200 (CEST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5FFDC44D-F094-4856-8FAC-4D14EB77B47A@sarenet.es> Content-Transfer-Encoding: 7bit From: Borja Marcos Date: Mon, 22 Aug 2005 17:55:42 +0200 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= X-Mailer: Apple Mail (2.734) Cc: freebsd-hackers@freebsd.org Subject: Re: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 15:55:47 -0000 > I think this will need to be tailored to the exact type of "mishap" > one wants to protect against. I think that the main purpose of the shock detection system is to allow data to be recovered from the disk in case the laptop is broken. By parking the heads asap you can avoid damaging the plates with the head. At least that's what I read. The disk won't be necessary usable after being dropped, but at least the plates should be readable. In that case, priority number one would be a fast parking of the head. However, it could lead to a worst-case data loss with softupdates and the disk cache, isn't it? Borja. From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 17:07:16 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C80F816A41F for ; Mon, 22 Aug 2005 17:07:16 +0000 (GMT) (envelope-from thib@mi.is) Received: from quasar.skima.is (quasar.skima.is [212.30.200.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9885243D58 for ; Mon, 22 Aug 2005 17:07:15 +0000 (GMT) (envelope-from thib@mi.is) Received: from caulfield ([85.220.68.246] [85.220.68.246]) by quasar.skima.is; Mon, 22 Aug 2005 17:07:14 Z Date: Mon, 22 Aug 2005 17:07:14 +0000 From: "Thordur I. Bjornsson" To: freebsd-hackers@freebsd.org Message-Id: <20050822170714.4365a92b.thib@mi.is> In-Reply-To: <20050821231247.567b9c2f.thib@mi.is> References: <20050821231247.567b9c2f.thib@mi.is> Organization: n/a X-Mailer: Sylpheed version 1.0.5 (GTK+ 1.2.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart=_Mon__22_Aug_2005_17_07_14_+0000_K4GvqVSDZGI2uQ_A" Subject: Re: xl driver proplem. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 17:07:16 -0000 This is a multi-part message in MIME format. --Multipart=_Mon__22_Aug_2005_17_07_14_+0000_K4GvqVSDZGI2uQ_A Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit *snip* > Hello list. > > I had this proplem with the xl driver: *snip* Hello list (again). I'm sorry for the noize last night. I was way to sleepy ;) Now I had this proplem with a non-sleepable lock in if_xl.c (As explained in the previous post. Now, I did not provide alot of info in my last mail so here goes: FreeBSD caulfield.bitcode.eu.org 6.0-BETA2 FreeBSD 6.0-BETA2 #0: Sun Aug 21 22:21:18 UTC 2005 thib@caulfield.bitcode.eu.org:/usr/obj/usr/src.inuse/sys/caulfield i386 This is built from sources from around noon on Sunday. This proplem exist in -HEAD since there have been no changes in if_xl.c Now this morning I made myself a null-modem cable and went on to see what was scrolling by so fast because of this "bug". Attached is a log from the serial connection when I reboot the machine. This proplem "went away (TM)" also with my diff. Now I have been doing some further testing on the NIC and everything seems to be OK. PS: I though about CC'ing this to current also but... Am I going through the wrong channels here ? -- Thordur I. Humppa! --Multipart=_Mon__22_Aug_2005_17_07_14_+0000_K4GvqVSDZGI2uQ_A Content-Type: text/plain; name="reboot.txt" Content-Disposition: attachment; filename="reboot.txt" Content-Transfer-Encoding: 7bit Mon Aug 22 16:49:32 UTC 2005 AWaiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...3 1 1 1 0 0 done All buffers synced. unmount of /dev failed (BUSY) lock order reversal 1st 0xc258c3ac vnode interlock (vnode interlock) @ /usr/src/sys/kern/vfs_subr.c:2373 2nd 0xc1043144 system map (system map) @ /usr/src/sys/vm/vm_kern.c:295 KDB: stack backtrace: witness_checkorder(c1043144,9,c072fc08,127,c0572615) at witness_checkorder+0x406 _mtx_lock_flags(c1043144,0,c072fc08,127,c104e460) at _mtx_lock_flags+0x54 _vm_map_lock(c10430c0,c072fc08,127,8,c104e468) at _vm_map_lock+0x37 kmem_malloc(c10430c0,1000,101,101,8) at kmem_malloc+0x3a slab_zalloc(0,c071fc85,33b,c2392600,c2392678) at slab_zalloc+0x7d uma_zone_slab(c104e468,8,c072eec1,8ab,0) at uma_zone_slab+0xa6 uma_zalloc_internal(1,0,0,c104dc48,ed0baa78) at uma_zalloc_internal+0x3e bucket_alloc(c10290a8,0,c072eec1,967,c10290a0) at bucket_alloc+0x29 uma_zfree_arg(c104dc00,c25667bc,0,ed0baa9c,c0644508) at uma_zfree_arg+0x2c5 mac_labelzone_free(c25667bc,c258c330,ed0baab8,c05b1d0b,c258c330) at mac_labelzone_free+0x22 mac_destroy_vnode(c258c330,0,c07252ec,2d6,c258c330) at mac_destroy_vnode+0x18 vdropl(c0748b00,ed0baae0,c07252ec,8ad,c2533844) at vdropl+0x121 vflush(c2533800,0,2,c2392600,c071ba1f) at vflush+0x446 ffs_flushfiles(c2533800,2,c2392600,c2560a00,0) at ffs_flushfiles+0x80 ffs_unmount(c2533800,80000,c2392600,c2392600,0) at ffs_unmount+0x425 dounmount(c2533800,80000,c2392600,d6323f08,0) at dounmount+0x1d4 vfs_unmountall(d63240b0,0,c071c6e3,10c,267) at vfs_unmountall+0x45 boot(c0779e00,8,c071c6e3,a1,bfbfed10) at boot+0x773 poweroff_wait(c2392600,ed0bad04,4,422,1) at poweroff_wait syscall(3b,3b,3b,0,1) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (55, FreeBSD ELF32, reboot), eip = 0x280b33af, esp = 0xbfbfed0c, ebp = 0xbfbfed58 --- Uptime: 29s taskqueue_drain with the following non-sleepable locks held: exclusive sleep mutex xl0 (network driver) r = 0 (0xc23a80a4) locked @ /usr/src/sys/pci/if_xl.c:3350 KDB: stack backtrace: witness_warn(2,0,c071f440,c7fa80ff,1b) at witness_warn+0x5d6 taskqueue_drain(c226f800,c23a80c8,c072a962,cc7,c2394400) at taskqueue_drain+0x2e xl_stop(c23a80a4,8,c072a962,d16,c23a3400) at xl_stop+0x56 xl_shutdown(c23a3400,c23a3500,ed0babb8,c056136a,c23a3500) at xl_shutdown+0x4d bus_generic_shutdown(c23a3500,c2353d00,ed0babc8,c056136a,c2353d00) at bus_generic_shutdown+0x17 bus_generic_shutdown(c2353d00,c2353b80,ed0babd8,c056136a,c2353b80) at bus_generic_shutdown+0x17 bus_generic_shutdown(c2353b80,c22d0a00,ed0babe8,c056136a,c22d0a00) at bus_generic_shutdown+0x17 bus_generic_shutdown(c22d0a00,c226f600,ed0bac00,c08a2adc,c226f600) at bus_generic_shutdown+0x17 bus_generic_shutdown(c226f600,1,c08bdf2d,2a2,ed0bac10) at bus_generic_shutdown+0x17 acpi_shutdown(c226f600,c226fd00,ed0bac20,c056136a,c226fd00) at acpi_shutdown+0x35 bus_generic_shutdown(c226fd00,c225a480,ed0bac40,c05622bb,c22d0000) at bus_generic_shutdown+0x17 bus_generic_shutdown(c22d0000,102,c0777620,c225a4c0,c225e000) at bus_generic_shutdown+0x17 root_bus_module_handler(c225a480,2,0,c22573a0,ed0bacb0) at root_bus_module_handler+0x23 module_shutdown(0,0,c071c6e3,190,267) at module_shutdown+0x4c boot(c0779e00,8,c071c6e3,a1,bfbfed10) at boot+0x3a2 poweroff_wait(c2392600,ed0bad04,4,422,1) at poweroff_wait syscall(3b,3b,3b,0,1) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (55, FreeBSD ELF32, reboot), eip = 0x280b33af, esp = 0xbfbfed0c, ebp = 0xbfbfed58 --- taskqueue_drain with the following non-sleepable locks held: exclusive sleep mutex xl1 (network driver) r = 0 (0xc23ad0a4) locked @ /usr/src/sys/pci/if_xl.c:3350 KDB: stack backtrace: witness_warn(2,0,c071f440,c7fa80ff,1b) at witness_warn+0x5d6 taskqueue_drain(c226f800,c23ad0c8,c072a962,cc7,c2394000) at taskqueue_drain+0x2e xl_stop(c23ad0a4,8,c072a962,d16,c23a3380) at xl_stop+0x56 xl_shutdown(c23a3380,c23a3500,ed0babb8,c056136a,c23a3500) at xl_shutdown+0x4d bus_generic_shutdown(c23a3500,c2353d00,ed0babc8,c056136a,c2353d00) at bus_generic_shutdown+0x17 bus_generic_shutdown(c2353d00,c2353b80,ed0babd8,c056136a,c2353b80) at bus_generic_shutdown+0x17 bus_generic_shutdown(c2353b80,c22d0a00,ed0babe8,c056136a,c22d0a00) at bus_generic_shutdown+0x17 bus_generic_shutdown(c22d0a00,c226f600,ed0bac00,c08a2adc,c226f600) at bus_generic_shutdown+0x17 bus_generic_shutdown(c226f600,1,c08bdf2d,2a2,ed0bac10) at bus_generic_shutdown+0x17 acpi_shutdown(c226f600,c226fd00,ed0bac20,c056136a,c226fd00) at acpi_shutdown+0x35 bus_generic_shutdown(c226fd00,c225a480,ed0bac40,c05622bb,c22d0000) at bus_generic_shutdown+0x17 bus_generic_shutdown(c22d0000,102,c0777620,c225a4c0,c225e000) at bus_generic_shutdown+0x17 root_bus_module_handler(c225a480,2,0,c22573a0,ed0bacb0) at root_bus_module_handler+0x23 module_shutdown(0,0,c071c6e3,190,267) at module_shutdown+0x4c boot(c0779e00,8,c071c6e3,a1,bfbfed10) at boot+0x3a2 poweroff_wait(c2392600,ed0bad04,4,422,1) at poweroff_wait syscall(3b,3b,3b,0,1) at syscall+0x13b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (55, FreeBSD ELF32, reboot), eip = 0x280b33af, esp = 0xbfbfed0c, ebp = 0xbfbfed58 --- Shutting down ACPI Rebooting... --Multipart=_Mon__22_Aug_2005_17_07_14_+0000_K4GvqVSDZGI2uQ_A-- From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 17:26:06 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2947F16A41F for ; Mon, 22 Aug 2005 17:26:06 +0000 (GMT) (envelope-from victor.cruceru@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2567343D46 for ; Mon, 22 Aug 2005 17:26:03 +0000 (GMT) (envelope-from victor.cruceru@gmail.com) Received: by wproxy.gmail.com with SMTP id i4so1024072wra for ; Mon, 22 Aug 2005 10:26:00 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=tpGgJliu4TQbuIk0SKyuxK67c8tmolzf1t6EiknO5BbXiITHI5U/gDYDFiD791H1ox9PJUedYFqW8tlNqfKh8ivs81P8kPiuaxbmEBJK5Hwi24bFVahG/MzeeCb9c1BGocqMGfcw8cDEnGYBpZqBcSqeN8FuIgM6L8UpfMAG1hc= Received: by 10.54.131.6 with SMTP id e6mr1566968wrd; Mon, 22 Aug 2005 10:25:59 -0700 (PDT) Received: by 10.54.91.20 with HTTP; Mon, 22 Aug 2005 10:25:59 -0700 (PDT) Message-ID: <4940255050822102561928fbd@mail.gmail.com> Date: Mon, 22 Aug 2005 20:25:59 +0300 From: victor cruceru To: freebsd-hackers@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 6.0 BETA2: SATA HDD not detected X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: soc-victor@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 17:26:06 -0000 Hi all, I've just tried to install 6.0 BETA2 on a PC with a SATA HDD. I have no issue installing and running 5.4 - RELEASE on the same hardware. Here it is what is detected by the 5.4 installation: ---------------------------------------------------------------------------= --------------------------------------------- atapci1: port=20 0xef90-0xef9f,0xefe0-0xefe3,0xefa8-0xefaf,0x efe4-0xefe7,0xeff0-0xeff7 irq 17 at device 5.0 on pci0 ad4: 76319MB [155061/16/63] at ata2-master SATA150 ---------------------------------------------------------------------------= --------------------------------------------- While the SiS 964 SATA150 controller is also detected by the 6.0 BETA2=20 install, the ad4 HDD is not detected. Any help is greatly appreciated. Thanks, victor cruceru From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 17:35:09 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C71616A41F for ; Mon, 22 Aug 2005 17:35:09 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: from voodoo.oberon.net (voodoo.oberon.net [212.118.165.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id F18D843D46 for ; Mon, 22 Aug 2005 17:35:08 +0000 (GMT) (envelope-from igor@doom.homeunix.org) Received: from dialup84114-209.ip.peterstar.net ([84.204.114.209] helo=doom.homeunix.org) by voodoo.oberon.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.52 (FreeBSD)) id 1E7GCN-000MCY-6D for freebsd-hackers@freebsd.org; Mon, 22 Aug 2005 19:35:04 +0200 Received: from doom.homeunix.org (localhost [127.0.0.1]) by doom.homeunix.org (8.13.3/8.13.3) with ESMTP id j7MHYZQk000678; Mon, 22 Aug 2005 21:34:35 +0400 (MSD) (envelope-from igor@doom.homeunix.org) Received: (from igor@localhost) by doom.homeunix.org (8.13.3/8.13.3/Submit) id j7LIwP40000749; Sun, 21 Aug 2005 22:58:25 +0400 (MSD) (envelope-from igor) Date: Sun, 21 Aug 2005 22:58:25 +0400 From: Igor Pokrovsky To: kamalp@acm.org Message-ID: <20050821185825.GA702@doom.homeunix.org> Mail-Followup-To: kamalp@acm.org, Mike Adewole , hselasky@c2i.net, freebsd-hackers@freebsd.org References: <20050821083920.4674.qmail@web52713.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050821083920.4674.qmail@web52713.mail.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, hselasky@c2i.net Subject: Re: Project BSDVISION Wants To Develop Native *BSD Console Desktop X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 17:35:09 -0000 On Sun, Aug 21, 2005 at 01:39:20AM -0700, Kamal R. Prasad wrote: > > It will be running on a virtual console in text or > > graphics mode like > > TurboVision used to, but we are focusing on text > > mode for now. As I just > > wrote to someone else, the main idea is to enable > > BSD programs to have a > > nice console (textual and graphical) interface with > > and without any windows > > system. So I could have a standalone program that > > Thst would be great to have and extend to a > full-fledged GUI interface as X is overkill for lots > of people. BTW -does it use drivers for graphics > accelerator cards? Heh, what are you going to accelerate in text mode? 8-) -ip -- Go where the money is. From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 23:06:20 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44AB416A41F; Mon, 22 Aug 2005 23:06:20 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from rohrpostix.tallence.de (rohrpostix.tallence.de [212.12.62.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id D240243D48; Mon, 22 Aug 2005 23:06:19 +0000 (GMT) (envelope-from stb@lassitu.de) Received: from [44.128.40.11] (janus.spock.tallence.de [44.128.40.11]) by rohrpostix.tallence.de (Postfix) with ESMTP id 9EA731AD921; Tue, 23 Aug 2005 01:06:17 +0200 (CEST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v733) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <5051CE43-C8D3-41BD-9944-11EDFEA4300D@lassitu.de> Content-Transfer-Encoding: quoted-printable From: Stefan Bethke Date: Tue, 23 Aug 2005 01:06:18 +0200 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= X-Mailer: Apple Mail (2.733) Cc: freebsd-hackers@freebsd.org, m.ehinger@ltur.de Subject: Re: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 23:06:20 -0000 Am 22.08.2005 um 17:26 schrieb S=F8ren Schmidt: > On 22/08/2005, at 10:08, m.ehinger@ltur.de wrote: >> what would be the best approach to implement aps on FreeBSD? >> >> I got an Accelerometer driver which will deliver data. First =20 >> Version is available at >> https://sourceforge.net/project/showfiles.php?=20 >> group_id=3D138242&package_id=3D160977 >> >> We have to poll the device for information quiet often to detect a =20= >> possible shock early enough to park disk drive heads. > Urhm, what type of "accidents" is it we want to protect against here ? > > It will take several tens of mS to get the heads parked if not =20 > hundreds, and the worst case scenario would be that the "accident" =20 > will happen just as the heads are on the way to the parking zone =20 > which would *really* destroy data on there, unless the disk has =20 > special HW to just quickly lift the heads or something. I have no insight into either IBM's or Apple's implementation, but =20 I've read that they both rely on detecting the machine being in =20 freefall, or similar acceleration states, as a cue to have the HD =20 park the heads before a possible impact. Early reports from Mac enthusiast sites (and I believe similar =20 reports from IBM users) indicate that the hysteresis is so small that =20= gently pounding the table the notebook is sitting on will make the =20 drive park the heads, and lead to 10 to 20 seconds delay before the =20 drive can be accessed again. Given how tightly coupled mechanically the HD in most notebooks is to =20= it's shell, it seems a very good idea to pursue. If you have access to a new(ish) PowerBook, I recommend checking out =20 http://www.kernelthread.com/software/ams/. The sensitivity of the =20 accelerometer is truely astounding. (For those who haven't seen it: =20 you turn the notebook, and the demo window is turned so it stays =20 level. It takes *really* small movements to confuse the system.) Stefan --=20 Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 23 02:47:12 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 028AD16A41F; Tue, 23 Aug 2005 02:47:12 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (delight.idiom.com [216.240.32.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B368643D45; Tue, 23 Aug 2005 02:47:11 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 438B221E0D2; Mon, 22 Aug 2005 19:47:11 -0700 (PDT) Received: from [192.168.2.2] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id j7N2lATD055844; Mon, 22 Aug 2005 19:47:10 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <430A8E2B.6040408@elischer.org> Date: Mon, 22 Aug 2005 19:47:07 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050424 X-Accept-Language: en, hu MIME-Version: 1.0 To: Borja Marcos References: <5FFDC44D-F094-4856-8FAC-4D14EB77B47A@sarenet.es> In-Reply-To: <5FFDC44D-F094-4856-8FAC-4D14EB77B47A@sarenet.es> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2005 02:47:12 -0000 Borja Marcos wrote: >> I think this will need to be tailored to the exact type of "mishap" >> one wants to protect against. > > > I think that the main purpose of the shock detection system is to > allow data to be recovered from the disk in case the laptop is broken. > By parking the heads asap you can avoid damaging the plates with the head. > > At least that's what I read. The disk won't be necessary usable > after being dropped, but at least the plates should be readable. no, the aim is to detect the LACK of acceleration as the laptop goes into freefall. You have about 1/4 a second to get the heads in once you detect that you are falling. Quick by human standards but an eon in computer terms. > > In that case, priority number one would be a fast parking of the > head. However, it could lead to a worst-case data loss with softupdates > and the disk cache, isn't it? > > > > > Borja. > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 23 03:39:08 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDB8516A41F; Tue, 23 Aug 2005 03:39:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 909B643D46; Tue, 23 Aug 2005 03:39:08 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j7N3cmOR054897; Mon, 22 Aug 2005 21:38:48 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 Aug 2005 21:38:57 -0600 (MDT) Message-Id: <20050822.213857.78011913.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <430A8E2B.6040408@elischer.org> References: <5FFDC44D-F094-4856-8FAC-4D14EB77B47A@sarenet.es> <430A8E2B.6040408@elischer.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.village.org [127.0.0.1]); Mon, 22 Aug 2005 21:38:49 -0600 (MDT) Cc: freebsd-hackers@freebsd.org, sos@freebsd.org, borjamar@sarenet.es Subject: Re: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2005 03:39:09 -0000 In message: <430A8E2B.6040408@elischer.org> Julian Elischer writes: : You have about 1/4 a second to get the heads in once you detect that : you are falling. Yes. For a 4' fall, we know it takes 1/2 a second to reach the ground: s = 1/2 a t^2 + v0 t + s0 s0 = 0, a = 32 f/s^2, v0 = 0, s = 4, solve for t gives 1/2 a second to make the fall. Sos was saying 10's of ms to retract the heads, so even a 300ms response time wouldn't be fatal, but it would be pushing the limits. For a 2' fall, you have even less time. More like 350ms. 1' is 250ms... Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 23 04:48:54 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12ECC16A41F for ; Tue, 23 Aug 2005 04:48:54 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: from smtpgate2.pacific.net.sg (smtpgate2.pacific.net.sg [203.120.90.28]) by mx1.FreeBSD.org (Postfix) with SMTP id 1C3DC43D45 for ; Tue, 23 Aug 2005 04:48:52 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 13967 invoked from network); 23 Aug 2005 04:48:51 -0000 Received: from maxwell2.pacific.net.sg (203.120.90.192) by smtpgate2.pacific.net.sg with SMTP; 23 Aug 2005 04:48:51 -0000 Received: from [192.168.0.107] ([210.24.246.165]) by maxwell2.pacific.net.sg with ESMTP id <20050823044850.DYRQ28012.maxwell2.pacific.net.sg@[192.168.0.107]>; Tue, 23 Aug 2005 12:48:50 +0800 Message-ID: <430AAA72.9090603@pacific.net.sg> Date: Tue, 23 Aug 2005 12:47:46 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: m.ehinger@ltur.de References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2005 04:48:54 -0000 Hi, m.ehinger@ltur.de wrote: > > what would be the best approach to implement aps on FreeBSD? > Go as deep as possible into the disk driver. The reason is pretty simple. Just stop any write access to the disk as soon as the machine starts moving above a given limit. If the movement is above a higher level, start also to move the heads out. As the heads are moved out when a fall starts, the chance that the heads hit the surface is minimised. The driver can then move the heads back after a certain amount of time passed by without any event and continue operation. > Would an daemon be sufficient for that? Reaction time? What about an kernel thread? > Getting the heads out of the danger zone is one thing but the most crucial thing from my point of view is the write access. If the heads are moved away while writing the current part of the track is damaged. I have seen a Thinkpad of the first lot being so nervous moving the heads avway at the slidest movement of the machine to slow work down to a crawl being seated in a bus or plane. > Other solutions? I did some work like this a very long time ago on RSX. Stopping a write brought for us the cases of damaged file systems down to some 10% of the original value. Erich From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 23 07:04:21 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 781FF16A41F; Tue, 23 Aug 2005 07:04:21 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (delight.idiom.com [216.240.32.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33B3743D45; Tue, 23 Aug 2005 07:04:20 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 96CDD1FDF10; Tue, 23 Aug 2005 00:04:20 -0700 (PDT) Received: from [192.168.2.2] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id j7N74I5d056905; Tue, 23 Aug 2005 00:04:19 -0700 (PDT) (envelope-from julian@elischer.org) Message-ID: <430ACA72.7070303@elischer.org> Date: Tue, 23 Aug 2005 00:04:18 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050424 X-Accept-Language: en, hu MIME-Version: 1.0 To: "M. Warner Losh" References: <5FFDC44D-F094-4856-8FAC-4D14EB77B47A@sarenet.es> <430A8E2B.6040408@elischer.org> <20050822.213857.78011913.imp@bsdimp.com> In-Reply-To: <20050822.213857.78011913.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, sos@freebsd.org, borjamar@sarenet.es Subject: Re: IBM Active Protection System Approach X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2005 07:04:21 -0000 M. Warner Losh wrote: > In message: <430A8E2B.6040408@elischer.org> > Julian Elischer writes: > : You have about 1/4 a second to get the heads in once you detect that > : you are falling. > > Yes. For a 4' fall, we know it takes 1/2 a second to reach the > ground: > s = 1/2 a t^2 + v0 t + s0 > > s0 = 0, a = 32 f/s^2, v0 = 0, s = 4, solve for t gives 1/2 a second to > make the fall. Sos was saying 10's of ms to retract the heads, so > even a 300ms response time wouldn't be fatal, but it would be pushing > the limits. > > For a 2' fall, you have even less time. More like 350ms. 1' is 250ms... > > Warner I decided that you assume it's being picked up and slips out of your grasp and then dropped a pen from about 2' and said "yep, something like 1/3rd of a second.. I'll say something shorter than that" :-) From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 23 09:34:11 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAEFB16A41F for ; Tue, 23 Aug 2005 09:34:11 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 417A643D45 for ; Tue, 23 Aug 2005 09:34:10 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.4/8.13.3) with ESMTP id j7N9Y6bm096018 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 23 Aug 2005 11:34:06 +0200 (CEST) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id j7N9Y6Q6096017 for hackers@freebsd.org; Tue, 23 Aug 2005 11:34:06 +0200 (CEST) Date: Tue, 23 Aug 2005 11:34:06 +0200 From: Divacky Roman To: hackers@freebsd.org Message-ID: <20050823093406.GB95757@stud.fit.vutbr.cz> References: <20050821094849.GA79907@stud.fit.vutbr.cz> <86slx25g6i.fsf@xps.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86slx25g6i.fsf@xps.des.no> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 Cc: Subject: Re: number of simultanously opened files X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2005 09:34:12 -0000 On Mon, Aug 22, 2005 at 02:06:45PM +0200, Dag-Erling Sm?rgrav wrote: > Divacky Roman writes: > > witten ~# sysctl kern.maxfiles=100000 > > kern.maxfiles: 100000 -> 100000 > > witten ~# sysctl kern.maxfilesperproc=100000 > > kern.maxfilesperproc: 100000 -> 100000 > > witten ~# > > > > but I still cannot open more than 7319 files simultaneously. pls can > > you tell me why? > > man ulimit yeah.. you're right (in this case it was tcsh's limit) thnx roman From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 23 10:08:47 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BBA8716A420 for ; Tue, 23 Aug 2005 10:08:47 +0000 (GMT) (envelope-from sd@buc.com.ua) Received: from relay3.sitel.com.ua (pitt.sitel.com.ua [217.27.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E64643D49 for ; Tue, 23 Aug 2005 10:08:46 +0000 (GMT) (envelope-from sd@buc.com.ua) Received: from arrow.buc.com.ua (arrow.buc.com.ua [217.27.145.61]) by relay3.sitel.com.ua (8.12.9p2/8.12.9) with ESMTP id j7NA8h9P062263 for ; Tue, 23 Aug 2005 13:08:43 +0300 (EEST) (envelope-from sd@buc.com.ua) Received: by arrow.buc.com.ua (Postfix, from userid 85) id 3D268A1295; Tue, 23 Aug 2005 13:12:29 +0300 (EEST) Received: from [192.168.13.97] (unknown [192.168.13.97]) by arrow.buc.com.ua (Postfix) with ESMTP id 12463A11D9 for ; Tue, 23 Aug 2005 13:12:29 +0300 (EEST) Message-ID: <430AF4F0.4050606@buc.com.ua> Date: Tue, 23 Aug 2005 13:05:36 +0300 From: sd User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, uk, ru MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Making several custom boot configurations? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2005 10:08:47 -0000 I'm trying to make several different configurated systems on one FreeBSD box: different kernel parameters for each configuration, different hostname, startup scripts, network configurations, etc. Can it be done by adding some custom points to boot manager menu or altering existent ones? Thanks, Dmytro From owner-freebsd-hackers@FreeBSD.ORG Mon Aug 22 13:12:28 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6855416A41F for ; Mon, 22 Aug 2005 13:12:28 +0000 (GMT) (envelope-from inten@inten.pl) Received: from a.org.pl (a.org.pl [80.51.218.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CCF343D48 for ; Mon, 22 Aug 2005 13:12:26 +0000 (GMT) (envelope-from inten@inten.pl) Received: from bhy208.neoplus.adsl.tpnet.pl ([83.28.114.208]) by a.org.pl with esmtpa (Exim 4.50) id 1E7C64-0003vP-KK for freebsd-hackers@freebsd.org; Mon, 22 Aug 2005 15:12:18 +0200 Date: Mon, 22 Aug 2005 15:12:18 +0200 From: "inten.pl" X-Mailer: The Bat! (v3.0) Professional X-Priority: 3 (Normal) Message-ID: <115555517.20050822151218@inten.pl> To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Scanned with clamav. X-Mailman-Approved-At: Tue, 23 Aug 2005 11:54:37 +0000 Subject: [4.11] weekly panics - hints needed X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "inten.pl" List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 13:12:28 -0000 Hello, we have problem with one of your 4.11 machine. About once a week it has a kernel panic. I've tried many different kernel configs and a few different -STABLE builds for different months. It always gets panic one or two times each week, but in random time. This server is used mainly as a web/database server. This problem occurs from time we have run this server. Hardware seems to be good, we hadn't have any hardware problems and server hangs. Now it's: # uname -a FreeBSD server.foo 4.11-STABLE FreeBSD 4.11-STABLE #0: Sun Aug 14 23:11:31 CEST 2005 root@server.foo:/usr/src/sys/compile/XXX i386 dmesg: Aug 21 12:15:10 xxx /kernel: root@xxx.inten.pl:/usr/src/sys/compile/XXX Aug 21 12:15:10 xxx /kernel: Timecounter "i8254" frequency 1193182 Hz Aug 21 12:15:10 xxx /kernel: CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3065.81-MHz 686-class CPU) Aug 21 12:15:10 xxx /kernel: Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Aug 21 12:15:10 xxx /kernel: Features=0xbfebfbff Aug 21 12:15:10 xxx /kernel: Hyperthreading: 2 logical CPUs Aug 21 12:15:10 xxx /kernel: real memory = 1073676288 (1048512K bytes) Aug 21 12:15:10 xxx /kernel: avail memory = 1039650816 (1015284K bytes) Aug 21 12:15:10 xxx /kernel: APIC_IO: MP table broken: ExtINT entry corrupt! Aug 21 12:15:10 xxx /kernel: Programming 16 pins in IOAPIC #0 Aug 21 12:15:10 xxx /kernel: IOAPIC #0 intpin 2 -> irq 0 Aug 21 12:15:10 xxx /kernel: Programming 16 pins in IOAPIC #1 Aug 21 12:15:10 xxx /kernel: Programming 16 pins in IOAPIC #2 Aug 21 12:15:10 xxx /kernel: Programming 16 pins in IOAPIC #3 Aug 21 12:15:10 xxx /kernel: FreeBSD/SMP: Multiprocessor motherboard: 4 CPUs Aug 21 12:15:11 xxx /kernel: cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 Aug 21 12:15:11 xxx /kernel: cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 Aug 21 12:15:11 xxx /kernel: cpu2 (AP): apic id: 2, version: 0x00050014, at 0xfee00000 Aug 21 12:15:11 xxx /kernel: cpu3 (AP): apic id: 3, version: 0x00050014, at 0xfee00000 Aug 21 12:15:11 xxx /kernel: io0 (APIC): apic id: 8, version: 0x000f0011, at 0xfec00000 Aug 21 12:15:11 xxx /kernel: io1 (APIC): apic id: 9, version: 0x000f0011, at 0xfec01000 Aug 21 12:15:11 xxx /kernel: io2 (APIC): apic id: 10, version: 0x000f0011, at 0xfec02000 Aug 21 12:15:11 xxx /kernel: io3 (APIC): apic id: 11, version: 0x000f0011, at 0xfec03000 Aug 21 12:15:11 xxx /kernel: Preloaded elf kernel "kernel" at 0xc053a000. Aug 21 12:15:11 xxx /kernel: Warning: Pentium 4 CPU: PSE disabled Aug 21 12:15:11 xxx /kernel: Pentium Pro MTRR support enabled Aug 21 12:15:11 xxx /kernel: md0: Malloc disk Aug 21 12:15:11 xxx /kernel: Using $PIR table, 18 entries at 0xc00f8270 Aug 21 12:15:11 xxx /kernel: npx0: on motherboard Aug 21 12:15:11 xxx /kernel: npx0: INT 16 interface Aug 21 12:15:11 xxx /kernel: pcib0: on motherboard Aug 21 12:15:11 xxx /kernel: IOAPIC #1 intpin 0 -> irq 2 Aug 21 12:15:11 xxx /kernel: IOAPIC #1 intpin 1 -> irq 5 Aug 21 12:15:11 xxx /kernel: pci0: on pcib0 Aug 21 12:15:11 xxx /kernel: pci0: at 4.0 irq 2 Aug 21 12:15:11 xxx /kernel: fxp0: port 0x9c00-0x9c3f mem 0xfe000000-0xfe01ffff,0xfe100000-0xfe100fff irq 5 at device 5.0 on pc i0 Aug 21 12:15:11 xxx /kernel: fxp0: Ethernet address 00:0d:61:37:30:62 Aug 21 12:15:11 xxx /kernel: inphy0: on miibus0 Aug 21 12:15:11 xxx /kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Aug 21 12:15:11 xxx /kernel: isab0: at device 15.0 on pci0 Aug 21 12:15:11 xxx /kernel: isa0: on isab0 Aug 21 12:15:11 xxx /kernel: atapci0: port 0x9fd0-0x9fdf,0x374-0x377,0x170-0x177,0x3f4-0x3f7,0x1f0-0x1f7 at device 15.1 on pci0 Aug 21 12:15:11 xxx /kernel: ata0: at 0x1f0 irq 14 on atapci0 Aug 21 12:15:11 xxx /kernel: ata1: at 0x170 irq 15 on atapci0 Aug 21 12:15:11 xxx /kernel: pcib1: on motherboard Aug 21 12:15:11 xxx /kernel: IOAPIC #1 intpin 13 -> irq 9 Aug 21 12:15:11 xxx /kernel: IOAPIC #1 intpin 14 -> irq 10 Aug 21 12:15:11 xxx /kernel: pci1: on pcib1 Aug 21 12:15:11 xxx /kernel: ahd0: port 0xc800-0xc8ff,0xcc00-0xccff mem 0xfe800000-0xfe801fff irq 9 at device 3.0 on p ci1 Aug 21 12:15:11 xxx /kernel: aic7902: Ultra320 Wide Channel A, SCSI Id=0, PCI 33 or 66Mhz, 512 SCBs Aug 21 12:15:11 xxx /kernel: ahd1: port 0xc000-0xc0ff,0xc400-0xc4ff mem 0xfe600000-0xfe601fff irq 10 at device 3.1 on pci1 Aug 21 12:15:11 xxx /kernel: aic7902: Ultra320 Wide Channel B, SCSI Id=0, PCI 33 or 66Mhz, 512 SCBs Aug 21 12:15:11 xxx /kernel: pcib2: on motherboard Aug 21 12:15:11 xxx /kernel: IOAPIC #1 intpin 3 -> irq 11 Aug 21 12:15:11 xxx /kernel: pci2: on pcib2 Aug 21 12:15:11 xxx /kernel: em0: port 0xdc00-0xdc3f mem 0xfeb00000-0xfeb1ffff irq 11 at device 2.0 on pci2 Aug 21 12:15:11 xxx /kernel: em0: Speed:N/A Duplex:N/A Aug 21 12:15:11 xxx /kernel: pcib3: on motherboard Aug 21 12:15:11 xxx /kernel: pci3: on pcib3 Aug 21 12:15:11 xxx /kernel: pcib4: on motherboard Aug 21 12:15:11 xxx /kernel: pci4: on pcib4 Aug 21 12:15:11 xxx /kernel: orm0: