I will soon be implementing a new application ;)
The application will be called iThena NRT.

The credit problem will be solved.

The tasks for iThena CNode will be phased out.

However, there are many problems.
Initially, iThena NRT will be available as a virtualised environment (VBox/Vmware). You will be able to start a virtual system.

Of course it will also be possible to run it locally.

In addition, the iThena NRT application will require a permanent connection to the Internet.

I will try to add tomorrow a new application, share a virtual disk (virtual machine) and a simple instruction.

However, possible delays.

Being obliged to install VB to run a nci project is... counterproductive. Huge resource requirement for something supposed to be "light and painless".

I'm using it on a linux VM (not running on my machine, but a French provider), since you only have a linux application, so I won't be able to install VB anyway.

Bye bye ithena...

I suggest you read it carefully.

I think you can run everything without VM.
Logically / software is not a problem.

The problem may be different.
Application in current version requires root permissions (Internet connection issues).

Do you want to give root for iThena NRT?
This may be a little controversial.

From the point of view of the virtual machine it is a smaller problem.
But Thena NRT will be open source.
I will make the code available, which is based on other/ready solutions.

However, the VM will not be critically required.
This problem may even disappear in some time.

Well, unfortunately, today it was not possible to add a new application (too many problems).

I'm running tests locally.
If there will be no problems, today (tomorrow) I will add the application to the project: ithena_nrt_v1.00_x86_64-pc-linux-gnu.

Look forward to the NON Virtual version and a change to the credit system.

---

Proud Founder and member of

Have a look at my WebCam

I got one of the new work units....
It took forever to download only to process for less than a minute. I hope that this was just a test and in the future the units will be longer.

I got one of the new work units....
It took forever to download only to process for less than a minute. I hope that this was just a test and in the future the units will be longer.

https://root.ithena.net/usr/result.php?resultid=2296425
Stderr output.

The problem is boinc user permissions.

Due to the fact that the application requires root privileges, errors appear.

Does anyone have any VPS available only for BOINC?
Can someone add root privileges and check?

Except for that first WU, the other WUs I have gotten seem to be working fine....crossing my fingers and knocking on wood.

Except for that first WU, the other WUs I have gotten seem to be working fine....crossing my fingers and knocking on wood.

You have other WU with iThena NRT v1.00?

My bad, they were other CNode WUs. I had thought you stopped that app when you started the new app.

So I do not understand when you write "iThena NRT will be available as a virtualised environment (VBox/Vmware). You will be able to start a virtual system. Of course it will also be possible to run it locally."

My boinc user experience with VB / without VB project is

- regular project app : an app version for one (or various) OS is developed by the project, running natively in the host OS (executed by boinc user)
- VB project app : a linux virtual machine is ran by boinc in the host OS (whatever OS it is) using VirtualBox. Inside that VM the boinc project app is running.

(it seems in recent times a few projects are also using docking containers to run the boinc app, being a lighter solution than VB VM, example Theory Native for LHC)

What you said doesn't match with these two options, could you explain better please ?

one of the components of the new application requires running on behalf of the root

options:
1. run a boinc instance under root
2. " chown root tracebeat* " + " chmod u+s tracebeat "

in both cases, logs are created accessible only to the root, not for the boinc

one of the components of the new application requires running on behalf of the root

options:
1. run a boinc instance under root
2. " chown root tracebeat* " + " chmod u+s tracebeat "

in both cases, logs are created accessible only to the root, not for the boinc

This idea will work well with the boinc client?

This idea will work well with the boinc client?

for the client test, new tasks on the server are needed (+ the ability to run them only by choice, otherwise they will immediately take it all apart)

I started the application manually with a fake input file.

PS. did not have time to save the real task for the experiments

There is an interesting idea from the LHC dev site - the BOINC client embedded in the VM.

a regular client receives and runs a task for Vbox.
VM - Linux with a specially configured client (for example, launch from root or installed additional software)
one nuance is to pass the user authentication key to the internal client before it starts

an additional host with a name defined in the VM appears in the user’s list, you just need to configure a separate "location" for such hosts with only native applications

Yes. LHC@Home still using the VBox?
Theoretically, I see information in applications (CMS Simulation, Theory Simulation, ATLAS Simulation) that it is currently using ;)

LHC-dev
BOINC VM APP - external task
Atlas & Theory (native) - internal task for VM