Posts by Nicolas

61) Message boards : Questions and problems : Strange 6.6.41 problem (Message 28322)
Posted 25 Oct 2009 by Nicolas
Post:
Also, 'Add Port' is for incoming connections...

Wasn't sure there... then again, when the parts talk to each other, they use an outgoing and incoming port. I figured it doesn't hurt to set the ports.

But as far as the firewall is concerned, it's neither incoming nor outgoing if it never goes (or comes from) outside the computer. And allowing port 80 incoming is probably a bad idea unless you knowingly run a webserver and want outside access.
62) Message boards : Questions and problems : Deploying BOINC on multiple computers invisibly (Message 28318)
Posted 25 Oct 2009 by Nicolas
Post:
This is a partial solution in that the exe is running, but there are no icons displaying to the user that it is running.

With his solution, boincmgr.exe is not running at all...
63) Message boards : Questions and problems : Strange 6.6.41 problem (Message 28317)
Posted 25 Oct 2009 by Nicolas
Post:
Jord, have you ever seen Windows Firewall actually cause problems with BOINC in localhost?

Also, 'Add Port' is for incoming connections...
64) Message boards : Questions and problems : Does boinc utilize multi core cpus well? (Message 28259)
Posted 23 Oct 2009 by Nicolas
Post:

10/22/2009 11:59:48 PM Preferences limit # CPUs to 1

Well there you go. Change your preferences to allow 2 CPUs and it will work.
65) Message boards : Questions and problems : BOINC & Virtual Machines (Message 28088)
Posted 18 Oct 2009 by Nicolas
Post:
BOINC isn't "treating VM processes differently"; it doesn't even know or care what other processes are running on your computer. It just runs in "low priority" and lets the operating system care about the rest...
[/i]
66) Message boards : Questions and problems : Compatibility with Snow Leopard? (Message 28087)
Posted 18 Oct 2009 by Nicolas
Post:
What version of BOINC?
67) Message boards : Promotion : Problems Getting folks to run BOINC (Message 28086)
Posted 18 Oct 2009 by Nicolas
Post:
After talking to some people about running BOINC they tell me that they don't like the idea of a program that is downloading and uploading stuff with out them knowing it. Most are worried about someone breaking into the computer and getting their info like bank accounts and things.

BOINC doesn't leave anything open for "someone to break into the computer". Your computer communicates with the project, not the other way around. You just have to trust the projects you attach to.

Analogy: BOINC is not leaving your house window open, where thieves could get in. You are letting some specific people come in (the projects you attached to), and then only to one room of the house (if you enable "protected application execution" when installing).

Sure, that project could be malicious. But then so could any other website. And it's highly unlikely none of the people you talked to had ever downloaded a program from a website and run it. To do that, they'd have to trust the website. Attaching a BOINC project is basically the same. When you attach, you're downloading software from it and running it. How to know if they're trustable? Well, how did they know if random-website-they-got-a-program-from was trustable?

Also, it doesn't "download and upload without them knowing"; there is a list of "transfers" in the manager, after all :P And then again, just because something uploads and downloads doesn't mean it's doing something bad. I'd be more worried about the "running code on your computer" part than the "downloading and uploading" part... And then again, many programs are already "downloading and uploading stuff" without you knowing exactly what it is. Web browsers do quite a bit of downloading from servers other than the website you're connecting to; for example, to get ads :P
68) Message boards : API : Implementing dynamic application executables (Message 28007)
Posted 14 Oct 2009 by Nicolas
Post:
That is a terrible idea for security. Application files have a cryptographic signature, input files don't.
69) Message boards : Questions and problems : Mac OS X - GPU not being used (Message 27942)
Posted 12 Oct 2009 by Nicolas
Post:
The new drivers are in OSX 10.6.x and have been out for around 1 month. I have asked on seti and been told that the GPU programers have no experience coding on OSX (They only know CUDA). Also all GPU programing for both ATI and NVIDIA are accessed though the OpenCL API extension. The beta Open CL Windows/Linux for NVIDIA is http://developer.nvidia.com/object/opencl-download.html it also has sample code and SDK stuff for OSX/Windows/Linux. In theory once ATI has it's kit out it will be posable to write the code once and have it work on both GPU types and all OSs. OpenCL is the compute standard put out by the group that publishes the OpenGL standard for graphics. Now the science apps need to be rewritten for OpenCL and people need to use OpenCL final when released for windows.

