S@H mandatory v3.03

[Hellburner]

I just stopped by the S@H FTP site and only 3.03 clients are listed except for the OSX beta client.

My guess: any minute now. or already happened?

 

[Poof]

Well if my alpha linux client isn't due until almost the end of next week, then it better not be "any minute now"...

And I want to know what the difference is between "No upgrade client at this time" as opposed to "No upgrade client available"... I have a Sparc Linux box crunching...

I wish they would stop bullsh1tting and just do like they did last year and post a list of "Clients to be obsoleted". :|

 

[Hellburner]

Just stopped by usenet and it looks like it's happening.

Poof, I noticed a couple Sparc clients posted yesterday, don't know if they're your flavor.

 

[BadThad]

hummmm...as of today all of my v3.0 winNT cli's are working fine. Nothing rejected yet.

 

[Hellburner]

Well, I've been testing my clients. The 3.0 GUI was a no go, Setiq dumped and loaded 3.0 wu's without a problem and a direct connect with the CLI 3.0 gave the message that it wouldn't run but it then proceded to download a wu. ???

 

[Poof]

Hellburner - my Sparc client (linux) says "No upgrade client available". If they are obsoleting it, then dammit, they should come right out and say "No upgrade client will be available. This platform is obsolete" or something... Don't just leave it hanging out there... :|

And since it's a libc 5 machine (running Red Hat 5.2 for sparc), I just checked and won't be able to run RC5 on it unless I upgrade its libraries to libc 6... (the drive is only 250Mb so that would be tricky to do.... )

 

[PhotoLenny]

Dumped wu's this morning, got a message that I need to upgrade the client, but the wu's didn't get rejected ------ I upgraded, and things have slowed down considerably.

 

[Michael]

The message I received was that a mandatory upgrade was coming, not that it was needed immediately. I will change over my home fleet this weekend. They all go through SETIQ which did not generate a message and I'm being credited for my 3.0 WU's.

Less WU's isn't a problem as everybody will be the same. It will be harder to move up in ranks, however, and the number of extra WU's produced per day will go down and we're trying to go up against older WU's.

My 600 mhtz Dell laptop has been chewing on one 3.03 WU for 14 hours and is only 50% through.

I do SETI because I believe in the cause. More science is better.

Michael

 

[Robor]

I just retired one of my ships. She's an old dog (P233/64MB) and the 3.03 client isn't going to do well on her so I decided to give her an early retirement.

I've got 4 3.0 CL clients at home and 31 3.0 CL clients at work that need to be upgraded to the 3.03 CL client. Looks like someone's going to be doing some free overtime work this weekend.

Rob

 

[Poof]

I just retired one of my ships

Just one? I got a pile that will need to be retired including a P120 (currently 44 hrs/WU with 3.0), a P200MMX (currently 28hrs/WU with 3.0) and a K6-2/333 (currently 35hrs/WU with 3.0).

And it looks like they may retire my little Sparc IPX (currently 153hrs/WU with 2.0)!
If they do, I'll lose my SETI Hall of Fame cruncher... (unless I put my 486 back on it again... )

 

[Jani]

Any chance use those machines in other competitions?

 

[Poof]

Oh sure - 2 of them are already doing folding and I'll move the others to RC5. My 486 is doing RC5 and I was about to switch my alpha over to RC5 if the seti folks decided to have the audacity to retire my alpha linux client (which apparently they didn't...). I already have a NetBSD K6-2/450 running RC5 after they retired my NetBSD client last spring and my K6-2/500 is folding and running RC5 too...

 

[Robor]

Poof: You've got a client that takes 153 hours per WU? :Q At that rate, how can you even tell if the client is stalled! Man, that's gotta put a dent into your average CPU time!

Seriously though, I think we're going to see a lot of SETI users switching older machines over to other projects due to the 3.03 client. I can't myself. I can't start another DC project on any of my work machines because I don't want to cause any problems. I'm currently managing 31 SETI clients but they're all CL clients and are hidden so they don't cause any problems. Maybe a little more network traffic but not much until the dump and that happens at 3AM when the building is empty anyway.

I'm NOT looking forward to all of those client upgrades!

