Sierp base 16 - team drive #1 - Page 11

em99010pepe · 2008-03-03, 07:45

Quote:

Originally Posted by gd_barnes

The fact that I thought we had tested to 130K tells me that there is some communication issues that can't seem to be resolved after several attempts amoung the 3 of us.

You are wrong once again. What several attempts?
I closed the server on 01 Mar 08 because last result in was on 02/28/08 07:47:01, so I waited two days for some activity. BTW, last results since 02/25/08 were from the same user.

mdettweiler · 2008-03-03, 07:49

Quote:

Originally Posted by em99010pepe

You are wrong once again. What several attempts?
I closed the server on 01 Mar 08 because last result in was on 02/28/08 07:47:01, so I waited two days for some activity. BTW, last results since 02/25/08 were from the same user.

Oh, I forgot--when tnerual took his proxy off the Sierp. server for the last rally, the Sierp. server was thus left with no users. I see now.

Carlos, if you'd rather not run the Sierp. server any more, now that it's shut down, how about you zip up its LLRnet server directory, and send it to Gary and I so that somebody else can run it?

em99010pepe · 2008-03-03, 08:15

The server is up and running....
I prefer to run only one server independently of the project.

mdettweiler · 2008-03-03, 17:43

Quote:

Originally Posted by em99010pepe

The server is up and running....
I prefer to run only one server independently of the project.

Okay. How about as soon as everybody's done drying the port 100 server, we dry the Sierp. server?

mdettweiler · 2008-03-03, 20:15

I just started up an LLRnet client on the Sierp. server now, and was shocked to find the following k/n pairs in my workfile.txt:

6663 491036
2908 491064

Those two k's aren't supposed to be in the drive, yet somehow it seemed they were included!

Gary, maybe you should mark those two k's (and presumably 10183, too) as part of Drive #1 on the Sierp. Base 16 page (right now they're marked as unreserved and at n=100K)?

gd_barnes · 2008-03-03, 22:29

Quote:

Originally Posted by Anonymous

I just started up an LLRnet client on the Sierp. server now, and was shocked to find the following k/n pairs in my workfile.txt:

6663 491036
2908 491064

Those two k's aren't supposed to be in the drive, yet somehow it seemed they were included!

Gary, maybe you should mark those two k's (and presumably 10183, too) as part of Drive #1 on the Sierp. Base 16 page (right now they're marked as unreserved and at n=100K)?

Carlos and Anon,

It appears I goofed for files n>120K. I needed to pull those k's out and didn't. They were OK for n=110K-120K.

Carlos, would you mind stopping your server and loading a new file that I will give you a link to shortly? Anon, could you test something else until we get the file reloaded?

Although it will require doing some work over again, the easiest thing on Anon and me and anyone else would be to delete the file currently in the server and to load a new one.

I will put a couple of machines on it here after you reload the file to help catch it back up.

Sorry about that.

In the mean time, if you have results for n=105.3K-120K, that would help confirm things.

Thanks,
Gary

mdettweiler · 2008-03-03, 22:36

Since we'd have to go back to n=120K anyway, why don't we simply stop the Sierp. server right here and now? I'm guessing that there shouldn't be any gaps below n=120K (there's been plenty of time for missed k/n pairs to have been recycled by the server), but I'd of course check it anyway when I process the results.

That way, we won't need to expend a hefty effort to get the server dried out.

Thoughts? Suggestions? Rotten tomatoes?

gd_barnes · 2008-03-03, 22:45

Quote:

Originally Posted by Anonymous

Since we'd have to go back to n=120K anyway, why don't we simply stop the Sierp. server right here and now? I'm guessing that there shouldn't be any gaps below n=120K (there's been plenty of time for missed k/n pairs to have been recycled by the server), but I'd of course check it anyway when I process the results.

That way, we won't need to expend a hefty effort to get the server dried out.

Thoughts? Suggestions? Rotten tomatoes?

Sounds good to me. Carlos, if you're in agreement, please send the LLRnet Sierp results to Anon and you can stop your Sierp server.

I have files prepared now for n=120K-130K with the 3 k's removed, both in one big chunk on the offhand chance that you'd like to continue the server, and in 2K chuncks to put back into the drive.

Sorry folks...hopefully it works out best for everyone here. Assuming that we close the server, I'll reserve the first range, n=120K-122K, since that will be a fair amount of duplicate effort at this point.

Gary

em99010pepe · 2008-03-03, 23:34

2008-03-03, 08:15	#113
em99010pepe Sep 2004 2830₁₀ Posts	The server is up and running.... I prefer to run only one server independently of the project. Last fiddled with by em99010pepe on 2008-03-03 at 08:17

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Sierp base 6 - team drive #3	gd_barnes	Conjectures 'R Us	373	2014-06-11 21:31
Sierp base 63 - team drive #5	rogue	Conjectures 'R Us	146	2011-04-20 05:12
Sierp base 3 - mini-drive II	gd_barnes	Conjectures 'R Us	46	2009-10-26 18:19
Sierp base 3 - mini-drive Ib	gd_barnes	Conjectures 'R Us	43	2009-03-06 08:41
Sierp base 3 - mini-drive Ia	gd_barnes	Conjectures 'R Us	170	2008-11-11 05:10

2008-03-03, 20:15	#115
mdettweiler A Sunny Moo Aug 2007 USA (GMT-5) 14151₈ Posts	I just started up an LLRnet client on the Sierp. server now, and was shocked to find the following k/n pairs in my workfile.txt: 6663 491036 2908 491064 Those two k's aren't supposed to be in the drive, yet somehow it seemed they were included! Gary, maybe you should mark those two k's (and presumably 10183, too) as part of Drive #1 on the Sierp. Base 16 page (right now they're marked as unreserved and at n=100K)?

2008-03-03, 22:36	#117
mdettweiler A Sunny Moo Aug 2007 USA (GMT-5) 3×2,083 Posts	Since we'd have to go back to n=120K anyway, why don't we simply stop the Sierp. server right here and now? I'm guessing that there shouldn't be any gaps below n=120K (there's been plenty of time for missed k/n pairs to have been recycled by the server), but I'd of course check it anyway when I process the results. That way, we won't need to expend a hefty effort to get the server dried out. Thoughts? Suggestions? Rotten tomatoes?