Wait for slow network startup

[Dagorath]

This issue was brought up in this thread. Summarising, the user starts BOINC client as a daemon during boot on a Fedora 9 system that apparently brings up the network rather slowly. When BOINC client starts it finds no network available. Putting a 15 second delay in the system startup scripts to delay starting the BOINC daemon fixed the problem for the user.

I imagine BOINC client, when it starts, checks if the network is available before proceeding. Perhaps the OS (Fedora 9) is reporting incorrectly? Perhaps the OS reports correctly but BOINC times out too quickly?

[Nicolas]

Already possible. Set <start_delay> in cc_config.xml

[Dagorath]

Setting <start_delay> in cc_config.xml delays starting science apps which is not the preferred solution.

[Nicolas]

Sorry, my misunderstanding. I thought start_delay made the client do absolutely nothing until the delay finished.

<start_delay> only delays the client starting science apps. You want to limit the client accessing the network. So, good to reopen ticket :)

[mjakubicek]

In my point of view the problem cannot be solved by waiting on startup: the real trouble is that BOINC cannot use any networks newly available after its startup. This regards not only slow DHCP responses but mainly wireless connections or any connections which indeed come up when BOINC is already running.

From what I know this should be solved in BOINC 6.4 by the asynchronous GUI RPC. I truly do not understand how GUI (!) RPC connections are related to this (isn't it a problem in the client itself?), but I hope I'm just wrong in this and it will be solved soon.

[Nicolas]

The new asynchronous GUI RPCs won't stop the client from attempting network access during startup. They will stop the GUI from hanging while the client is busy, for example, trying to access the network.

[Nicolas]

fixed link to forum thread in ticket description.