i'd rather not have the full "setiathome_4.02_i686-pc-linux-gnu" showing up in the output of ps or top... anyone ever tried renaming the executable?

i see in slots/0 that there's a text file called setiathome_4.02_i686-pc-linux-gnu that contains the following:

../../projects/setiathome.berkeley.edu/setiathome_4.02_i686-pc-linux-gnu

i'm wondering if changing the name of the executable under projects, and the contents of the soft_link tag shown above, would do the trick.

anyone tried this?

---

> i'm wondering if changing the name of the executable under projects, and the
> contents of the soft_link tag shown above, would do the trick.

Well,

There is an md5 checksum calculated over the executable, and this value is stored in the client_state.xml file. I can't recall if in the code the filename is inclcuded as part of what is summed up.

As a test you could try reducing the size of your WU queue a bit (so as not to lose many WUs), and then stop boinc, rename both the executable and the reference to it inside of client_state.xml.

When a new science app is released you would have to do it all over again, of course.

> There is an md5 checksum calculated over the executable, and this value is
> stored in the client_state.xml file. I can't recall if in the code the
> filename is inclcuded as part of what is summed up.

yeah, this scares me a bit, 'cuz that's obviously a generated file...


> As a test you could try reducing the size of your WU queue a bit (so as not to
> lose many WUs),

having just started with the boinc client today... how would i do this? i don't see it anywhere on the prefs pages on this site. is there a local config file?

> and then stop boinc, rename both the executable and the
> reference to it inside of client_state.xml.

i'll try it later today or tomorrow.

> When a new science app is released you would have to do it all over again, of
> course.

well, yeah... but it beats smacking the Ops guys in the face with the fact that i'm running it. yeah, they're "my" development boxes, and if i feel like pegging the CPUs at 100%, it's my binness... but still, no need to be that ostentatious about it...

---

It will work, but ONLY if you create an "app_info.xml" in the SETI Project folder (thus enabling the anonymous Platform feature) AND fill in the correct data for your renamed SETI Binary into it.

If you do, any existing WorkUnits on your System will be skipped and discarded, including unfinished ones.

(I know since I recently switched from the original 32bit Binary to a custom compiled x86-64bit on one of my machines)

---

> It will work, but ONLY if you create an "app_info.xml" in the SETI Project
> folder (thus enabling the anonymous Platform feature) AND fill in the correct
> data for your renamed SETI Binary into it.

could you post yours? i don't know what the structure of app_info.xml is supposed to be, and don't see one in my install directory to model on.

thanx!

---

> could you post yours? i don't know what the structure of app_info.xml is
> supposed to be, and don't see one in my install directory to model on.
>
> thanx!
>

Here is an example of app_info.xml.

> Here is an example of <a> href="http://boinc.berkeley.edu/anonymous_platform.php">app_info.xml[/url].


egggselent! thanks much!

---

> > As a test you could try reducing the size of your WU queue a bit (so as
> not to
> > lose many WUs),
>
> having just started with the boinc client today... how would i do this? i
> don't see it anywhere on the prefs pages on this site. is there a local
> config file?

W/U que is loosely controlled by web site settings in YOUR ACCOUNT under general prefs, the setting behind "Connect to network about every "

---

- da shu @ HeliOS,
"A child's exposure to technology should never be predicated on an ability to afford it."

> If you do, any existing WorkUnits on your System will be skipped and
> discarded, including unfinished ones.

It is possible not to get WUs discarded, just kinda tricky.

The part that begins <app_version>...you can have multiple sets of these.
(highlight and copy all lines between app_version and /app_version, inclusive)
To make it not reject current WUs, include an app_version for current project version_num (for windows seti current is 409, I think linux is 402...not sure)

I also do it the this way :
Set "Connect to Network every x days" to 0...

Wait until System is depleted off all WorkUnits (will not aquire new ones).
After that, make the clean switch.

IMHO easier than fiddling with the app_info.xml but your mileage may vary.

Hint : Make sure the data is filled into the app_info.xml 100.0% correctly, otherwise you will likely get an Error Message like "No Work sent - unknown Platform", which will cause BOINC to defer contact to the Server for 24 hours (a limitation that can be overcome by editing the client_state.xml, but that's really a last ditch "beat the System" kinda Workaround)

---