Rob

 

[Fardringle]

If you're interested, those K6-2's would be MUCH more effective running OGR with the version 463 client! (My K6-3+ 550 does almost the same amount of work as a Celeron 700.. )

 

[Assimilator1]

Hmm odd ,my 2 home ships are running v3.0 CLi & getting WU's via SETIQ ,I've had no update message yet of any kind.I know that SETIQ has the version info inside get_work_unit.txt.
What's going on?

 

[JWMiddleton]

I just got home from Shreveport for the weekend and dumped a SetiQ load with no problem or message. I suspect that there is no way to get SetiQ to display a message other than the one that says the WU was rejected as duplicate. We've already read where the author of SetiQ has been in touch with S@H HQ and they asked him to make to make some changes in addition to the support for 3.03. Thus, I suspect that they will give him a little time to get done before the converion since a lot of WU's come from SetiQ users. I check daily to see if Ken's site is back up.

Today I got the following new message:

Well it's still "the earlier part of January" but it's going to pass me by. I have to leave town for 10 days and will not be able to post the new version until the end of the month. But I do have a new version working. It's a re-write and for some reason much more robust :^). The basics, plus some, are functional and I am running it right now on my limited configuration.... but I don't have time to complete the some important UI (yes the new one has one) details and documentation verbiage (not that I write anything understandable anyway :^). When I get back I think it will only take a few more days before I can post a beta that should be usable.

If anyone has the time & desire to create a couple of graphics for me, I would appreciate it. I need a program Icon (32 x 32) and a toolbar Icon (16 x 16), and maybe one nifty graphic for the web site around 100 x 150 (width, height) or so.

Also while I'm asking for help, I was wondering if anyone has a graphic of the sky and how to convert Ra & Dec to a point on the picture. If so, I can incorporate that into the program as well (but it's not important enough for me to go to the library to figure it out... so if someone can show me how to do it I can code it).

------------

So, it is still weeks away...what will SETI HQ do?

 

[Assimilator1]

Thanks for the info ,I guess I should read his site from time to time!

 

[Sukhoi]

Hmm, I'm still running the 3.0 CLI and 3.0 GUI ok. I haven't dumped any 3.0 GUI results yet though, because I just installed it last night to replace the 2.04 GUI.

 

[Poof]

Poof: You've got a client that takes 153 hours per WU? At that rate, how can you even tell if the client is stalled!
Man, that's gotta put a dent into your average CPU time!

That's why it crunches under its own user account. I keep a "permanent" telnet session to it from my main workhorse notebook. And since it's a 2.0 client, it displays the %complete progress info by default. But it crunches faster than my 486 did with the 2.x client (which took 175 hrs/WU with 2.x and > 400hrs with 3.00. It would probably take about 800 hrs w/3.03)!

So if anyone wishes to accuse me of only being in the project "for the stats"....

This of course doesn't mean that I'm not gonna build my new Duron 700 system and try to OC it to 1Ghz this weekend...

And JWMiddleton - it would be interesting to see if SETI@home waits for Mr. Reneris, although I having a feeling that a final cutover may happen by the end of the month whether he's ready or not (which will give them time to get some of the remaining clients out and give a grace period of about 2 weeks). I think the hostname work-around for the current version of Setiqueue should work okay though.

Not sure why Ken's decided to try to re-write the entire app right now, right in the middle of what I'm gonna dub "THE PURGE".

I'm a linux freak and I don't need no graphics for Setiqueue

The console is just fine the way it is and gives me everything I need. To me, the app is a WU server. You don't need fancy dancy graphics if its primary function is to feed your machines. This is why windud keeps failing - making everything graphical, which inturn forces it to get all entwined in and gummed up in the broken kernel, which tends to lead to crash city...

 

[Assimilator1]

Well I dumped results from a GUI v3.0 & CLi v3.0 client this morning via SETIQ (for my brother) ,still no problems .

 

[JWMiddleton]

Poof: With the additonal delay by Reneris, not sure what Seti HQ will do...

It sounded to me like he was working on a GUI rather than the console and decided to finish it rather then patch the console when "The Purge" hit.