The fact that Boinc no longer consistently restarts after receiving a quit RPC is literally a showstopper, although it is not insurmountable and it does require external intervention to produce. If one has a Java program that scans all the computers on the network to make sure that all of them have all possible cores occupied, discovers one that does not have a core busy, issues it a quit RPC, Boinc does not restart the science clients, the time is 11:37 PM, one goes to bed at 11:00 PM, then Boinc on that computer is essentially down all night, still of course using electricity, though only about 1/2 as much as when the clients are all running. These numbers are realistic.
After a quit RPC, Boinc/BoincMgr take indeterminately one of three possible courses of action: 1) Both restart normally, as do the science apps. 2) Boinc and the science apps restart, but BoincMgr does not connect to Boinc. No real harm is caused, but one does have to log into the remote computer, click on the Boinc icon in the system tray, and either click on exit (and then restart BoincMgr and Boinc from the Start Menu) or click on Open Boinc Mgr .../ Advanced / Select Computer and enter the computer name and password. This latter is the most common mode of failure; oftentimes BoincMgr posts a balloon saying that the password is incorrect. No matter how many times one enters the password, it is still incorrect. However, entering the correct computer name always results in BoincMgr prompting with the correct password. 3) There is no Boinc in core for BoincMgr to connect to, so the computer is effectively down until one notices the outage. This behavior is typical of version 6.6.38. Charles Elliott -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rom Walton Sent: Monday, October 26, 2009 2:10 PM To: BOINC Alpha Mailing List Cc: [email protected]; [email protected] Subject: [boinc_dev] BOINC 6.10 release Well folks, It looks like we are coming up on 6.10 being ready for a public launch. Does anybody know of any show stopping issues in the 6.10 client that should keep us from releasing? A showstopper is a bug that causes the client software to crash, the client to overload the computer, or trash the work queue. At this point bad bugs that also reproduce on 6.6 or 6.8 should be reported, but more than likely will not stop the release. As always we will follow up with bug fix releases for 6.10. ----- Rom BOINC Development Team _______________________________________________ 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. _______________________________________________ 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.
