KWSN Orbiting Fortress

[Yankton]

I've been meaning to post some guides to make it easier for those less technically inclined to run non-boinc projects. I mostly run linux, but I will attempt to make windows guides as well.


I'm starting with "distributed computing" or "dnet" which runs the projects for OGR-NG (OGR-26 and some day OGR-27) and RC5-72.

The project is located at http://www.distributed.net/

First you have to know what kind of computer you are using so you can download the correct client. The clients can be downloaded from http://www.distributed.net/download/clients.php

They do have a beta client download area as well, but if you are running hardware that would need one of them right now then chances are you don't need this guide. Note that there is a cuda beta for 32-bit windows which I have no experience with yet, and there is also a

For regular 32-bit windows download the file for [x86/Installer]
If you are using a really old version of windows (NT or 9x) then you will have to install the windows installer software first. If anyone needs this, please leave a message and instructions will be posted. Note that there is a cuda beta for 32-bit windows which I have no experience with yet, and there is also a beta for 64-bit windows but it has issues that should be corrected within a month.

For 64-bit windows I suggest using the 32-bit windows version until such time as the beta client is more stable or an actual release for it occurs.

For 32-bit linux you want the download for [x86/ELF]
For 64-bit linux you want the download for [AMD64/ELF]
For the PS3 (with linux) you want the download for [CellBE]

For those with non x-86/AMD-64 based processors (The X-86/AMD-64 lines include just about every Intel and AMD processor out there) you need to go down the list and find the correct one for your system. AMD-64 does NOT mean an AMD processor. AMD-64 is a generic term for 64-bit processors both AMD and Intel. Likewise for x-86 - Intel and AMD 32-bit

Download the appropriate file to your desktop

For windows, it's file extension is .msi - you should be able to double click it to install it, I haven't run this on a windows box but I will install it on my laptop later so I can give a rundown of the steps needed.

For linux, open up a terminal window. it should be already at your desktop but just in case:

[ohiomike]

To run it as a service under Linux:
1) copy the following script to /etc/rc.d/init.d/dnetc
2) chmod #777
3) ckconfig

------Script Below This Line-----------------
#!/bin/sh
#
# dcnet - start and stop the dcnet client daemon on Unix
#
# Usage: dnetc { start | stop | status | restart }
#
# chkconfig: 345 71 29
#
### BEGIN INIT INFO
# Provides: dnetc
# Required-Start: $network
# Required-Stop: $network
# Default-Start: 3 4 5
# Default-Stop: 0 1 2 6
# Description: This script starts the local dcnet client as a daemon
### END INIT INFO
#
########################################################################

# Note: If anyone else uses your machine create a user 'dnetc_user' and use it
DNETCUSER=root

# Note: Change to point at the dir where dnetc is installed
DNETCDIR=/MC/DC-Compute/dnetc507-linux-amd64-elf
DNETCEXE=/MC/DC-Compute/dnetc507-linux-amd64-elf/dnetc

# Note: You may need to create the /subsys dir on some versions of Linux
LOCKDIR=/var/lock/subsys
export TERM dumb

# Init script function library. This stuff is Red Hat specific,
# but if the functions are not found we create our own simple replacements.
# (The idea for replacing the functions comes from OpenAFS. Thanks guys!)

if [ -f /etc/rc.d/init.d/functions ] ; then
. /etc/rc.d/init.d/functions
else
export PATH=/sbin:/bin:/usr/sbin:/usr/bin
function echo_success () { echo -n " [ OK ] " ; }
function echo_failure () { echo -n " [FAILED] " ; }
function echo_warning () { echo -n " [WARNING] " ; }
function killproc() {
PID=`pidof -s -x -o $$ -o $PPID -o %PPID $1`
[ $PID ] && kill $PID ; }
fi

## Locate the working directory

if [ ! -d $DNETCDIR ]; then
echo "Cannot find dnetc directory $DNETCDIR "
exit 7
fi

export PATH=$DNETCDIR:/usr/local/bin:$PATH

