Scheduling BOINC

[AMDave]

In another thread, DMMC said:

If I could get the %@@!!*&@ scheduler to work right in BOINC so that systems would run after hours I could put alot more systems in it

So I thought we should have a look at this.

We know that there is a "service" instance of BOINC and it has CLI controls. We know that we can't directly control a service from the scheduler. But we know that we can control WSH (Windows Shell script) files from the scheduler.

So what we need is some code to start and stop the service.
We don't want the WSH script running the whole time so we should split this into 2 files (1 to start it and 1 to stop it each to be called by the scheduler).

Now we need some WSH control code (can be .wsh or .vbs or .js). There's not much that you can't find or get a lead on from MSDN & the MS Knowledgebase these days.:
http://msdn.microsoft.com/library/de...ting061499.asp

I found this piece which should help:
http://msdn.microsoft.com/library/de...rvicestart.asp

Alternatively you could use the ShellExecute method to start BOINC as a CLI task and send the kill SIG to the process later on to stop it.

I'd prefer to use the service instance though as the output is sent to the windows message log.

[AMDave]

Oh, by the way you will need to ensure that BOINC has been installed as a service...

Starting the service can be done using this script I saved as BOINCstart.vbs

Call ServiceStartVB()

Sub ServiceStartVB()
        dim objShell
        dim bReturn

        set objShell = CreateObject("Shell.Application")

        bReturn = objShell.ServiceStart("BOINC", true)

        set objShell = nothing
end sub

Stopping the service can be don using this file BOINCstop.vbs which is exactly the same but with "start" replaced with "stop"

Call ServiceStopVB()

Sub ServiceStopVB()
        dim objShell
        dim bReturn

        set objShell = CreateObject("Shell.Application")

        bReturn = objShell.ServiceStop("BOINC", true)

        set objShell = nothing
end sub

So. There you go.

Now you can place some scheduler entries to call the files when you want from the scheduler.

You can even script that across your network as well using the AT command.

I'd prefer to make some extra "stop" call to make absolutely sure, but even if BOINC is running in the background as a service it is not going to be visible to an end user in terms of CPU availability or in the GUI.

[DMMc]

OK!!

Thanks Dave. I will start trying this on systems Monday. I do hope it works. for me.

[AMDave]

Ooops.
Almost forgot.

====================
* Never run the GUI and *
* the CLI at the same time. *
====================

It *will* trash your projects and
it *can* trsh the BOINC install.

[Empty_5oul]

now that owuld have been funny across 90 systemas if they all needed re-installing for BOINC to work lol :P

[AMDave]

:oops: I seem to have a habit of learning some things the hard way.

[DMMc]

now that owuld have been funny across 90 systemas if they all needed re-installing for BOINC to work lol :P

Remote access is a wonderful thing but a total reinstall on all systems..... :shaking:


Please don't even jest [-X

[Empty_5oul]

just wondering what do you use for remote access and what os do the systems have?
i have used VNC which is good but at school / college they had some amazing tools where the master had thumbnails on their screen of every PC and could take control in real time, that was pretty kool but lagged the network a bit

[DMMc]

Use a program called Radmin. it works well across both network and even 56k connections. the interface allows you to see and interact live with user at other system or to take total control.
I use it to see what is going on when my users FU.

[Empty_5oul]

ok, ill have a look online at some point,

sounds good tho :thumbleft:
how long would it take you for example to install a simple program and get it running such as SOB on ALL the machines then - is there a command to allow you to do something to every machine all at the same time.