staff blogs

distributed.net staff keep (relatively) up-to-date logs of their activities in .plan files. These were traditionally available via finger, but we've put them on the web for easier consumption.

1999-04-27

ivo [27-Apr-1999 @ 20:17]

Filed under: Uncategorized @ 20:17 +00:00

:: 27-Apr-1999 20:17 (Tuesday) ::

I need a plan?

1999-04-26

moose [26-Apr-1999 @ 12:53]

Filed under: Uncategorized @ 12:53 +00:00

:: 26-Apr-1999 13:00 (Monday) ::

A new version of the rc5des441-win32-x86-cli.zip client has been
uploaded. This version fixes the shutdown problem in the previous
client.

The client can be downloaded from:

http://www.distributed.net/clients.html

or

ftp://www.distributed.net/pub/dcti/v2.7110/

Enjoy

1999-04-20

nugget [20-Apr-1999 @ 21:17]

Filed under: Uncategorized @ 21:17 +00:00

:: 20-Apr-1999 21:17 (Tuesday) ::

Just a tiny addition…

http://stats.distributed.net/rc5-64/money.html

nugget [20-Apr-1999 @ 02:54]

Filed under: Uncategorized @ 02:54 +00:00

:: 20-Apr-1999 02:57 (Tuesday) ::

The stats run this evening failed for reasons I have not yet determined.
The bcp (that’s “Bulk Copy”) routine that dumps the actual log files into
the database failed with complaints of being unable to connect to the
server. I have, however, been unable to duplicate the failure. While
worrisome, there isn’t much I can do in the way of debugging unless it
decides to start failing more consistently. I’ve simply restarted the
run and I’ll keep an eye on it as it goes.

As a result, of course, the update will be delayed this evening. Sorry
for the inconvienence.

1999-04-17

gregh [17-Apr-1999 @ 19:50]

Filed under: Uncategorized @ 19:50 +00:00

:: 17-Apr-1999 19:54 (Saturday) ::

I have put together a todo list of all things left to do in the OGR core
integration. This list can be found at:

http://www.distributed.net/~gregh/ogr-todo.html

1999-04-15

nugget [15-Apr-1999 @ 15:13]

Filed under: Uncategorized @ 15:13 +00:00

:: 15-Apr-1999 15:18 (Thursday) ::

Well the reports are starting to roll in, it looks like retire_to is a
success. So far I’ve not heard any bug reports or problems. Since I
posted the plan update yesterday, we’ve had over 250 addresses retired.

However, I would like to mention that you can stop mailing me about the
“bug” in stats that’s causing people to rise thousands of places without
having done a lot of blocks “yesterday”. This is what retire_to looks
like when it happens. There’s no cause for alarm. :)

1999-04-14

nitehawk [14-Apr-1999 @ 17:50]

Filed under: Uncategorized @ 17:50 +00:00

:: 14-Apr-1999 17:52 (Wednesday) ::

The bug where tmsummary.php3 was reporting teams as nonexistent,
should be fixed now. Please let me know if there are problems.

Also fixed are the nifty little arrows that say how far a team
moved in the rankings from yesterday :)

Next on my list is the team member listings (unless nugget beats
me to it).

nugget [14-Apr-1999 @ 14:51]

Filed under: Uncategorized @ 14:51 +00:00

:: 14-Apr-1999 15:21 (Wednesday) ::

The retire_to function is now in service. To briefly explain, you may
now permanently retire an old/outdated/invalid email address in stats
and have those blocks attributed to your current email address. To do
this, you need a couple things:

o You need to know the password for the email you wish to retire
o You need to configure your clients to use your new email address.
o Your new email address must appear in the stats database.

If you’ve got all that straightened out, then simply edit the information
for the old address you wish to retire. You will find a new link at the
very bottom of the participant configuration screen which will walk you
through the retiring process.

Just a few FAQs for those who are not completely familiar with the
process:

1. all past and any future blocks are allocated, so if you miss a
client and blocks still come in from the old address, you’ll
still be properly credited for them.

2. Team assignments are not affected by this. If your old address is
on one team, and the new address is on another team, the original
team will not have its blocks stolen as a byproduct of the retire
procedure.

3. This procedure is quite permanent.

myshkin [14-Apr-1999 @ 07:43]

Filed under: Uncategorized @ 07:43 +00:00

:: 14-Apr-1999 07:45 (Wednesday) ::

To shrink the to-do list.

(No, the to-do list is not publically available.)

1999-04-13

moose [13-Apr-1999 @ 15:18]

Filed under: Uncategorized @ 15:18 +00:00

:: 13-Apr-1999 15:44 (Tuesday) ::

Ok lots of you have been asking about the new features in the
2.7109.440 clients. Here are the major changes:

– Added FIFO buffers
– Added Big Block support. Current Limit 2^33 block sizes.
Big blocks are only supported with 306+ proxies.
– Added infrastructure for OGR and CSS
– Added Remote buffer support
– Improved client speed in some cases

Users upgrading to 440 series will need to upgrade all clients at one
time if they are in a buffer sharing situation.

Hope this helps.

Older Posts »