if [ ! -x "$DNETCEXE" ]; then
echo "Cannot find an executable for the dnetc client."
exit 2
fi

## Functions: $1 is one of start|stop|status|restart

case "$1" in
start)
echo "Start dnetc"
cd $DNETC

if [ -f $LOCKDIR/dnetc ] ; then
echo -n "Another instance of dnetc is running (lockfile exists)."
echo_failure
echo
exit 4
fi

echo -n "Starting dnetc client as a daemon: "
su $DNETCUSER -c "$DNETCEXE" &
sleep 1
PID=`pidof -s -x -o $$ -o $PPID -o %PPID $DNETCEXE`
if [ $PID ]; then
touch $LOCKDIR/dnetc
echo_success
else
echo_failure
fi
echo
;;

stop)
echo "Stop dnetc"
cd $DNETCDIR
if [ ! -f $LOCKDIR/dnetc ] ; then
echo -n "dnetc is not running (no lockfile found)."
echo_success
else
echo -n "Stopping dnetc client daemon: "
killproc $DNETCEXE && echo_success || echo_failure
# clean up in any case
rm -f $LOCKDIR/dnetc
fi
echo
;;

restart)
echo "ReStart dnetc"
$0 stop
$0 start
;;

status)
echo "Get dnetc Status"
PID=`pidof -x -o $$ -o $PPID -o %PPID dnetc`
if [ "$PID" == "" ]; then
PID=`pidof -x -o $$ -o $PPID -o %PPID $DNETCEXE`
fi
if [ "$PID" != "" ]; then
echo "dnetc client is running (pid $PID)."
else
if [ -f $LOCKDIR/dnetc ]; then
echo "dnetc is stopped but lockfile exists."
else
echo "dnetc client is stopped."
fi
fi
;;

*)
echo "Usage: dnetc {start|stop|restart|status}"
exit 1
esac

exit
_________________

Resident Linux fan and credit ho >My Shrubbers<
Proud member of the "Fry a CPU for breakfast club"

[Yankton]

OGR-26 is officially completed. But OGR-27 has just started.

It appears the old clients will not do OGR-27, so if you are into this project, please download and install the 509 client.


_________________
Some days are worse than others.

[Sir Papa Smurph]

Wow,

Thanks guys....


I think I will stick with windoze
_________________
a.k.a. Licentious of Borg.........Resistance Really is Futile.......
and a Really Hoopy Frood who always knows where his Towel is...

[Yankton]

it's a lot easier than it looks.


_________________
Some days are worse than others.

[Idan]

Is there any way to know when a WU or a packet will finish as they call it?
_________________
Anyone for Crunch?

[Yankton]

unlike RC5, the ogr unit run times will vary. I would expect them to take at least a couple of hours each on a newer box. They are taking a little over 4 hours each on my quaddie but it is sieving at the same time...
_________________
Some days are worse than others.

[Idan]

[Yankton]

Are you observing it in a terminal to see when it finishes 1 unit of the batch it downloads? If you're waiting for a whole batch to finish then we are talking a whole other timescale. My PS3 downloaded 1000 units which I think will take a couple of weeks (Though it wil be worth several hundred thousand points at the current rate), while the quad downloaded enough for about four-five days.

If you are observing it, you can halt it and then submit what it has already with the -flush switch. Or you can wait till it submits the first batch.
_________________
Some days are worse than others.

[Idan]

[Yankton]

Sweet! Crunch on!


_________________
Some days are worse than others.

[Yankton]

If someone doing ogr-28 can verify the setup hasn't changed since this written? Can't imagine they'd change the client config much. I'll start running boxes out of work and see about checking it myself soon but since people are poking at this already.


_________________
Some days are worse than others.

[Plomos]

Its very simple to run on windows. There is no install, just a zip archive. Extract the zip somewhere and then run dnect.exe and it will launch the app. It will ask you what email address you want to use, enter it and push enter.

then it will start running. Within the client click on client in the top left and go to configure. From here you can change all the options, like how many cores it runs, your ID, which project it prioritizes etc
_________________