Message boards :
Technical News :
Ups and Downs (Mar 22 2007)
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13832 Credit: 208,696,464 RAC: 304 |
But i'm sure it would cause problems for many of those that do have permission, but the users are unaware of what's running on their systems (ie most organisations). Grant Darwin NT |
1mp0£173 Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0 |
BOINC could be self-updating, but that also adds a "vector" for someone to install some sort of malware by "tricking" BOINC into updating. Remember there really isn't a central "BOINC" server by design. It might be a good idea though if BOINC had some kind of "uninstall" based on some reasonably distant date -- if BOINC hasn't been updated by Dec. 2011 for example, it'd stop working -- and move that date with each new release. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13832 Credit: 208,696,464 RAC: 304 |
At present when a new version is avaailble there is a message to that effect in the message logs when the server is contacted. All that needs to be done is when users need to move to a higher version, change the message to "A new version is avaiable & this version is no longer supported" & not allow any new work to be dowloaded. When the credits stop, i'm sure people will then start checking the message log to see what's happening. Grant Darwin NT |
Pooh Bear 27 Send message Joined: 14 Jul 03 Posts: 3224 Credit: 4,603,826 RAC: 0 |
There are some of these things in place, when version 3 was retired for version 4 of BOINC, they had a balloon type pop-up / messages sent to the software that it was outdated. BOINC is meant to be set and forget. Most of us like to keep updated, but some do not. Also there have been issues ever since version 5 came out on some Proxy authentication, so no force update has been allowed, because a lot of people would lose usability. I suspect the next force will come when the new data comes online, and they go to a newer version of everything. I could be wrong, but this is the feeling I have. Download the code, and read it yourself, it is after all open source. There are several different goodies built in. My movie https://vimeo.com/manage/videos/502242 |
n7rfa Send message Joined: 13 Apr 04 Posts: 370 Credit: 9,058,599 RAC: 0 |
Based on past messages....there are a number of users that will "panic" and claim that "the servers are down" or some such rather than look at their own systems. |
Grant (SSSF) Send message Joined: 19 Aug 99 Posts: 13832 Credit: 208,696,464 RAC: 304 |
Based on past messages....there are a number of users that will "panic" and claim that "the servers are down" or some such rather than look at their own systems. There's no cure for stupidity. Grant Darwin NT |
Chris Luth Send message Joined: 24 Dec 99 Posts: 21 Credit: 59,135 RAC: 0 |
Remember there really isn't a central "BOINC" server by design. Well, there isn't a centralized BOINC project server, but there is a centralized Web server: boinc.berkeley.edu. I see no reason why the BOINC software couldn't be hard-coded (to prevent someone from tricking the client) to contact boinc.berkeley.edu (which should be safe as long as nobody hijacks UCB's DNS) and self-update. But I'm not an expert, and maybe even then, malicious, evil, bad things can happen... The only downside I can see is that if the BOINC development team were to move away from Berkeley, all of the hard-coded BOINC clients wouldn't be able to receive new updates--unless UCB were generous enough to throw in a CNAME entry. Or, you could allow the BOINC updater to change its target domain, but then you run back into the problems of allowing malicious trickery. I don't know what the proper balance is, but all I'm saying is I don't see why it couldn't be done. |
1mp0£173 Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0 |
Remember there really isn't a central "BOINC" server by design. I started to post two different ways that this could be attacked easily, assuming that BOINC was self-updating -- and they're too easy. I decided not to post them, but the how-to is in the RFCs. I can also think of ways to make sure they never ever happen, but it's not simple, and it isn't the same as a project updating their science app. |
Odysseus Send message Joined: 26 Jul 99 Posts: 1808 Credit: 6,701,347 RAC: 6 |
Then how about a feature added to future releases that pops up a window that states NEWER RELEASE AVAILBLE - CLICK HERE TO DOWNLOAD. New versions are mentioned in the message logsâ€â€but of course some people don’t read them. Particular projects can go further; for example, recently I’ve been seeing messages like this from Pirates@home: Wed 21 Mar 20:55:45 2007|Pirates@Home|Message from server: Starting in 90 days and 14 hours, project will require a minimum BOINC core client version of 5.8.0. You are currently using version 5.4.9; please upgrade before this time. |
Chris Luth Send message Joined: 24 Dec 99 Posts: 21 Credit: 59,135 RAC: 0 |
New versions are mentioned in the message logsâ€â€but of course some people don’t read them. Well, a quick skim of my message logs (I read the initial startup sequence in detail and then skimmed through the rest) didn't reveal any notes that I'm using an outdated boinc (5.8.3, newest is 5.8.15). So, even those of us who do at least pay fleeting attention to the logs may not be notified. (What causes the notification? Since as mentioned earlier there's no central boinc server, notifications can only come via projects--and since projects are all independent, you can't guarantee that project managers will pass those messages along.) I just downloaded 5.8.15 cli for Mac OS X, but I'm a little leery of installing it--when I transitioned to 5.8.3 from 5.4.9, I had an absolute heckuva time getting the permissions set properly (the script screwed things up more than it helped, overwriting and creating weird users and groups and making my boinc files all be owned by user/group smmsp:smmsp instead of boinc_master and boinc_project). (In fact, one of the computers I've got boinc on still looks like it thinks everything is owned by smmsp--but the boinc install is working, so I'm not going to muck with permissions right now--fortunately the other Mac OS X cli install seems to be fine, and the other one is a GUI install.) I don't want to simply overwrite the boinc executable and the few other files in the download without running the permissions script, as they're not currently owned by boinc_master, but I really don't want to chance running the script (and I'm not sure what the proper owner/permissions settings are for each of the files in the cli download). As far as popping up balloons to warn of upgrades: bad idea. On three of my computers (all except the laptop), I'm not the only user. If a message were to pop up warning of an out-of-date BOINC client, my less-computer-savvy fellow users would probably freak out and think the computer was going to burn itself out or something. I still think a self-updating install would be the best solution, but short of that, a voluntary email notification system for updates would be nice--or the poor man's version--make one of these message boards admin-postable only (sort of like this forum, except with no non-admin replies allowed to keep traffic down) and then have people subscribe to it for updates. |
Aurora Borealis Send message Joined: 14 Jan 01 Posts: 3075 Credit: 5,631,463 RAC: 0 |
A possible a solution would be to put the new release advisory on the top border of the Boinc manager. That would not be as intrusive as a pop up. If it could be made to scroll so your eye would be drawn to it. Eventually there should also be a download/install new version button in the menu. |
Odysseus Send message Joined: 26 Jul 99 Posts: 1808 Credit: 6,701,347 RAC: 6 |
New versions are mentioned in the message logsâ€â€but of course some people don’t read them. I haven’t noticed nearly as many announcements as there have been versions, but opening this Mac’s stdoutdae.old file I see for example: 2007-02-05 08:14:34 [---] A new version of BOINC (5.8.8) is available for your computer 2007-02-05 08:14:34 [---] Visit http://boinc.berkeley.edu/download.php to get it. I have no idea how this notification works: just reporting what I’ve seen. I just downloaded 5.8.15 cli for Mac OS X, but I'm a little leery of installing it--when I transitioned to 5.8.3 from 5.4.9, I had an absolute heckuva time getting the permissions set properly (the script screwed things up more than it helped, overwriting and creating weird users and groups and making my boinc files all be owned by user/group smmsp:smmsp instead of boinc_master and boinc_project). I haven’t used a CLI version, but I recently installed v5.8.15 on my partner’s new iMac, and it looks like I may be in for some fun getting it to work with the Team MacNN optimized S@h app with regard to ownership of the files and their permissions. It’s already posting –5000 errors all over the place, presumably because it’s not being allowed to change the executable’s icon to the green dish. (I’m letting the host run stock for a while, to establish an RAC baseline.) The science app upgrade was nearly painless under v5.4.9 (service installation) on a similar iMac at work. Anyway, like you I contemplate installing a new version of BOINC with some trepidation. ;) |
KWSN THE Holy Hand Grenade! Send message Joined: 20 Dec 05 Posts: 3187 Credit: 57,163,290 RAC: 0 |
True, there's a message - but it is easy to miss, particularly if you don't watch the messages after hitting the "update" button on BOINC manager... perhaps if the message were in a different color, like green but not red, which should be saved for true errors... [edit to add...] A red message of this type should be used ONLY if there is an incompatability between the old version(s) and the new... ...and I agree with other posts on this thread that doing the "A new version is available & this version is no longer supported" is a bad idea; (unless the possibility above occurs...) and would generate a lot of traffic of the sort "why did my credits stop?" on the message boards - a lot of people don't seem to pay any attention to the messages tab of BOINC manager! . Hello, from Albany, CA!... |
Tisa Send message Joined: 8 Nov 01 Posts: 7 Credit: 53,314 RAC: 0 |
I'm running version 5.2.13 Can someone please direct me to the upgrade or do you have to just download the new version separatly? |
PhonAcq Send message Joined: 14 Apr 01 Posts: 1656 Credit: 30,658,217 RAC: 1 |
go to the boinc home page and download the current recommended virgin. It will replace your existing one. If this doesn't work, disable your existing version first and then try again. May this Farce be with You |
OzzFan Send message Joined: 9 Apr 02 Posts: 15691 Credit: 84,761,841 RAC: 28 |
go to the boinc home page and download the current recommended virgin. It will replace your existing one. Can everybody get a virgin? And what if you don't have an existing virgin to replace? (Man, is this a deal or what!?) |
1mp0£173 Send message Joined: 3 Apr 99 Posts: 8423 Credit: 356,897 RAC: 0 |
go to the boinc home page and download the current recommended virgin. It will replace your existing one. I looked at the download page, and it looked like a lot of people downloaded already -- at least I didn't see anything that looked "virgin." |
Michael Gmirkin Send message Joined: 18 Dec 03 Posts: 50 Credit: 8,956,363 RAC: 26 |
Fascinating stats. I'm still of the opinion that BOINC should "look into" some kind of "notification system" if not "upgrade system" to keep everyone on the same page. I personally wouldn't mind a pop-up every so often that says "There is a newer RECOMMENDED version of BOINC available. You are currently running version 5.4.11. The CURRENT stable version is 5.8.15. Would you like to upgrade?" If yes, take folks to the download page. If no, perhaps an option "remind me again in N days" or "please don't remind me again about this updated version" (though with the caveat that if a NEWER recommended new version comes out it might pop up a new message again). Of course, in my opinion, some kind of "automatic update" functionality would be peachy. So long as a user or admin could easily control the level of updates allowed or disallowed ("Do Not Auto-Update Ever," "Notify me an update is available, but do not download it," "Download updates, but let me choose when to install them," or "automatically install all updates." That should make both sys admins who want to maintain a stable unchanging version happy, as well as folks who don't care if the latest version gets downloaded and installed automatically so long as the transition is seamless.) I think this would benefit BOINC and users equally by keeping everyone on the same page with updates as much as possible so everyone gets the same benefits of newer versions. It will also cut down on wasteful tech support as newer version fix glitches in older version (granted they occasionally introduce NEW glitches, c'est la vie). I know it's not at the top of anyone's priority list, tho'... If an update scheme isn't possible, is at least a non-updating "notification" message and link to the download page possible? That way users would still be in control, but at least they'd KNOW when updated versions are available... And it would satisfy sys admins who don't want software that auto-updates stable mission critical systems (possibly making them unstable in the process). ~Michael If there were no time, how old would YOU be? ~Me BOINC Seti@Home Stats: Classic Seti@Home Stats: |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.