sleep x delay in /etc/init.d/boinc-client START

[Skip Guenter]

Daniel,

OMG and give up 21 seconds of valuable crunching time!  Daniel you could 
be banned from the Church of BOINC for such heresy!  You can only hope 
that the Grand Inquisitor doesn't read this.  ;-) 

OK, OK, on a slightly more serious note... At 30 secs I'd wonder if 
users will get signed on, start boincmgr and get the not-connected error 
because boinc is still starting up?  Then there would be a rash of 
posts/bugs on that.  I'd suggest something smaller if you think this is 
even a possibility.  Maybe it's not.  Tell ya what I'll set mine to 30 
and see if it can happen as I was saying or not and let you know.

..................  Update following ..............

With add-ons Compiz & Gkrellm starting at login but not much else:  I 
started at 30 and worked down to "sleep 20".  At sleep 20 I can restart 
the computer, get logged on and start boincmgr just as boinc client is 
starting to crunch (I can tell from my gkrellm display of CPU load).  At 
values >20 I can beat it to the start but not by enough that boincmgr 
will have given up on connecting and give the "not connected" message.  
I just have a blank screen for a longer than normal.  At "sleep 30" it's 
a quite noticeable delay and at "20" it's barely perceptible. 

So my conclusion would be the max value s/b 20 seconds and min value 6 
seconds.  I'd go w/ 19 or 20 if I were in your shoes.

I know, this is a pretty esoteric discussion but as long as it doesn't 
take much time from those of you who can deal with bigger issues, let's 
get it right 1st time out.

l8r, Skip

pkg-boinc-devel-request at lists.alioth.debian.org wrote:
> ------------------------------
> Message: 2
> Date: Tue, 03 Aug 2010 18:22:17 -0000
> From: Daniel Hahler <launchpad at thequod.de>
> Subject: Re: [Bug 587426] Re: No GPU found
>
>   
>> PS:  Use "sleep 9" if machine is slow getting thru gmd start or if you
>> wanna be really, really safe that it'll not start until after gdm for
>> remote, unattended reboots.
>>     
> Just for info:
> I would just use "sleep 30" and be done with it: it's not worth to tweak
> this from 5-6 to 9 seconds, when it's not time critical.
> When we would use this kind of workaround, it would be rather generous
> in this regard.
>   

-- 
"A child's exposure to technology should never be predicated on an ability to afford it."