Version 3.1 of BOINC LCS is available. BOINC LCS is a web application, written in PHP, for monitoring a set of BOINC clients.

---

Is the website available in English?

---

Currently not, i'm sorry :)

Since english isn't my native language i'll try to use it in the changelog and there is also a file called INSTALL included with the package. It is written in english as well. Feel free to use the contact form: https://www.onenext.de/contact.html

Greetings!

Willy

Hi,

I've read the installation doc, do you mean that all the prerequisites and installation instructions apply to the machine from which you want to access to the remote boinc, or on the one that is actually crunching with boinc ?

Thx

Hi,

the requirements (Apache or lighttpd with PHP) are related to the machine from which you want to access the remote Boinc clients. Let's call it "master".

Installation steps 5 and 6 applies to the remote client. The only thing you have to do on the client side is to make your client_state.xml obtainable on the network.

There are several ways to achieve that:

* Already installed webserver
* My small Perl script (miniserv.pl)

or (if you are brave enough) on a Linux machine with netpipes installed type:

faucet 8080 --out --localhost 0.0.0.0 --backlog 128 cat /path/to/your/client_state.xml

I've found out that the contact data provided with the installation instructions are out of date. I will fix it as soon as i can :) And maybe there is someone out there who wants to help me to improve the translation..?

I had the idea to use your interesting system from a corporate machine where boinc cannot get access to network (bad proxy), therefore only to himself (I feed it with WU from outside / USB), and I cannot see what's happening to my home boinc... but all these installation steps will also certainly be blocked on that machine (I cannot run setup without admin pwd, I can only use portable apps / USB).

"bad proxy" means that there is a proxy but it is configured for HTTP connections only? If so, you can try to send your client_state.xml to a webserver (via PHP or Perl upload) using a simple POST command.

I meant "meeeean proxy", ie here at the office we don't know the proxy address + we don't even have the windows password (changed automatically by the login ID card, we only know our car pincode), so it's impossible to setup boinc access internet...

Could you be more specific about "try to send your client_state.xml to a webserver (via PHP or Perl upload) using a simple POST command" please ?

Is your Windows "command prompt" accessible? Maybe you can view your proxy settings.

Execute the following command if possible:

netsh winhttp show proxy

Could you be more specific about "try to send your client_state.xml to a webserver...

Under Linux i would use POST on the commandline to do POST requests against any webserver for testing purposes. If you do not know what a POST request is take a look at the contact form. https://www.onenext.de/contact.html

It's a form which uses the POST method also used to upload files to a webserver... If you click on the "Go" button you can still see the same address in your browser since the data will be sent "invisible" within the HTTP request itself. A GET request on the other hand would look like this: https://www.onenext.de/contact.html?name=YourName&email=you@example.com&message=YourMessage

My idea:
- Open port 80 and install a webserver at home
- Use (install) a PHP file upload script on that server
- Download cURL binaries for your machine at work

cURL for Win2000/XP http://www.gknw.net/mirror/curl/win32/curl-7.21.4-ssl-sspi-zlib-static-bin-w32.zip
Other versions http://curl.haxx.se/download.html

If you know your proxy address you can use cURL and upload files to your home-server. For example:

curl -x YOURPROXYADDR:YOURPROXYPORT -F "fileupload=@/path/to/your/client_state.xml" http://example.com/upload.php

I don't want you to lose your work! And sorry but i don't use Windows... So i cannot reproduce those (OS-specific) steps :)

Thanks for all those explanations !

The first command tells me "direct access with no proxy", which I know is wrong since boinc manager cannot access anything on the net, and we have websites blocked by it regularly... so it's a hidden proxy.

And anyway even if I knew it's address, I cannot setup a user / login access under proxy parameters since our own windows account password it hidden to us (security card login, I just know my PIN).

So I guess I wouldn't be able to use that interesting cURL tool neither... ?


Since it's a very interesting topic (even though I'm afraid we're waisting it a bit here right now ;) ) I'd like to understand, your idea is that I could be able to upload the client_state file from my home boinc on a webserver onto my home machine so I can then use it through this boinc LCS script at my office, right ?

And I could do this in plain html from my office browser, not needing any proxy setting then ?

But then couldn't I put this xml file on the home serveur *from home*, and then just use the boinc LCS from the office ?