Hi hackers,
I'm pleased to participate in such cool project. Is anybody kind
enough to tell me how to run this program while the FreeBSD box is
idle?
Thanks in advance,
--
Kazukiyo Ueda
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the
On Tue, 18 May 1999, Ueda, Kazukiyo wrote:
I'm pleased to participate in such cool project. Is anybody kind
enough to tell me how to run this program while the FreeBSD box is
idle?
Install the astro/setiathome port. One thing I've been meaning to look at
though is that it seems to run it at
Hi,
At 16:48 18/05/99 +0900, Ueda, Kazukiyo wrote:
I'm pleased to participate in such cool project. Is anybody kind
enough to tell me how to run this program while the FreeBSD box is
idle?
man nice
--
Bob Bishop +44 118 977 4017
r...@gid.co.uk fax +44 118 989 4254
Kris Kennaway kkenn...@physics.adelaide.edu.au wrote:
On Tue, 18 May 1999, Ueda, Kazukiyo wrote:
I'm pleased to participate in such cool project. Is anybody kind
enough to tell me how to run this program while the FreeBSD box is
idle?
Install the astro/setiathome port.
Make sure you have
#define quoting(Stefan Bethke)
// Kris Kennaway kkenn...@physics.adelaide.edu.au wrote:
// On Tue, 18 May 1999, Ueda, Kazukiyo wrote:
// One thing I've been meaning to look at though is that it seems to run it
// at niceness 1, which isn't exactly friendly to the other consumers of
// CPU. You
Stefan Bethke wrote:
Make sure you have the newest version of the port (for setiathome-1.1).
Pre-1.1 version don't work anymore. Unfortunatly, the release of 1.1 came
too late for the 3.2 CDs. Even more unfortunate is the fact that all
versions (including 1.1) try to send mail by invoking
In the last episode (May 18), Wes Peters said:
Stefan Bethke wrote:
Would you suggest a different default nice level, then, and what
should it be?
RTP_PRIO_IDLE of course. See rtprio(2).
One can easily modifiy ${PREFIX}/etc/rc.d/setiathome.sh to run it
-with nice 100, and I'm open
Dan Nelson wrote:
Problem is that idprio isn't safe. I used to idprio the rc5client, but
within a day or do the machine would lock up. Rc5client would get a
lock on the root of the filesystem at idprio, and if there was another
process running at 100% CPU, rc5client would never get a
:Dan Nelson wrote:
:
: Problem is that idprio isn't safe. I used to idprio the rc5client, but
: within a day or do the machine would lock up. Rc5client would get a
: lock on the root of the filesystem at idprio, and if there was another
: process running at 100% CPU, rc5client would never get
Hi,
On Tue, May 18, 1999 at 12:17:48PM -0500, Dan Nelson wrote:
Problem is that idprio isn't safe. I used to idprio the rc5client, but
within a day or do the machine would lock up.
oops. That's new for me.
I'm running the 'rc5client' on various machines (2.2.6-stable, 2.2.8-stable,
Matthew Dillon dil...@apollo.backplane.com wrote:
For people who have idle cpu to spare, this is a good time to start
putting those cycles to good use with the Seti project! The project
has been running a beta test for a while, but as of May 13th 1999 they
reset the stats and
#define quoting(Matthew Dillon)
// This reduces the effect an idprio seti background task has on the rest of
// the system.
Yeah... I was going to ask just this. My users complained about
server response after starting setiathome.
// sysctl -w kern.quantum=2
Humm, my systems
Joao Carlos Mendes Luis wrote:
#define quoting(Matthew Dillon)
// This reduces the effect an idprio seti background task has on the rest
of
// the system.
Yeah... I was going to ask just this. My users complained about
server response after starting setiathome.
// sysctl
Joe Abley jab...@clear.co.nz wrote:
I compiled the 1.1 client for FreeBSD3.1 -- what seems to be the
problem with it? [It seemed to work ok for me, but I admit I didn't
test it very exhaustively].
I'm running it on a P166 box running 3.1, and it's running quite
happily.
As an aside:
I
On Fri, May 14, 1999 at 04:56:05PM -0700, Matthew Dillon wrote:
:http://setiathome.ssl.berkeley.edu/
:
: Now available at ftp://ftp.cdrom.com/pub/setiathome/
:
:-DG
:
:David Greenman
:Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
:Creator of
On Fri, May 14, 1999 at 04:57:30PM -0700, Matthew Jacob wrote:
So do I. I would like them to make the source available. I have *lots* of
machines available that are sitting doing nothing. But they don't run
FreeBSD (yet). I have at least 3 alpha 8200s and 4 Alpha 4100s that are
running
:If people have been having problems with proxy support in the 1.1 client
:on FreeBSD, let me know and I'll mail you a new binary to test.
It seems to be working now. Maybe it was just some bad work units.
Very Odd.
-Matt
BTW, this story might be of interest:
http://www.msnbc.com/news/255770.asp
-DG
David Greenman
Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
Creator of high-performance Internet servers - http://www.terasolutions.com
To Unsubscribe: send mail to
The seti stuff appears to be working again. I think they just
had some bad data batches. I'm running it on 6 cpus at idprio.
Hmm.. seems to effect responsiveness some, sounds like something
in the scheduler that we should be able to fix :-)
This reduces the effect an idprio seti background task has on the rest of
the system.
sysctl -w kern.quantum=2
The default is 100,000 ( 100ms ) which, for a modern cpu, is much more
chunky then it needs to be. Reducing it to 20ms makes a big difference.
At 10 I can
beware, I think this sysctl does something different on 3.x as I think
there was a code freeze on 3.x when we fixed it..
On Sat, 15 May 1999, Matthew Dillon wrote:
This reduces the effect an idprio seti background task has on the rest of
the system.
sysctl -w kern.quantum=2
For people who have idle cpu to spare, this is a good time to start
putting those cycles to good use with the Seti project! The project
has been running a beta test for a while, but as of May 13th 1999 they
reset the stats and introduced new clients for Unix, Windows, and the Mac.
For people who have idle cpu to spare, this is a good time to start
putting those cycles to good use with the Seti project!
Where would would find informatio on said project?
Nate
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the
:
: For people who have idle cpu to spare, this is a good time to start
: putting those cycles to good use with the Seti project!
:
:Where would would find informatio on said project?
:
:
:Nate
Oops! I'm sorry!
http://setiathome.ssl.berkeley.edu/
: For people who have idle cpu to spare, this is a good time to start
: putting those cycles to good use with the Seti project!
:
:Where would would find informatio on said project?
:
:
:Nate
Oops! I'm sorry!
http://setiathome.ssl.berkeley.edu/
They're not responding
:
: For people who have idle cpu to spare, this is a good time to start
: putting those cycles to good use with the Seti project!
:
:Where would would find informatio on said project?
:
:
:Nate
Oops! I'm sorry!
http://setiathome.ssl.berkeley.edu/
Now available at
:http://setiathome.ssl.berkeley.edu/
:
: Now available at ftp://ftp.cdrom.com/pub/setiathome/
:
:-DG
:
:David Greenman
:Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org
:Creator of high-performance Internet servers - http://www.terasolutions.com
Yah, but I
So do I. I would like them to make the source available. I have *lots* of
machines available that are sitting doing nothing. But they don't run
FreeBSD (yet). I have at least 3 alpha 8200s and 4 Alpha 4100s that are
running NetBSD now and mostly quiescent.
On Fri, 14 May 1999, Matthew Dillon
28 matches
Mail list logo
