Posts by Peter Jeremy

1) Message boards : News : Added FreeBSD applications (Message 51265) Posted 30 Sep 2011 by Peter Jeremy Post: I detached and re-attached and only got the N-body client. On the positive side, v0.69 successfully processed its initial work-unit and is working on a second work-unit. Thanks for your efforts.
2) Message boards : News : Added FreeBSD applications (Message 51261) Posted 30 Sep 2011 by Peter Jeremy Post: My test Separation task is running and I'll let you know how it turns out. It completed and validated correctly. Unfortunately, I'm not sure of the correct process to disable only part of a project.
3) Message boards : News : Added FreeBSD applications (Message 51251) Posted 28 Sep 2011 by Peter Jeremy Post: Thanks for that, they now both download. Unfortunately, the N-body client instantly has an assertion failure: Assertion failed: (j < argc), function mwFixArgv, file /home/matt/milkywayathome_client/milkyway/src/milkyway_util.c, line 489. See http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=117646922 and http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=117680728 My test Separation task is running and I'll let you know how it turns out.
4) Message boards : News : Added FreeBSD applications (Message 51238) Posted 27 Sep 2011 by Peter Jeremy Post: This still isn't quite right. The configure script for boinc-client-6.4.5 maps a target type of "amd64" to "x86_64" and then maps various machine types to "pc", resulting in "x86_64-pc-freebsd", rather than "amd64-pc-freebsd". These mappings all appear to be part of the standard configure script - which isn't changed by the FreeBSD port. Could you please copy the existing amd64/x86_64 FreeBSD clients to "x86_64-pc-freebsd".
5) Message boards : Number crunching : FreeBSD MilkyWay port silently fails (Message 51230) Posted 27 Sep 2011 by Peter Jeremy Post: I have recently discovered that the FreeBSD milkyway port (boinc-milkyway-0.18d_3,1) no longer works - whilst workunits appear to execute normally, they show up as "validate error" on the tasks list. Looking back, this appears to have been going on for several months. I've had a look at a couple of other people in the FreeBSD team[0] and there's only one person with a functional FreeBSD client[1] and it's not clear how his system is different. If this client version is too old for current workunits, would it be possible to prevent new workunits being forwarded as the current situation just wastes everyone's (including the MilkyWay project's) time and resources. If this client version should still work, could you please look into why workunits are consistently failing. Note that I'm aware that there is supposed to be an "official" FreeBSD client but it will not work for me - I've reported that in another thread. [0] http://milkyway.cs.rpi.edu/milkyway/team_members.php?teamid=581&offset=0sort_by=expavg_credit [1] http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=289084
6) Message boards : News : Added FreeBSD applications (Message 51229) Posted 27 Sep 2011 by Peter Jeremy Post: Thank you for that. Unfortunately, the FreeBSD client doesn't appear to work - at least for me. On my FreeBSD-8.2/amd64 host, attempting to attach to MilkyWay gives the error: Tue 27 Sep 19:24:50 2011\|Milkyway@home\|Message from server: This project doesn't support computers of type x86_64-pc-freebsd Could you please investigate