multiple installs of Boincview

[123bob]

This may be old news to some of you, but I found out tonight you can run more than one install of Boincview on different machines. My main rig, with XP pro 32, has been running it for some time. I thought it would be nice to run it on my new garage bench machine too. That way I don't have to walk the 10 feet over to the farm...:ROTF:

The garage machine is running vista 64 bit. It runs Boincview fine, simultaneously with the main rig. Now I can poke all the machines from two locations. :up:

Regards,
Bob

EDIT: Boincview available here (http://boincview.amanheis.de/)

[rcofell]

Yup, as long as the boinc installations are setup to allow each of the different machines running boincview to have access it should work :)
This works since boinc doesn't need to maintain a session for RPC, it just receives the command(along with accompanying password) and checks if it's from an authorized host(unless you use the --allow_remote_gui_rpc arguement), then replies with its corresponding response.

Now too bad BoincView hasn't been updated for quite some time. The developer hasn't made any contact for over 6 months...

[123bob]

Yup, as long as the boinc installations are setup to allow each of the different machines running boincview to have access it should work :)
This works since boinc doesn't need to maintain a session for RPC, it just receives the command(along with accompanying password) and checks if it's from an authorized host(unless you use the --allow_remote_gui_rpc arguement), then replies with its corresponding response.

Now too bad BoincView hasn't been updated for quite some time. The developer hasn't made any contact for over 6 months...

Thx for the further info. I run a "remote hosts.cfg" file that contains a set range of IP addresses. It allows me to still do DHCP. Of course, a massive power fail on the farm can cause the IPs to change. I haven't brought myself to run static IP yet. I've only had one instance of a severe enough power failure to cause a problem. Then it was a simple case of updating the IP of all the machines so Boincview could find them again.

As to updates, I find the program to run reasonably well, with only very rare hickups from time to time. I run mine only inside my secured network. I don't allow outside traffic since I run my farm "naked". No AV or firewalls. No wasted CPU cycles on that. I figure if I ever do get an infection or attack, I just reformat since these machines are dedicated crunchers only, and I don't use them for anything else. I find the program useful. Now that you mention it, I should browse over and find out if he takes donations....I don't mind donating for solid stuff without a lot of BS. Coretemp and CPUz are examples of this.

Regards,
Bob

[SiGfever]

Thx for the further info. I run a "remote hosts.cfg" file that contains a set range of IP addresses. It allows me to still do DHCP. Of course, a massive power fail on the farm can cause the IPs to change. I haven't brought myself to run static IP yet. I've only had one instance of a severe enough power failure to cause a problem. Then it was a simple case of updating the IP of all the machines so Boincview could find them again.

As to updates, I find the program to run reasonably well, with only very rare hickups from time to time. I run mine only inside my secured network. I don't allow outside traffic since I run my farm "naked". No AV or firewalls. No wasted CPU cycles on that. I figure if I ever do get an infection or attack, I just reformat since these machines are dedicated crunchers only, and I don't use them for anything else. I find the program useful. Now that you mention it, I should browse over and find out if he takes donations....I don't mind donating for solid stuff without a lot of BS. Coretemp and CPUz are examples of this.

Regards,
Bob
Bob,
Use the computer name instead since it will not change.

[123bob]

Bob,
Use the computer name instead since it will not change.

I've tried. It can't seem to find it that way. I don't know why. Perhaps my linksys can't do the lookup for it? That's what is acting as my DHCP server.

Bob

[rcofell]

Hmmmm, I think I've tried that before. I know BoincView can get the IP right from the computer name, but I'm not sure about Boinc. I'm thinking what I had to do for Boinc was ping them(computer names) first to make sure it could figure out the IP; I'm thinking this because just the other day I had Boinc complaining about not being able to find a computer name.

Another thing I've tried was setting up Boinc for a dynamic DNS address, that way I could change it on the fly which computer could control them all. I can't remember if it would cache the resulting IP though, because if it does you'd have to wait a while before it updates...

Of course there's always just RPD'ing into the machine running BoincView, that way you could control things while you're away from the house :)

[fart_plume]

just pull up a command promt window and type in ipconfig and hit enter it'll give you the ip of the computer your on.