[FaD] 123b Beta Testers,

[Cowboybooter]

Originally posted by THINK at FaD Forums,

Posted: Wed Jan 28, 2004 12:08 pm Post subject:

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

Build 139 is now available for beta test members. This needs to be downloaded manually by deleting v123b.end and the pushing the receive button in the job queue server window.


<Edit1: when it says 'waiting 5mins for prog to close, leave it - it can't tell the time!>

<Edit2: I couldn't find TT's original thread to put this in, sorry!>

:)

Bob

[Nukes]

Is this the one that gave you no points for big jobs?

[Win2Kuser]

I think that was only the Linux beta client Nukes.

Not 100% sure though...

[Cwizard]

Originally posted by Nukes
Is this the one that gave you no points for big jobs?

Yes, this beta lost me about 20K worth of points by posting 0 points. :(

I just shut the machine down after that happened and then the software started claiming corrupted files.

Cwizard

[Nukes]

It doesn't seem to update the think.tip and server.tip anymore either.

[Cwizard]

Does anyone know how to shutoff the beta option with isetup. I just reinstalled and it started grabbing the beta again. :eek:

Cwizard

[Win2Kuser]

Originally posted by Cwizard
Does anyone know how to shutoff the beta option with isetup. I just reinstalled and it started grabbing the beta again. :eek:

Cwizard

Yup, under the projects tab, make sure there is NO tick in Beta

:)

[Cwizard]

Originally posted by Win2Kuser
Yup, under the projects tab, make sure there is NO tick in Beta

:)

Uh, where is there a project tab in the Linux client?

PS. The problems with the Linux client continue to escalate. It is not recognizing the second processor. Isn't the correct command for think.env:

think_processes=2 ?

I can't seem to get a command list up.

[Win2Kuser]

Ah, in that case then, I haven't got a clue :bunny: sorry.

You could always pm BitSpit, I'm sure he won't mind, he has a whole herd of linux machines and always get very involved in Beta clients.

[Nukes]

I think you need to do:
THINK_PROCESSES=2
Not sure though, but afaik they all need to be in capitals.
However, I don't think thats how you're meant to do it:

Originally posted by THINK on the FaD boards
The setup for multiple CPU is trivial with Find-a-Drug but not automatic. You need to increase the GHz setting in the setup program to the total CPU power and run two copies of THINK (its not multithreaded). The best way of doing so is by editing think.lgo in the think folder to repeat the think.exe line. If you subsequently re-run setup, there will be occasions when you need to re-edit think.lgo (sorry).
I don't think you can 'shut off' the beta in Linux (like methedology) but if you can you would do:

./isetup -projects -Beta+Cancer
You have to add in the team, email and username bits as well.
Also, I found a solution to my problem;
Edit think.env and add:
THINK_KDFOLD=YES
Don't know what KDFOLD is, and don't care, but it works.

[Twinkletoes]

Originally posted by Nukes
Don't know what KDFOLD is, and don't care, but it works. :ROF: :rofl: :ROF:

[Nukes]

yar, you go ahead and laugh. Just 'cos you don't know what a PCI slot looks like. :lol:

[Cwizard]

The second processor finally kicked in. I had already edited the think.env with the Think_processes=2 and restarted several times but it kicked in on it's own. Really strange.

Will watch it as this thing has more bugs than an Orkan commercial. :o

Cwizard

[Cowboybooter]

TT - PCI = Partitioned Computer, Innit! BTW,

:lol:

Bob

[Nukes]

:lol:
It is, Honest :| None of that Peripheral Component Interconnect stuff here :D

[mickwish]

KDFold (http://www.kdfold.com/) is a monitoring app for DC's, Nukes. THINK has coded to allow THINK to report stuff to KDFold.

I tried using KDFold with FAD once, but it didn't do anything for me. :rolleyes:

Originally posted by Cwizard
Will watch it as this thing has more bugs than an Orkan commercial. :o

No idea what an Orkan commercial is, but it sure has more bugs than a Petri dish in the lab!! :eek:

Cheers
Mick

[Nukes]

I'd hope the labs would be kept clean enough to avoid that sort of thing. You're playing with Cancer or anthrax and suddenly a nasty bug comes along :eek:
:lol:
Yeah, I had actually found that page, its one of the first ones google threw up, but I've no reason to try it. My current system works fine.

[Win2Kuser]

Ah the fun I had at school once pupils realised what type of Jelly is contained in a petri dish...

My surname is Agar :rolleyes:

:D

[BitSpit]

Well, this Linux beta is fun. :rolleyes: The new THINK simply will not run for me. Segmentation fault on every single machine every time I try to run it. At least the build 139 SERVER will upload results now. This means the working setup for me is THINK 1.21L and SERVER 1.23b build 139. Here's the process I have to go through to get things working right now:


killall think
killall server
rm v123b.end
./server -receive
./loader
Hit Ctrl-C because at this point loader hangs but it does get the files mostly updated
Telnet to armadacommand (the server for the whole thing)
cd /usr/bin/fad
cp think /home/fad/NODENAME/task_1
logout of armadacommand
chmod 755 fadsetup
./fadsetup -list
./loader (loader finally works for me. Go figure)


Now that I've gotten this figured out on one node, I have to do it on all the others. Eventually I'll get around to all of them.