FreeBSD x86 S5R1 App 4.09 available

nochjemand
nochjemand
Joined: 6 May 05
Posts: 28
Credit: 402,401
RAC: 0

RE: The standard

Message 38016 in response to message 38014

Quote:
The standard command-line client that can be compiled from the BOINC CVS tree (and snapshots) has an option -recdirectio that will write stdout and -err logs into the directory where it is started.

Merci - it logs. I'm sorry - rtfm helps...

CU

Martin

nochjemand
nochjemand
Joined: 6 May 05
Posts: 28
Credit: 402,401
RAC: 0

Hi, RE: Do you have

Message 38017 in response to message 38009

Hi,

Quote:

Do you have the opprtunity to compare wall-clock times

7,581 for this WU:
http://einsteinathome.org/workunit/10351297
(first Computer)
http://einsteinathome.org/task/35493977

Seams to be okay. ca.25% for other tasks - identical to the top output.

CU

Martin

Pav Lucistnik
Pav Lucistnik
Joined: 7 Mar 06
Posts: 136
Credit: 853,388
RAC: 0

RE: RE: Forgotten to

Message 38018 in response to message 38015

Quote:
Quote:
Forgotten to report: There is a warning at starttime:
$ > 2006-06-29 13:05:18 [Einstein@Home] Unparsed line in app_info.xml:

Oops. Thank you. Not severe, though. Can anyone using Einstein@Home from the ports have a look if this happens there, too?

Yes it happens too. It does not affect functionality in any way, so I decide to just leave it in.

As for comparing Linux vs FreeBSD, well, unless you dual-boot the same computer, all the comparitions are basically meaningless.

Pav Lucistnik
Pav Lucistnik
Joined: 7 Mar 06
Posts: 136
Credit: 853,388
RAC: 0

RE: Why is misc/compat5x

Message 38019 in response to message 38008

Quote:
Why is misc/compat5x needed?
My computer runs without and it seams to be ok...

$ ldd /var/db/boinc/projects/einstein.phys.uwm.edu/einstein_S5R1_4.09_i386-unknown-freebsd
/var/db/boinc/projects/einstein.phys.uwm.edu/einstein_S5R1_4.09_i386-unknown-freebsd:
libstdc++.so.4 => /usr/local/lib/compat/libstdc++.so.4 (0x2817d000)
libm.so.3 => /usr/local/lib/compat/libm.so.3 (0x2824f000)
libpthread.so.1 => /usr/local/lib/compat/libc_r.so.5 (0x2826a000)
libc.so.5 => /usr/local/lib/compat/libc.so.5 (0x2828c000)

That's why it's needed. Perhaps you did an upgrade from FreeBSD 5.X in the past, and left the old libraries where they were?

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5,833
Credit: 108,119,863,887
RAC: 33,457,006

All this talk about a FreebSD

All this talk about a FreebSD app incited me to grab another box or three and see what was involved in running BOINC/Einstein on FreeBSD. My last FreeBSD install was a few years ago and I must admit to have been corrupted by the dark side by essentially only using Windows of late. So I had to dust off some cobwebs and start thinking about shells and shell scripts and Vi and all that good stuff.

Well, I grabbed the 6.1 ISOs and started installing on an old Compaq PIII 750/256/20. I was surprised how little sysinstall had changed from the days when Jordan Hubbard was doing his thing. The install went very easily and I soon had the box up and talking to the outside world. I grabbed the BOINC 5.4.9 port (thanks Pav!!) and the Einstein app (thanks Bernd!!). Initially I couldn't find compat5x even though I remember that the compat libs were very visible as part of the distribution (back in the 3.x days anyway). So despite Pav's good advice that it would be needed, I decided to run things and see what happened. I always like saving unnecessary downloads so I grabbed the sun and earth files from a Windows install and the einstein account file and placed them all in the appropriate places. I edited out the blank lines in app_info.xml and created the files remote_hosts.cfg and gui_rpc_auth.cfg in anticipation of using a BOINC Manager on one of the Windows boxes to monitor the FreeBSD BOINC.

So I fired up BOINC on the FreeBSD box and attached to the running boinc_client from BOINC Manager on a Windows box and that worked fine. The whole thing fired up fine but to my horror I saw two results get trashed before I could pull the plug :). So now I can report the bleeding obvious - yes those compatibility libs really are required. But do you think I could find anything about them in the FreeBSD hanbook or other installation documents. In the end in desperation I googled "compat5x" and got a bunch of hits, one of which actually mentioned /usr/ports/misc/compat5x/ so a quick "make install" and the problem was solved.

