Phew, a new record. 3 1/2 hours to round trip this mail list.
Is it just this project, or has the whole net gone to heck this past weekend?
Our local corporate computer security czar was busy today filling up his
message board with postings of hackers this week attacking Japan, The Well,
and va
Clark B. Wierda wrote:
> I
> thought I was contributing to a process involving mature individuals. I'm
> sorry to see that this is not the case.
>
> I will remove all my systems from the search after the current LL tests
> complete.
Clark,
I've been member of quite some organizations of sever
Phew. something is stinky here.
http://entropia.com/
503 Service Unavailable
--
--
This server is too busy right now. Your request would have exceeded the
maximum number of simultaneous connections set by the operator. P
John R Pierce wrote:
> agreed. I discovered most of my HTTP clients at work were busy retrying ever 2
> minutes and not getting any work done today.
The next version (16.x or whatever) should default to 240 minutes instead of 2. As
long as the server is down less than the days of work to get (mi
Guido Stolz's statistics for Primenet (but not for GIMPS) are
also empty.
If the server is going to be gone for a long time, we probably
should back off our retry timers to only retry every 5 hours or
so. That way, we won't increase traffic for entropia.com until
this is straightened out.
Hopef
On Sat, 19 Sep 1998 13:25:20 +0200, Henk Stokhorst wrote:
>The next version (16.x or whatever) should default to 240 minutes instead
>of 2. As long as the server is down less than the days of work to get
>(mine is at 7) it will work fine. Also I would like to be able to set it
>to a maximum o
I always default mine to 300 min. If it happens to complete while
I'm not home I don't want it wasting time trying to contact Primenet
when there is no chance. I usually start checking it manually
everyday when it starts to get close to completion. With these
5 mil+ numbers that is a lot less oft
>> agreed. I discovered most of my HTTP clients at work were busy retrying
ever 2
>> minutes and not getting any work done today.
>
>The next version (16.x or whatever) should default to 240 minutes instead of
2. As
>long as the server is down less than the days of work to get (mine is at 7)
it
>w
On Fri, 18 Sep 1998, Ocrat Subscriber wrote:
>>> the GIMPS server
>>> machines, which [the FBI] would be entitled
>>> to by many grounds, weren't confiscated.
> The PrimeNet Server? I hope this was a joke in
> poor taste. There are no such grounds for the
> FBI to take any such action. They ma
At 10:45 PM 9/19/98 +0300, Jukka Tapani Santala wrote:
>Also consider the fact that the newspaper articles said the search
>warrant (By the way, any change of getting it scanned out for a web-site
>on the issue?
I have it on a web site, but I have not published the URL yet.
I only posted the f
Henk Stokhorst wrote:
>The next version (16.x or whatever) should default to 240 minutes instead
>of 2. As long as the server is down less than the days of work to get
>(mine is at 7) it will work fine. Also I would like to be able to set it
>to a maximum of 720 minutes.
I don't see any reason
John R. Pierce wrote:
>ANYone who's running a primenet client should immediately go into the menus,
>Options / Preferences, and set the "Minutes between network retries" to about
>30 or 60.
I personally use 180 minutes. But okay, I'm not continuously connected to the
internet.
>With the 10's of
ANYone who's running a primenet client should immediately go into the menus,
Options / Preferences, and set the "Minutes between network retries" to about
30 or 60. With the 10's of 1000's of clients out here now, and with the
server offline for over a day now, we probably have 5000 clients all t
13 matches
Mail list logo
