> On Tue, 27 Feb 2001, Jake Burkholder wrote:
>
> > > a distributed.net client (ports/misc/dnetc) being run on -current with
> > > today's kernel just hangs my box. the system _dramatically_ slows
> > > down and stops to respond on any external events (keyboard, network,
> > > etc).
> > Sorry, th
On Tue, 27 Feb 2001, Jake Burkholder wrote:
> > a distributed.net client (ports/misc/dnetc) being run on -current with
> > today's kernel just hangs my box. the system _dramatically_ slows
> > down and stops to respond on any external events (keyboard, network,
> > etc).
> Sorry, this should be f
> Hello,
>
> a distributed.net client (ports/misc/dnetc) being run on -current with
> today's kernel just hangs my box. the system _dramatically_ slows
> down and stops to respond on any external events (keyboard, network,
> etc).
>
> d.net client is a daemon, that uses cpu idle (and only idle)
Unless the network is lying to me again, Ilya Naumov said:
> a distributed.net client (ports/misc/dnetc) being run on -current with
> today's kernel just hangs my box. the system _dramatically_ slows
> down and stops to respond on any external events (keyboard, network,
> etc).
An interesting s
Hello,
a distributed.net client (ports/misc/dnetc) being run on -current with
today's kernel just hangs my box. the system _dramatically_ slows
down and stops to respond on any external events (keyboard, network,
etc).
d.net client is a daemon, that uses cpu idle (and only idle) time to do some