So now, a few hours later, the third result is happily progressing without being trashed. It's 31% finished in just over 7 hours and extrapolating gives a crunch time of just over 23 hours. It is a long result. By way of comparison, I have a PIII 800 running at 840MHz and also doing longs under Windows. It is currently taking 29 hours per result. So that's almost 100MHz faster but close to six hours slower per long result. I know it's early days yet but I thought it was worth reporting that, like the linux app, the FreeBSD app seems to be going to turn out to be significantly faster than the Windows stock app. Looks like I might be converting a bunch of Windows boxes into FreeBSD boxes :).

A quick question for Pav if he happens to be reading. As I'm very rusty on shell scripts now, is there a set of scripts for starting and stopping boinc_client? It would be good to have it start automatically after any power failure. Also, the only switches I used were -daemon and -return_results_immediately, the latter because I want to see the outcome as soon as it finishes :). Is that all I really need? I'm not intending to do any local monitoring on the FreeBSD box as it's easier to leave it headless and monitor over the network from a windows box. Which reminds me, does anybody know if there is some syntax for the file "remote_hosts.cfg" to say that any box on the local LAN is allowed to talk to the boinc_client? Putting them all in one host per line seems a bit tedious :).

Cheers,
Gary.

nochjemand
nochjemand
Joined: 6 May 05
Posts: 28
Credit: 402,401
RAC: 0

Hi, RE: As I'm very

Message 38021 in response to message 38020

Hi,

Quote:
As I'm very rusty on shell scripts now, is there a set of scripts for starting and stopping boinc_client?

Yes: /usr/local/etc/rc.d/boinc.sh

Edit /etc/rc.conf and add this lines:
boinc_enable="YES"
boinc_flags="-allow_remote_gui_rpc" # only if needed

The Scripts under /usr/local/etc/rc.d will be start|stop by BSD-Init.
If you need to start boinc manuell:
/usr/local/etc/rc.d/boinc.sh start
/usr/local/etc/rc.d/boinc.sh stop

More info in the manual rc(8)

CU

Martin

Dave Burbank
Dave Burbank
Joined: 30 Jan 06
Posts: 275
Credit: 1,548,376
RAC: 0

RE: Which reminds me, does

Message 38022 in response to message 38020

Quote:
Which reminds me, does anybody know if there is some syntax for the file "remote_hosts.cfg" to say that any box on the local LAN is allowed to talk to the boinc_client? Putting them all in one host per line seems a bit tedious :).

I recall reading somewhere that if you leave the file 'remote_hosts.cfg' blank (no IP adresses), any computer can access that host over a LAN. I have never tried this so I don't know if it'll work, I suggest backing up 'remote_hosts.cfg' if you already have many IP adresses listed.

There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5,833
Credit: 108,119,863,887
RAC: 33,457,006

RE: Yes:

Message 38023 in response to message 38021

Quote:

Yes: /usr/local/etc/rc.d/boinc.sh

Of course, thanks. You've jogged my memory and the mechanism is coming back to me now. I hadn't realised just how much Windows rots your brain :).

I should have realised that all good packages install those scripts automatically and gone looking for them.

Cheers,
Gary.

Dave Burbank
Dave Burbank
Joined: 30 Jan 06
Posts: 275
Credit: 1,548,376
RAC: 0

Take a look at this excerpt

Take a look at this excerpt from the BOINC web site:

Quote:

Remote host restriction

By default the core client accepts GUI RPCs only from the same host.

You can allow remote hosts to control a core client in two ways:

* If you run the client with the -allow_remote_gui_rpc command line option, it will accept connections from any host. This is not recommended unless the host is behind a firewall that blocks the GUI RPC port (1043).

* You can create a file remote_hosts.cfg in your BOINC directory containing a list of allowed DNS host names or IP addresses (one per line). Those hosts will be able to connect. The remote_hosts.cfg file can have comment lines that start with either a # or a ; character as well.

There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman

Pav Lucistnik
Pav Lucistnik
Joined: 7 Mar 06
Posts: 136
Credit: 853,388
RAC: 0

Yes, I'm reading this thread,

Yes, I'm reading this thread, Gary :)

You could have installed einstein app from it's own port too, it's in /usr/ports/astro/boinc-einsteinathome. It would pull in compat5x libs automatically for you.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.