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

[Skip Guenter]

Just figured out something else:

At these large values something else is happening.  If I logon, start 
boincmgr and the close boincmgr boinc-client also stops!  I've got to 
assume that what's really going on here is that I'm starting 
boinc-client via the boincmgr so the script is doing something else via 
the "already running" check.  IF this is what's happening then it wasn't 
starting after the sleep delay but was starting because I got logged on 
and started boincmgr. 

I don't see how to tell what started boinc-client in 
/var/lib/boinc-client/stdoutdae.txt.  I'm gonna try moving the 
"log_begin_msg" around.

I was able to this even down to a value of 20.  At a value of 15 the 
script had started boinc-client. 

I just re-booted a couple more times with sleep 15 and was not able to 
start boincmgr b4 the script had started boinc-client.

Given this, I'm now thinking the value s/b in the 10~15 range.

BTW, did all this on my main desktop which is Ubuntu v9.10, x64
v10.6.58 from PPA
SCHEDULE=1 in defaults

Skip Guenter wrote:
> 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.
>>   
>

-- 
"La carencia de recursos no debe de ser impedimento para que un niño tenga acceso a la tecnología."