OpenCL is to program the science apps. BOINC just needs to detect if there is a GPU on the computer, and what model it is. Since BOINC on Mac is 64-bit, it needs a 64-bit library to get that information.
70) Message boards : Questions and problems : Mac OS X - GPU not being used (Message 27898)
Posted 12 Oct 2009 by Nicolas
Post:
Until nVidia makes a 64-bit CUDA driver for Mac, there won't be support. Or so I heard.
71) Message boards : Questions and problems : Operating System Upgrade (Message 27897)
Posted 12 Oct 2009 by Nicolas
Post:
You'd save yourself some trouble by setting all projects to "no more work", waiting till you have no work left (and making sure all is reported), and then reformatting.
72) Message boards : Questions and problems : Does boinc utilize multi core cpus well? (Message 27896)
Posted 12 Oct 2009 by Nicolas
Post:
only one project at this time supports Multi-thread apps, and thats aqua@home...

the more cores/the better for them.

Who said anything about multi-threaded apps in this thread?

BOINC has always supported multiple cores, by running one workunit on each. The more cores the better for any project: you do more of their tasks per day.
73) Message boards : Questions and problems : Does boinc utilize multi core cpus well? (Message 27894)
Posted 12 Oct 2009 by Nicolas
Post:
hey, howd you do your boinc work in progress in your signature?

I wrote it myself :)

If you have a webserver with PHP on the same computer as BOINC, I can give you the script.
74) Message boards : The Lounge : Google launches Monopoly Online (Message 27828)
Posted 7 Oct 2009 by Nicolas
Post:
Although I'll grant you that Google has a monopoly online ;)
75) Message boards : Web interfaces : Filtered users on message board (Message 27767)
Posted 4 Oct 2009 by Nicolas
Post:
What do you think would happen if any user had the ability to block any other user from posting to the forum?
76) Message boards : BOINC client : get_messages(int seqno, MESSAGES&) (Message 27766)
Posted 4 Oct 2009 by Nicolas
Post:
There is no way to get all the messages, because they aren't there anymore. Once the client writes the 2001st message, it deletes message 1 from memory.
77) Message boards : Questions and problems : BoincTasks alternative BOINC manager (Message 27747)
Posted 4 Oct 2009 by Nicolas
Post:
You're statically linking to the LGPL-licensed GUI RPC libraries from BOINC.

If you do that, you must provide either source code for your app, or the object files (.obj). I should be able to modify the BOINC code, and relink your app with my modified version of the BOINC code.

Your other option is dynamically linking instead (making a boincguirpc.dll or something like that). Then I could just put a modified version of the DLL in place without having to link anything.

In your license, you claim the BOINC libraries are GPL-licensed. That's incorrect (they're LGPL), but if it was actually GPL, you would be under a bigger problem (you wouldn't be able to link your closed-source program to that code at all).
78) Message boards : Web interfaces : Project doesn't appear in "Projects in which MC707 is participating" list (Message 27746)
Posted 4 Oct 2009 by Nicolas
Post:
That list comes from http://boinc.netsoft-online.com/. The admin of netsoft probably didn't add FreeHAL yet.

Maybe for a good reason.
79) Message boards : Projects : News on project outages. (Message 27742)
Posted 3 Oct 2009 by Nicolas
Post:
SETI@home

Since about 3:00 local time (10:00 UTC) the BOINC master database is disabled. So, uploading is possible, but no reporting or downloading (scheduler needs database). The forum is inaccessible too.

Eric Korpela reports:
"Our database machine crashed. I can't get in to campus. Matt's nowhere to be found. Jeff's in Nepal. Dan's in South Africa. Please spread the word that we know that there's a problem."
80) Message boards : Questions and problems : 6.6.40 SIGSEGV on Gentoo (Message 27708)
Posted 1 Oct 2009 by Nicolas
Post:
Recompiled with "-g" in CFLAGS and CXXFLAGS.


The client crashed as suspected

01-Oct-2009 07:09:54 [Rectilinear Crossing Number] Giving up on upload of W8_0168_1081_0927_0001.12: permanent upload error
SIGSEGV: segmentation violation
Stack trace (8 frames):
/usr/bin/boinc_client(boinc_catch_signal+0x45)[0x473895]
/lib/libpthread.so.0[0x7fa1a2caca00]
/usr/bin/boinc_client[0x456225]
/usr/bin/boinc_client[0x4564c1]
/usr/bin/boinc_client[0x420b28]
/usr/bin/boinc_client[0x454b10]
/lib/libc.so.6(__libc_start_main+0xe6)[0x7fa1a26e45c6]
/usr/bin/boinc_client(__gxx_personality_v0+0x1d9)[0x405de9]

Exiting...


If you can tell me where the debug info you need is I can post it.

Do that again, running the client manually (from the correct directory, careful with that!) under gdb.

trog@localhost /wherever/boinc/data/is$ gdb boinc_client
(gdb) run
[now wait for it to crash]
SIGSEGV: segmentation violation
(gdb) backtrace full

This time you should get a stack trace with debugging information instead of just memory addresses [0x4564c1].


Previous 20 · Next 20

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.