In article <d5egd3$g6l$2@tioat.ath.cx>, QoJ <justabitch@dodgeit.com> wrote:

John F Hall wrote:

Why not just let it run?  If it connects, it connects.  If it doesn't,
it sleeps for a while and tries again.  Big deal :-).

(I have mine set to a 4 days cache and invoked with
"-return_results_immediately".  That keeps it running and the cache
filling, though the cache has been half-eaten at times.  I did try
with
a larger cache, but I seemed then to be always the fourth return.)

Thanks for the tips but I don't have a clue what your talking
about.....sounds interesting.  I have a dial up and because of weather in
this area I don't leave my connection on unless I am here.

Ah, I have broadband, so it can try and connect whenever it wants.  I
don't know how it would work with dial up.  I believe you can allow it
to do the dialling (though restricting the times if you want).  If you
restrict it to using a link when you're connected you would need to
trigger the connection.  I'm not sure how that works.

When I had dial up I used a 7 day cache (for my computer, 20 work units)
and wrote my own Linux scripts that filled the cache and that ran the
Seti program.  But that was with "Classic".

The main difference with dial up is to use a larger cache of work units
so that you keep crunching even when you can't connect :-).

The recent delays were due to faults and everything now seems to be
running smoothly.  I assume there will be some more load balancing as we
users switch from Classic to Boinc, and there may be interruptions as
any external faults are found and worked round, and of course new faults
may happen.  But that can happen anytime.

-- 
John F Hall