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.

2003-06-01

decibel [01-Jun-2003 @ 17:39]

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

:: 01-Jun-2003 17:39 GMT (Sunday) ::

Ooops, forgot to turn the statsrun back on. *blush*

The change to the RC5-64 pages is done.

2003-05-30

decibel [30-May-2003 @ 22:14]

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

:: 30-May-2003 22:14 GMT (Friday) ::

Something that was changed when we migrated RC5 to the current statsrun code
was to add the ability to scale how things were being displayed on the pages.
As part of this, we decided that for RC5 stats, we would store the number of
keys in the database going forward, instead of the number of blocks. This is
how RC5-72 data is stored, but -64 data is still stored in the old format.

I’m currently running a script that is changing all this data. While it’s
running, there might be some odd things showing up in the RC5-64 pages. Please
ignore them. :)

2003-04-27

decibel [27-Apr-2003 @ 11:31]

Filed under: Uncategorized @ 11:31 +00:00

:: 27-Apr-2003 11:31 GMT (Sunday) ::

The proxy1.madsn.wi.us fullproxy stopped talking to the master for about two
days, which means that work sent to that proxy didn’t show up in stats. The
proxy is talking to the master now, and has flushed all it’s work. I believe
it was done flushing before yesterday’s statsrun, so all the work has probably
showed up in stats by now; if not it will show up in tonight’s run.

2003-04-18

decibel [18-Apr-2003 @ 22:46]

Filed under: Uncategorized @ 22:46 +00:00

:: 18-Apr-2003 22:46 GMT (Friday) ::

The master was down several hours today for a planned outage. Because of this,
the amount of work in stats for today will be a bit low. The ‘missing’ work
will show up tomorrow.

The statsrun was also delayed due to a minor bug. Stats are running now and
should be complete within an hour.

2003-03-27

decibel [27-Mar-2003 @ 13:04]

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

:: 27-Mar-2003 13:04 GMT (Thursday) ::

Stats are happy again.

2003-03-26

decibel [26-Mar-2003 @ 22:39]

Filed under: Uncategorized @ 22:39 +00:00

:: 26-Mar-2003 22:39 GMT (Wednesday) ::

Statsrun puked and the normal procedure for rebuilding things isn’t working.
I’ve been drinking, so I’m not going to screw with it right now. :) I’ll look
at it (and hopefully fix it) tomorrow.

2003-03-18

decibel [18-Mar-2003 @ 22:25]

Filed under: Uncategorized @ 22:25 +00:00

:: 18-Mar-2003 22:25 GMT (Tuesday) ::

DOH! I botched the OGR run last night with my manual shenanigans. I’m
re-running right now.

2003-03-16

decibel [16-Mar-2003 @ 18:49]

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

:: 16-Mar-2003 18:49 GMT (Sunday) ::

Looks like the teamjoin code (in fact, sybase itself) was using CST and not
GMT. I’ve fixed that problem; I’m going to see if it fixes the team join issue.

decibel [16-Mar-2003 @ 18:16]

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

:: 16-Mar-2003 18:16 GMT (Sunday) ::

Ok, I might actually work on stats tonight, even though I should be working on
my resume (anyone need a database architect in Austin, TX?). I’m going to put
the statsrun on hold for right now.

decibel [16-Mar-2003 @ 18:02]

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

:: 16-Mar-2003 18:02 GMT (Sunday) ::

A rather serious bug regarding team joins has been found in stats
(http://n0cgi.distributed.net/bugs/show_bug.cgi?id=3182). In a nutshell, any
work you submit on the day you join a team will not be credited to that team.
This also means that if you weren’t on a team and join one, the work for that
day will not be credited to that team.

I’m going to do tomorrow’s statsrun by hand in the hope that I can track
down what’s causing this. This means you can expect tomorrow’s stats to be
late. Additionally, I will at some point correct the database to reflect what
should have happened in the first place. This will probably change a few team
rankings, but I don’t expect it to be major, and more importantly, this means
that the data will reflect what should have happened and that everything in the
database will be in sync again.

More info once I figure out what’s actually broken.

« Newer PostsOlder Posts »