For all who want to read up on the Client Setup Logic for BOINC 6.0, please go read ClientSetupLogicWinSix in the BOINC Wiki.

It sure doesn't look like there's any other option to start BOINC than through a service. One that has its own user name and password as well.

Comments?

---

That seems like a big improvement in security. Currently BOINC runs under the same user that installed it on Windows. On Unixes it's easier to manually set it up to run on its own user.

Note that being installed as a service doesn't mean it will run on boot, it just means it can be set up to do that. The service may very well be set to start manually, and have the manager start it and stop it just in the way it used to start and kill boinc.exe.

Something else I noticed on the recent changesets and on the wiki: data files (projects, slots, maybe logs too) will now be on a separate directory than the executables. That's what Vista prefers, since programs aren't supposed to write to "Program files", and depending on security settings, they just can't write there.

PS: Trac is currently completely missing, and I have a feeling that it's my fault :|

For all who want to read up on the Client Setup Logic for BOINC 6.0, please go read ClientSetupLogicWinSix in the BOINC Wiki.

It sure doesn't look like there's any other option to start BOINC than through a service. One that has its own user name and password as well.

Comments?

Sounds like everything is getting screwed up because of Vista.

---

Sounds like everything is getting screwed up because of Vista.

I don't know. Vista drives me just as nuts as the next person.

But is sandboxing such a bad idea? The Mac version does it. You can install the Linux version to its own account.

---

Kathryn :o)

Sounds like everything is getting screwed up because of Vista.

I don't know. Vista drives me just as nuts as the next person.

But is sandboxing such a bad idea? The Mac version does it. You can install the Linux version to its own account.

You can install Linux that way, but so far you don't have to.

I don't know why BOINC has to be run as a service, other than to make it play nice with Vista.

---

I don't know why BOINC has to be run as a service, other than to make it play nice with Vista.

One reason to NOT run BOINC as a service is that services are harder for newbie and novice computer users to start and/or stop or even know if they are running.

---

It is possible that the service is used in sort of the same way that the new Adaware is using the service install: You can opt in for having it run as a guard all the time in the background, or else it'll only run when the GUI is started. When you exit the GUI, the service exits and goes back to sitting as manual/stopped.

But until we actually see a BOINC 6 available to test, it's anyones guess.
I'll see if I can have a chat with Rom tonight.

---

Questions and answers:

1. Will it still be possible to start BOINC by hand, by just starting the BOINC GUI and it exiting when you exit the GUI?

- Yes, services don't have to be setup as automatic start, they can be setup as start on demand.

2. Will it still be possible to start BOINC from the command line?

- Yes.

3. Will the service run all the time, or only when the GUI is activated? Or is there an opt-in option in the installer to only start BOINC when starting the GUI, with the service being dormant at all other times? (And if not, why not?)

- Depends on if the user has specified in the installer whether or not to start BOINC on startup.

4. When will support for Windows versions older than Vista cease to exist?

- Current plan is to support Win 98, Win ME, Windows 2000, Windows XP, Windows Server 2003, and Windows Vista.

----
So there you go, folks. anything else? :-D

---

I am running BOINC on four computers, two of which are Vista. I am running everything as single user. I am having no problems with either 5.8.16 on one and 5.10.20 on the other.

---

http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

I am running BOINC Manager version 5.10.28 .

For some reason one of my computers only updates and sends completed date once or twice a day. Or when I manually do it.

I assume there is a setting somewhere to tell the manager program how often to do this. Can someone tell me where to find this setting?

I am running this version on 4 computers, and only one is having these symptoms.

FWIW This is the only machine running VISTA.

Ideas?

Thanks! Jim Tanis

For some reason one of my computers only updates and sends completed date once or twice a day. Or when I manually do it.

You mean they stay in "ready to report"? Why do you want it to do it faster? Once a day is enough. You don't win anything by reporting them as soon as they finish.

---

Yes they stay in ready to report. I suspect that it may not even report once a day. I usually get tired waiting on it, and do it manually, so not sure. The other machines seem to do it more often. Yeh, I realize that there are no extra points for reporting quicker, but I am a perfectionist, and like things to work as I think they should <grin>

Thanks! Jim

For some reason one of my computers only updates and sends completed date once or twice a day. Or when I manually do it.

You mean they stay in "ready to report"? Why do you want it to do it faster? Once a day is enough. You don't win anything by reporting them as soon as they finish.

Two possible reasons I could think of :


1. In the BOINC version I'm using, a project will load fresh WUs only when it's completely empty when a different project (usually CPDN) is running as the second task, isn't allowed to load new WUs and piles up long term debits.


2. the project that doesn't update so often has very long WUs (e.g. QAH)

In this case, when BOINC detects a cache underrun it will ask for example 1000 seconds of work but receive 70.000 instead.

That means that the next cache underrun can only happen when 69.000 seconds of work are "used up".

Guess you misunderstood. I have no problem getting new work units, but reporting completed work units.

Thanks Jim

Two possible reasons I could think of :


1. In the BOINC version I'm using, a project will load fresh WUs only when it's completely empty when a different project (usually CPDN) is running as the second task, isn't allowed to load new WUs and piles up long term debits.


2. the project that doesn't update so often has very long WUs (e.g. QAH)

In this case, when BOINC detects a cache underrun it will ask for example 1000 seconds of work but receive 70.000 instead.

That means that the next cache underrun can only happen when 69.000 seconds of work are "used up".

Guess you misunderstood. I have no problem getting new work units, but reporting completed work units.

Thanks Jim

Nope, I didn't misunderstand :-)

Reporting and requesting are close related.

BOINC will only report finished results when it either has to request new work (and this is where my 2 reasons kick in) or when the workunits are close to the expiration date. The purpose of this setting is to reduce server connects.

Ahha! That makes sense! Thanks! Jim

Guess you misunderstood. I have no problem getting new work units, but reporting completed work units.

Thanks Jim

Nope, I didn't misunderstand :-)

BOINC will only report finished results when it either has to request new work (and this is where my 2 reasons kick in) or when the workunits are close to the expiration date. The purpose of this setting is to reduce server connects.

The purpose of this setting is to reduce server connects.

NXOR if you really want to report straight away you could get the Crunch3r version of BOINC, which reports results immediately (actually 60 seconds after upload). However having said that the reason why the "stock" BOINC doesn't do this is given above.

Here is the link to Crunch3r's BOINC page. Take the Red pill.

---

MarkJ

However having said that the reason why the "stock" BOINC doesn't do this is given above.

Actually, BOINC has had this option again since 5.10.45, but you need to enable it via cc_config.xml

---

The Big BOINC 6 Answer Thread

De Grote BOINC 6 Antwoorden Draad

Todo sobre BOINC 6

---