Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Nov 2011 19:37:31 +0200
From:      Andriy Gapon <avg@FreeBSD.org>
To:        Baptiste Daroussin <bapt@FreeBSD.org>
Cc:        FreeBSD Ports <ports@FreeBSD.org>
Subject:   Re: [removed ports] sysutils/cpuburn
Message-ID:  <4EC2A35B.8050300@FreeBSD.org>
In-Reply-To: <20111115150735.GA96251@azathoth.lan>
References:  <4EC2786E.5060907@FreeBSD.org> <20111115150735.GA96251@azathoth.lan>

next in thread | previous in thread | raw e-mail | index | archive | help
on 15/11/2011 17:07 Baptiste Daroussin said the following:
> On Tue, Nov 15, 2011 at 04:34:22PM +0200, Andriy Gapon wrote:
>>
>> Does anyone know good any alternative(s) for cpuburn?
>> If not, then I would like to request that this port be restored.
>> I am prepared to be designated as its maintainer and to host its distfile (via my
>> FreeBSD account).
>>
>> Maintaining the port should be rather easy as it can not have any security issues
>> by definition and at the moment there is no active upstream, so no code changes
>> are expected.
>>
>> P.S. Sorry that I've missed its deprecation.  I haven't noticed the activity until
>> I needed to use it at yet another system.
>>
> 
> I often use sysutils/stress don't know if that fits your needs?

I didn't know about this tool before...
Unfortunately I do not see a detailed description of how exactly it loads CPU and
if it does any validation/verification.  cpuburn is more explicit about this and
is kind of proven.  Besides it has additional stuff like e.g. burnBX/burnMMX.
So, I would I love to still have it.
Thank you for pointing me to sysutils/stress in any case.

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EC2A35B.8050300>