KWSN Orbiting Fortress

[JerWA]

http://boincview.amanheis.de/

[RampageIII]

Any tips on making it work? I put it in the folder they suggest but it doesn't find any of my clients.
_________________

[JerWA]

You only need to install it on one machine, and that machine will monitor the others (I assume you have more than one, else there's not much point to BoincView other than a better/more in depth interface than BOINC Manager).

On each of the machines you want to monitor you must created two .cfg files (they go in the BOINC directory, default of program files\BOINC):

1: gui_rpc_auth.cfg

This file is a password. Just edit it with notepad (not wordpad), and add whatever you want the password to be. It can be unique to each computer (meaning each PC you want to monitor can have it's own password), or you can just always use the same one (by copying the .cfg file to each workstation, which is what I did).

2: remote_hosts.cfg

This file is a list of hosts allowed to monitor/connect to BOINC Manager remotely (which is how BoincView works). It can be IP addresses or DNS names. I don't think WINS/NetBIOS names work though. One entry per line if you want multiple hosts to be able to monitor (you probably don't). This will/should be the same on each host you want to monitor, so simply copy the file to each one you want to monitor.

Once you've got those 2 files in place, stop (exit) BOINC Manager and start it. You may need to approve BOINC Manager for network access (Windows Firewall, ZoneAlarm, etc) and/or open port 31416 (default).

Now open BoincView on the machine you want to monitor from, and click the green + symbol in the menubar. Put in the name, IP, or NetBIOS name (it does work here, just not in remote hosts cfg) or browse your network to pick the computer you want to monitor. Put in the password you used in the cfg file, and it should appear and give you lots of info.

The next step is to spend 3, maybe 4 hours tweaking the appearance of BoincView.

Hope that helps.
_________________

Stats: [BOINC Synergy] - [Free-DC] - [MundayWeb] - [Netsoft] - [All Project Stats]

[mohrorless]

I'm not sure I want to do this....I spend WAAAAAYYYYYY to much time on the computer as it is, I don't need to watch my other computers too.
_________________
Fetch me the Holy Hand Grenade!




Keeper of the Unending keg of PGGBs
Taunter in Training
Campaign Manager for Sir Shrubbery



Plus

[JerWA]

[KWSN - Sir Brian C.......]

[JerWA]

Yeah, but less than 1% (on one core) on my system. Most of the time my system isn't idle anyways, so BOINC rarely gets 100%. It's at 94% and 97% right now, so it's not all that bad. Monitoring doesn't add any noticeable load to the monitored systems that I can tell. Even my lowliest rig gives BOINC 100% CPU time every now and then (it's never on 100% for long, Windows has to butt in from time to time).

I also have my poll times lower than default, and the priority set to Below Normal. 10s for my local system, 15s for most of the LAN machines (with a 60s offline timer for all), and 60s for my WAN machine (90s offline). I slowly bump the timers longer and longer as the projects prove to be stable, and the machines too. They're kind've fast right now because I've been working with BoincView (up to the 1.5 betas and back down to 1.4.2).
_________________

Stats: [BOINC Synergy] - [Free-DC] - [MundayWeb] - [Netsoft] - [All Project Stats]

[Pooh Bear 27]

Once it's set up correctly, you keep a copy of your gui and rpc files around to put in all new installations. Plus it's just a copy over the old (no install) each upgrade.

It is awesome to be able to see all 5 of my machines in a quick view, knowing what is happening on each processor, etc. Easy to add / change / update projects on all your farm, without having to remote / go to the box.
_________________
Watch the movie about me The 4-1-4s: The Original Teenage Hackers (It is only about 12 minutes long.)
My lucky numbers are 121*2^4553899-1 and 3756801695685*2^666669±1

[JerWA]

Yeah, thought it does provoke tinkering. So if you're a chronic tinkerer, BoincView may be just the thing hehe. Here's an example:

I added SIMAP recently, but right at the end of a batch of work units without knowing it. After a few days work ran dry and my PC doubled up on SETI. Hate that. So I told SETI no more downloading work, paused SIMAP, and added Proteins. I let Proteins download in 24 hour batches and then set it to not download more until I'd checked if SIMAP had work again or not (by simply starting it and then suspending it). In the middle of this, my WAN rig kept convincing Malaria Control that it wasn't on my account (kept changing CPIDs). So I added Malaria Control to my main rig, crunched a days worth of work, and then suspended that project. Just by luck, I was on the last workunit of a 24 hour batch of Proteins when SIMAP released the new work units. So I resumed SIMAP and just left Proteins active but not allowed to download. Worked a charm, and kept me entertained tinkering with it hehe.

About upgrades: Be careful between versions. 1.5 is a major change, and makes changes to program settings that 1.4.2 can't handle so you can't drop back from the 1.5 version (you end up having to redefine all the computers). Just a heads up hehe. I've had to do it four times, so I think I'm just going to wait for the 1.5 release rather than mess with those betas.

Here's my normal view.
_________________

Stats: [BOINC Synergy] - [Free-DC] - [MundayWeb] - [Netsoft] - [All Project Stats]

[KWSN - Sir Brian C.......]

and here's mine



_________________
Oh, it's blessed are the meek!, Well I'm glad they'll get something as they have a hell of a time!

[JerWA]