In article <dcb51c$7g0$1@green.home>,
John F Hall <jfh@avondale.demon.co.uk> wrote:

In article <73182$42e8e099$82a1d3bf$9377@news1.tudelft.nl>,
Patrick Vervoorn  <patrick.vervoorn@NOSPAM.perihelion.demon.nl> wrote:

[snip]

I also have "boinc" as a user that runs the boinc and seti programs, and
I login as boinc to monitor what's happening, but the program is started
by root using, as I said:  su boinc -c "...".

The same scripts without that would run as the normal user, though it
might be a good idea to include a "nohup" so that it isn't stopped if you
logout.  You could also 'if [ "$UID" = "0" ] ; then ...' or similar to
choose the right start-up command :-).

I've received your emails, thanks for that.

[snip]

I'll increase it, and see what happens. :) If I see significant delays in 
returning results, I'll modify my invocations of BOINC with the 
"-return_results_immediately"-flag.

If you try it with and without you'll see the difference.

Well, things seems to be like usual:

2005-07-28 19:50:44 [SETI@home] Computation for result 
20se03aa.25880.16128.615894.191_0 finished
2005-07-28 19:50:44 [---] schedule_cpus: must schedule
2005-07-28 19:50:44 [SETI@home] Starting result 
08fe05ac.6021.27024.290910.249_2 using setiathome version 4.02
2005-07-28 19:50:46 [SETI@home] Requesting 47041.55 seconds of work
2005-07-28 19:50:46 [SETI@home] Sending scheduler request to 
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2005-07-28 19:50:46 [SETI@home] Started upload of 
20se03aa.25880.16128.615894.191_0_0
2005-07-28 19:50:48 [SETI@home] Finished upload of 
20se03aa.25880.16128.615894.191_0_0
2005-07-28 19:50:48 [SETI@home] Throughput 25925 bytes/sec
2005-07-28 19:50:50 [SETI@home] Scheduler request to 
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2005-07-28 19:50:51 [SETI@home] Started download of 
20se03aa.25447.20065.479830.232
2005-07-28 19:50:57 [SETI@home] Finished download of 
20se03aa.25447.20065.479830.232
2005-07-28 19:50:57 [SETI@home] Throughput 65584 bytes/sec

No delays in sending back results yet, and I'm running BOINC without any 
special command-line switches. But as you yourself commented in your 
email, you were running an older version, so perhaps this is something 
which was changed (fixed? :) in the newer version.

I'll keep an eye on it, but so far, I like it: I have a load of WU's in 
the cache, so even if the netwerk/servers at Berkeley go out again, I'm 
(hopefully) set for a few days...)

[big snippage]

OK.  I'll leave you to digest them and see what you need to do for your
system.  I assume you're familiar with shell and bash scripts.

I think I'll manage, but as commented earlier and above, the current setup 
seems to be working quite ok for now.

Regards,

Patrick.