Re: automatic checking of source code

2006-04-23 Thread mygcc
Divacky Roman wrote: > I just found http://mygcc.free.fr/ which is a project for automatic checking of > source code for bugs (memory leaks, unreleased locks, null pointer > dereferences). I recall there was some SoC project to achieve something > similar but this is complete and ready to run... >

Still Fundraising for FreeBSD security development

2006-04-23 Thread Colin Percival
Dear FreeBSD users, On April 4th, I thought that I had reached my donations target for funding my summer of FreeBSD security development, and asked people to stop sending further donations. Sadly, it seems that this assessment was premature, as it relied upon two large pledges, and it now appears

Re: [PATCH] Fancy rc startup style RFC - v6

2006-04-23 Thread Coleman Kane
On 4/23/06, Sean Winn <[EMAIL PROTECTED]> wrote: > > [EMAIL PROTECTED] wrote: > > On Thu, Apr 20, 2006 at 10:32:33PM -0500, Eric Anderson wrote: > >> Other than that, do we have general consensus that these do what they > >> claim? Any outstanding issues that haven't been addressed? > > > > One re

Re: Server choice.

2006-04-23 Thread Michael Vince
Paul Halliday wrote: Hi, I am in the process of building a new database server and after pricing up 2 Dell models I thought I would throw this out just to see which choice would be better suited for FreeBSD. The demands on the system will be mostly network -> disk I/O with a hope of best perfo

Re: Per CPU cpu-statistics under SMP

2006-04-23 Thread Marco van Tol
On Fri, Apr 21, 2006 at 12:40:49AM +0200, Marco van Tol wrote: > On Wed, Apr 19, 2006 at 07:26:27AM +, Marco van Tol wrote: > > On Tue, Apr 18, 2006 at 06:38:26PM -0400, John Baldwin wrote: > > [...] > > > > Ah, hmm. On 6.x we don't have per-thread stat ticks yet, which is > > > probably why

RE: [PATCH] Fancy rc startup style RFC - v6

2006-04-23 Thread Sean Winn
[EMAIL PROTECTED] wrote: > On Thu, Apr 20, 2006 at 10:32:33PM -0500, Eric Anderson wrote: >> Other than that, do we have general consensus that these do what they >> claim? Any outstanding issues that haven't been addressed? > > One request: > > Please remove the two seperate rc.conf lines, and