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.

2006-01-17

dbaker [17-Jan-2006 @ 22:12]

Filed under: clients,keyservers,proxyper — dbaker @ 22:12 +00:00

:: 17-Jan-2006 22:12 GMT (Tuesday) ::

Hi, folks.

As Bovine announced 18 months ago in this plan entry:
http://n0cgi.distributed.net/cgi/planarc.cgi?user=bovine&plan=2004-06-28.08:48
we are shutting down the *.v27.distributed.net DNS entries and finishing the
migration to v2.9 clients. All v27 DNS entries now point to 127.0.0.1 in order
to avoid problems in some of the older clients if the DNS failed to resolve.

All current clients should already be using the *.v29.distributed.net servers,
so this should not impact any clients or proxies. If you haven’t upgraded your
client or proxy software recently, I recommend visiting:

http://www.distributed.net/download/clients.php for clients
http://www.distributed.net/download/proxies.php for proxies

Thanks for your contribution.

2005-09-13

bovine [13-Sep-2005 @ 16:54]

Filed under: keyservers — bovine @ 16:54 +00:00

:: 13-Sep-2005 16:54 GMT (Tuesday) ::

Last week we added a new Aussie keyserver, located in Brisbane.
Clients have already begun to automatically connect to it and it
is performing great so far.

Our secondary webserver (one of two servers that host www.d.net) is
currently offline. Since all of the content it was hosting was
mirrored, this should not have much immediate impact on us. We’ve
adjusted our load-balancing to exclude it, although there may be some
delays until the DNS changes fully propagate. (That machine had been
online for nearly 8 years and would have had an uptime of 858 days at
the time it went offline.)

2005-05-17

bovine [17-May-2005 @ 02:40]

Filed under: keyservers,stats — bovine @ 02:40 +00:00

:: 17-May-2005 02:40 GMT (Tuesday) ::

There was some unexpected server hardware downtime today, which has
led to some backlog accumulating and a delay in the start of today’s
daily stats processing. We’re currently processing the backlog right
now and hope to catch up within the next few hours. It is not
expected that any significant amount of work was lost, due to the
buffering nature of our network.

However please be aware that the statsrun for May 16 (once it has
finished processing) may be a little low, since most of the backlog
will be counted in tomorrow’s stats.