SETI Driver Hanging!!!

[Larry Quinn]

This is starting to ****** me off....

I have my Best cruncher greet me with the RED UPSIDE DOWN RADIO TELESCOPE 2 days straight now...

This thing will spit out WUs every 2-3 hours...but when this happens....
Well you get the picture....it acts "Gone to Lunch"

What do I need to change to insure this unit keeps trying to send and recieve persistantly..(SP?)..

So far my only fix has been to open the "Seti Driver" and press "Transmit" manually..

I have the Auto Transmit is checked.
and "Yes" the network is "Live" on the internet.


And on another note....
Are there any tweaks to apply to push even faster???
I have 4 units in my SETI farm....
My slowest is a AMD K6-400...and man it could use some help...

The MB is an old ASUS TX97-LE runnning 83 MHZ *4.5

this unit could use some serious help...
but it was made from parts I had laying around..so what the hell...right???

thanks to all on the TEAM who respond!!!!


Larry

[SleepyKat]

are you caching any WU on your SETI Driver. Sometimes the SETI Server is out/down/busy... and SETI Driver will wait one hour and try after that , it sits there until you tell it to send.... I cache about 1 days worth on each machine so I don't fall too far behind those massive SETI farms ;)

[Larry Quinn]

no I don't do more than 1 WU at a time...

I've just read too many horror stories here about caching..

there MUST be a way to lower the check frequency to something lower than an HOUR!!

If there is traffic..or server down issues..I'd rather it re-checked every 5 MIN.

Larry

[SleepyKat]

caching is ok as long as you don't horde everything and send them back in one shot. I send my WU as I finish them. Haven't lost one yet.

[Larry Quinn]

so you keep wu's ready to be crunched in FRONT of the system....

Then send them back as completed.

ok..so if there is a prob...and the sys can't connect...
it just keeps crunching the new WU's.

When does it try to send the "Old Finished" units back??

You still want the system to keep trying to send in the WU...

HMMM....
What are the settings I need to put in to make this happen?

Larry

[SleepyKat]

As long as SETI Drive still has a WU working and ready to send, it will automatically send the ones it couldn't send before. If it finishes out all the WU and the server is still down, you will have to send manually when the server is back up. The only thing you need to do is set the number of cache you want. I like 3 because this one handles 3 WU per day

[Murphy]

I have problems with Driver too lately. I run it on my homebox and internet sharing box. When driver can't connect at the first times, the 'auto transfer' stalls, and only picks up again when I manually press 'transmit' (after pressing 'stop transmit').

That's why I cache for one week (server downtime berkeley). As long as there are unprocessed WU's my driver keeps on running.

Also I noted that a driver in 'normal priority' with a stalled transfer has VERY bad influence on system performance and internet routing. That's why I set all my boxes to 'low' priority, if not my boxes lose performance and hang after a while (more than 1 day transfer error)!

I know normal priority crunches faster, but I want my FTP to be always up.

Crunch on!