hi Christian thanks for your reply.
I will look at the relevant threads on the devs forum, but I don't initially see how the scenarios you describe apply to either of my situations. For one thing the CLI (Debian Jessie) boxes do not have virtual network devices, and have exactly one network card, which must be running for the initrd to exit to systemd (because they are diskless, initrd needs a working network to find its nfs root file system). This is a fairly simple boot process which I think I understand (base system, sshd, and boinc; nothing else). I am not so confident about knowing what goes on when the Mint boxes boot up - virtual box is mentioned but I believe only to say that various modules are not being loaded as we are not in a virtual environment. But thanks for the tip, it is something I must check out I do see the issue if huge clusters generated new host records every time they booted up: I understand now the devs motivation for moving away from having a brand new cpid on each boot. I see why my changes are therefore not ones that you would want in the official release. I certainly would not claim to "understand" .deb packages, but I do know enough to add to an existing post-install script. As for the network booting machines, I already have a script running in the initrd that sets up the boinc directories ready for the client to be started. At present I give the client exactly the same files it gets from the post install trigger, plus an account_....xml file so that it thinks it is already connected to a project. Sudden thought: will the client get confused by having an account_....xml file but no client_state.xml ?? I have just realised I am giving it a combination of files that would not occur in normal use, so even though I believe that SHOULD work, it is a corner case that may not have been tested in development... you said > > The occasional problems you see might stem from the fact that the > network may not be working at the time when the BOINC Client tries to > get the MAC address and uses a random host-CPID instead. > > random would work for me, as it would be different each time. It must default to a _deterministic_ host-CPID to create collisions with older hosts. The suggestion on the Prime Grid forum was that it hashes the data directory with the MAC address, and that if the MAC is missing for any reason then, as the data directory is constant you always get the same hash.... Thanks for the links to the post on the dev forum, and to the formal description of the hash, I am off to read them now warm regards River~~ _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
