Thank you Jord for the quick reply. It appears that if XP and Linux are treated seperately, I may not be able to fulfill the workload as I have to split the runningtime between XP and Linux. I will have to see how it goes

Richard Nolan

Unless you HAVE to have cuda, then 6.2.19 is the newest version that you should use.

Use the venues (default, home, work, school etc.) or get BOINC 6.5.0 (or later) and use the option in cc_config.xml .. See this FAQ.

I wonder if in this transitional period where projects have yet not adopted the % parm in their website profiles, if there is a mechanism to translate the old to new on the client side?

Nope, the preference change was done without any thought about backwards compatibility or userfriendliness.

Without any thought, really.

How it got to this big a number? One possible cause is a system-clock that was way off (couple of months into the future or past) while BOINC was running.

If you don't exit then I'm surprised the BOINC executable can be updated. But even if it is I don't think you will be running the new version until you do exit and restart BOINC.

The installer is smart enough to shut down the running core client. I've tested it.

That said, I usually stop the service when I upgrade just to be on the safe side.

Can I exit BOINC, upgrade and then restart any tasks, or will this cause problems?

That's how I do it. Not a problem for me.

I don't even exit most of the time. However when it comes time to go to a version 6 client more precautions will be advisable.

Note: boinccmd NOT boinc_cmd
Perhaps the name changed as I've seen many references to boinc_cmd?

It's called boinc_cmd on Linux systems.

Also, the batch file MUST be in the Boinc directory else you get "Authorization failure: -155" error message. (Thanks to Ageless in another thread for that info)

If you include the password and hostname on the command line it can be run from any directory or from any machine on your LAN. The password is in boinc/gui_auth.cfg and it may be the very long password assigned by BOINC but you can change it to something shorter using a text editor.

Change all the slashes in the examples to backslashes.

If the software you're using is command-line, or has some way to automate it, you can run "boinc_cmd --set_run_mode never" just before the heavy processing, and "boinc_cmd --set_run_mode always" just after it ends.

I have to check if it is malaria@home or rosetta@home (or LHC?) but one of these applications made the mouse movements rather choppy on a slightly inferior machine (Pentium IV Mobile 2 GHz, 1 GB RAM)

So my guess would be that not the manager and not the client but the actual application run is the root cause here.

Cheers
PJ

I think, a credits penalty for those aborted WUs that have not even been tried to crunch (CPU time less than a minute or so) would be a good idea.

I'm aware that there are some real reasons to abort a WU, like a known faulty batch - but for that batch the admin could set a "no malus" flag or abort it on server side, which could be taken as a sign for "no penalty".


(now waiting for the stones to be thrown at me)

There is a penalty for aborting tasks either manually or from server-side aborts. In either case the daily quota is reduced 1 per abort.

Works for me. If you disable network activity, BOINC doesn't do any network activity on its own. Only if you explicitly tell it to, by for example updating a project.

I think you have misunderstood the issue: the problem is that it is simply not possible to start Boinc without some kind of net connection. For example, on my Gentoo machine I have to start either the cable or wireless card to be able to start Boinc. It doesn't matter if there is any internet behind the router, Boinc just needs some network.
It would be nice if this could get fixed in the future.