Posts by dhatz

1) Message boards : BOINC Manager : Can't connect to Predictor@home (Message 3755)
Posted 3 Apr 2006 by dhatz
Post:
darkpella, your traceroute results look fine to me. They're the same as mine and my BOINC connects to Predictor without problems.

Many sites block ICMP (ping/traceroute) traffic nowadays, so you can't ping or traceroute them, but the site itself is reachable via HTTP/HTTPS (web, used also by BOINC etc).

Do you still have problems attaching to the Predictor@home project?
2) Message boards : BOINC Manager : Can't connect to Predictor@home (Message 3733)
Posted 31 Mar 2006 by dhatz
Post:
Hi,
I tried attaching to predictor@home, but it looks like I can't connect to any server within the scripps.edu domain. I tried using visualroute from any public servers on the net (Italy, where I live, The US and others) but looks like San Diego Supercomputer Center is blcoking all traffic to www.scripps.edu, regardless where it comes from.
This is happening since months, so I'm wonderingf who's taking part in Predictor@home and how they could do it (and how could I possibly...)


Can you copy here the results of "TRACERT predictor.scripps.edu" command ? (or "traceroute predictor.scripps.edu" under Linux)

Does predictor.scripps.edu have an IP of 137.131.252.96 ?

Because I suspect the problem is due to "DNS poisoning", as I've noticed the same issue in the past.
3) Message boards : BOINC Manager : BOINC has CLIMATE PREDICTION (Message 3672)
Posted 28 Mar 2006 by dhatz
Post:
I have a related question to the previous one. Which projects have the smallest downloads for WU? I am on dial up and a slow one at that. I am not in a position to leave the connection on for hours, which is what I am finding necessary for Rosetta.


There is a special feature in Rosetta, for people with dialup or slow links:

see FAQ adjustable Work Unit runtime parameter

Basically you can crunch multiple "models" on the same WU for much longer than the default 2hrs/WU. I personally set it to 8hr/WU, but slow-link users can use up to 4days/WU (i.e. 4 CPU-days). If you set it 8hrs/WU, your download traffic will be reduced to 1/4th of the current one.

PS: I think thr max WU-runtime nowadays is 12hr, since the project has reduced WU-TTL (time-to-live or maxtime) while they're debugging the 1% issue.
4) Message boards : BOINC client : 5.2.13 - Low benchmark results on linux 64bit, Intel platform (Message 2846)
Posted 29 Jan 2006 by dhatz
Post:
AFAIK it's a known "issue" with BOINC under Linux, but it only affects the speed BOINC *thinks* your computer has. Consequently it'll give you less credits/points than you'd get with the same PC under e.g. WinXP.

Still, the science applications themselves should run fine regardless at your PC's "true" speed.

You can run an "optimized" BOINC-Linux client to remedy this (see the links in the URL in my sig or go to Paul Buck's Wiki)

PS: Try at
# cat /proc/cpuinfo
and see what your Linux kernel knows about your CPU
5) Message boards : BOINC Manager : Automating Project Attachment on Remote Machines (Message 2665)
Posted 18 Jan 2006 by dhatz
Post:
When running many PCs under the same account, the account key for every project is in the account-*.xml files in each PC's ~/BOINC directory.

But one would need to "protect" that account key, as knowing the account key of just one project, one can change BOINC defaults across all PCs and projects, right? (as long as some PCs have projects in common, for those defaults to "propagate")

So, when all my PCs are in my home, no problem. How do people deal with this issue when considering to setup BOINC on 30-40-100 PCs at work ? Or if I want to quickly setup a BOINC project on a friends PC, without him going through all the trouble of setting up a separate account?

Is there a way to attach a PC to an account, without storing the account key on that PC's .xml files in plaintext for everyone to see? Could BOINC be told to keep account keys in hashed form and just compare the hashed ones with project's server? (but still require plaintext account-key or password for changes of settings in /home.php)

Or am I missing something?
6) Message boards : BOINC client : How to run BOINC in a "sandbox" under WinXP? (Message 2488)
Posted 10 Jan 2006 by dhatz
Post:
Any ideas on the "sandbox" i.e. limited account, allowed to write under its own home-dir only and chroot() issue?

Btw, after spending some time on this, I've created a HowTo: Join Distributed Computing projects that benefit humanity document, where I categorise the various projects and give special weight to BOINC.
7) Message boards : BOINC client : How to run BOINC in a "sandbox" under WinXP? (Message 2463)
Posted 9 Jan 2006 by dhatz
Post:
Can I run BOINC under XP in a limited environment, so that file access to files outside its own directory tree is prohibited? If yes, how?

To give an example, under Linux I've setup a different user "boinc" and everything runs under this account. So right now, a rogue BOINC proj executable can only "harm" other BOINC files (under ~boinc/), but can cause no harm to the system and ordinary users.

Btw, would it be possible for BOINC/Linux to chroot()? so the reach of any child processes is limited (like Unix ftp daemons have been doing for anonymous users)




Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.