| View previous topic :: View next topic |
| Author |
Message |
John Beardmore Guest
|
Posted: Wed Jan 19, 2005 7:30 am Post subject: Seti on Alpha Debian |
|
|
Have just installed seti at home alpha-unknown-linux-gnu variant on an
EV4 Alpha Debian v3r3 Alphaserver 2100 to test it and give it something
useful to do.
Having unpacked the file to /root/seti/alpha-unknown-linux-gnu, I ran
./setiathome
which terminated complaining that it couldn't get a lock file.
Thought this might be down to permissions on the directory so set those
to 777, but still no joy, same error.
Has anybody seen this problem and spotted a fix ?
Thanks, J/.
--
John Beardmore |
|
| |
|
Back to top |
Paavo Hartikainen Guest
|
Posted: Wed Jan 19, 2005 8:12 am Post subject: Re: Seti on Alpha Debian |
|
|
John Beardmore <wookie@wookie.demon.co.uk> writes:
| Quote: | Having unpacked the file to /root/seti/alpha-unknown-linux-gnu, I
ran
./setiathome
which terminated complaining that it couldn't get a lock file.
|
Try "./setiathome -nolock".
--
"pienena / Paavo "Rainbow Rat" Hartikainen
minusta / E-mail: pahartik@sci.fi
tulee / URL: http://www.sci.fi/~pahartik/
rotta" / EFnet: pahartik at #Atari and #LionKing |
|
| |
|
Back to top |
Keith Harwood Guest
|
Posted: Wed Jan 19, 2005 1:02 pm Post subject: Re: Seti on Alpha Debian |
|
|
Paavo Hartikainen wrote:
| Quote: | John Beardmore <wookie@wookie.demon.co.uk> writes:
Having unpacked the file to /root/seti/alpha-unknown-linux-gnu, I
ran
./setiathome
which terminated complaining that it couldn't get a lock file.
Try "./setiathome -nolock".
|
I had the same problem. -nolock just takes you bit further and it fails
again. I can't remember what the error was. I mentioned it in this forum
some time ago and also reported it to seti@home. I didn't get any response
and correspondence from someone else with the same problem suggests that
seti@home haven't done anything to either fix the problem or to find a
work-around.
Keith Harwood. |
|
| |
|
Back to top |
John Beardmore Guest
|
Posted: Thu Jan 20, 2005 3:28 am Post subject: Re: Seti on Alpha Debian |
|
|
In message <41ee0709$0$25421$afc38c87@news.optusnet.com.au>, Keith
Harwood <vitalmis@optusnet.com.au> writes
| Quote: | Paavo Hartikainen wrote:
John Beardmore <wookie@wookie.demon.co.uk> writes:
Having unpacked the file to /root/seti/alpha-unknown-linux-gnu, I
ran
./setiathome
which terminated complaining that it couldn't get a lock file.
Try "./setiathome -nolock".
I had the same problem. -nolock just takes you bit further and it fails
again. I can't remember what the error was.
|
Presumably some pretty low level problem opening files ?
| Quote: | I mentioned it in this forum
some time ago and also reported it to seti@home. I didn't get any response
and correspondence from someone else with the same problem suggests that
seti@home haven't done anything to either fix the problem or to find a
work-around.
|
It's a shame because seti used to work like a charm under Alpha Redhat
6.2 !
Mind you - I have a funny feeling that in those days you downloaded the
source and compiled it yourself ?
Any other 'public good' projects out there for the Alpha command line ?
Cheers, J/.
--
John Beardmore |
|
| |
|
Back to top |
Gary Heston Guest
|
Posted: Thu Jan 20, 2005 5:25 am Post subject: Re: Seti on Alpha Debian |
|
|
In article <41ee0709$0$25421$afc38c87@news.optusnet.com.au>,
Keith Harwood <vitalmis@optusnet.com.au> wrote:
| Quote: | Paavo Hartikainen wrote:
John Beardmore <wookie@wookie.demon.co.uk> writes:
Having unpacked the file to /root/seti/alpha-unknown-linux-gnu, I
ran
./setiathome
which terminated complaining that it couldn't get a lock file.
Try "./setiathome -nolock".
I had the same problem. -nolock just takes you bit further and it fails
again. I can't remember what the error was. [ ... ]
|
Perhaps it has something to do with ownership and permissions of the
files in the directory?
Gary
--
Gary Heston gheston@hiwaay.net
"Sept. 11, 2001, already a day of immeasurable tragedy, cannot be
the day liberty perished in this country." Judge Gerald Tjoflat |
|
| |
|
Back to top |
John Beardmore Guest
|
Posted: Thu Jan 20, 2005 2:59 pm Post subject: Re: Seti on Alpha Debian |
|
|
In message <10utr3jm8deq101@corp.supernews.com>, Gary Heston
<gheston@hiwaay.net> writes
| Quote: | In article <41ee0709$0$25421$afc38c87@news.optusnet.com.au>,
Keith Harwood <vitalmis@optusnet.com.au> wrote:
Paavo Hartikainen wrote:
John Beardmore <wookie@wookie.demon.co.uk> writes:
Having unpacked the file to /root/seti/alpha-unknown-linux-gnu, I
ran
./setiathome
which terminated complaining that it couldn't get a lock file.
Try "./setiathome -nolock".
I had the same problem. -nolock just takes you bit further and it fails
again. I can't remember what the error was. [ ... ]
Perhaps it has something to do with ownership and permissions of the
files in the directory?
|
Maybe. While I'm building the machine root is the only user, so I
changed the owner and group of setiathome to root and set the
permissions of the directory owned by root to 777 before invoking. I
can' see why that would fail to be able to open files, but O&P aren't my
strong point.
J/.
--
John Beardmore |
|
| |
|
Back to top |
John Beardmore Guest
|
Posted: Fri Jan 21, 2005 1:19 am Post subject: Re: Seti on Alpha Debian |
|
|
In message <41ee0709$0$25421$afc38c87@news.optusnet.com.au>, Keith
Harwood <vitalmis@optusnet.com.au> writes
| Quote: | Paavo Hartikainen wrote:
John Beardmore <wookie@wookie.demon.co.uk> writes:
Having unpacked the file to /root/seti/alpha-unknown-linux-gnu, I
ran
./setiathome
which terminated complaining that it couldn't get a lock file.
Try "./setiathome -nolock".
I had the same problem. -nolock just takes you bit further and it fails
again. I can't remember what the error was. I mentioned it in this forum
some time ago and also reported it to seti@home. I didn't get any response
and correspondence from someone else with the same problem suggests that
seti@home haven't done anything to either fix the problem or to find a
work-around.
|
Actually, -nolock got it going for me in this instance. Chugging away
nicely now.
Thanks all ! J/.
--
John Beardmore |
|
| |
|
Back to top |
Keith Harwood Guest
|
Posted: Wed Jan 26, 2005 8:55 am Post subject: Re: Seti on Alpha Debian |
|
|
John Beardmore wrote:
| Quote: | It's a shame because seti used to work like a charm under Alpha Redhat
6.2 !
|
I had seti two point something working under suse 6.1
| Quote: | Mind you - I have a funny feeling that in those days you downloaded the
source and compiled it yourself ?
|
I don't think it's ever been compile yourself. The seti people want to be
very certain that the code you execute is the code they want executed. |
|
| |
|
Back to top |
Keith Harwood Guest
|
Posted: Wed Jan 26, 2005 8:57 am Post subject: Re: Seti on Alpha Debian |
|
|
John Beardmore wrote:
| Quote: |
Actually, -nolock got it going for me in this instance. Chugging away
nicely now.
|
Hm. perhaps I should try again. Maybe they have changed something. |
|
| |
|
Back to top |
DiskMan Guest
|
Posted: Wed Jan 26, 2005 10:44 am Post subject: Re: Seti on Alpha Debian |
|
|
Well version 1 was opensource but ppl were hacking the code thinking they
know better and was screwing up seti packets .... so the stopped it.. Will L
G
"Keith Harwood" <vitalmis@optusnet.com.au> wrote in message
news:41f707b2$0$2201$afc38c87@news.optusnet.com.au...
| Quote: | John Beardmore wrote:
It's a shame because seti used to work like a charm under Alpha Redhat
6.2 !
I had seti two point something working under suse 6.1
Mind you - I have a funny feeling that in those days you downloaded the
source and compiled it yourself ?
I don't think it's ever been compile yourself. The seti people want to be
very certain that the code you execute is the code they want executed.
|
|
|
| |
|
Back to top |
DiskMan Guest
|
Posted: Wed Jan 26, 2005 10:46 am Post subject: Well you have to specify the IP... |
|
|
Of the seti server... I ran into this problem myself ... to fire it up just
use:
/setiathome -nice 15 -nolock -proxy 66.28.250.122
Here's a little init script to fire up Seti when ever you boot your
computer, just change the paths to reflect your own setup:
..lf 1 /etc/rc.d/init.d/seti
#!/bin/bash
# chkconfig: 2345 30 60
# Source function library
.. /etc/rc.d/init.d/functions
################################################
#This script is a sample script to allow the seti
#client to run as a service on a linux box.
#
#Install Notes :
#
# customize the two first variables of the script
# make a symbolic link from
# You have to link /etc/rc.d/rc.<your run level>/S99seti
# to this file to make it run.
# start the service (or reboot )
# check it works with the status option
#
#
#How this works ?
#
#When using the script, your seti client will always
#run in the same folder (that you can choose) ,
#this is a "clean" way to run it.
#The service can be:
# -launched with "/etc/rc.d/initd/seti start"
# -stoped with "/etc/rc.d/initd/seti stop"
# -restarted with "/etc/rc.d/initd/seti restart"
# -watched with "/etc/rc.d/initd/seti status"
# -be logged with "/etc/rc.d/initd/seti log"
#As the last option (log) in quite unsual,
#it is intended to be used with the cron daemon
#to allow users to log their progress in some file
#so that can get a good idea of there current score
#and progress.
#Here are the 2 lines to type in your crontab :
# SHELL=/bin/bash
# 30 0 * * * "/etc/rc.d/initd/seti log"
#You must have write permission on all the files
#to add it to your crontab.
#Author Stephane NICOLAS
#<snicolas@iad.ift.ulaval.ca>
#This program is distributed under the terms of the GPL.
#You can get a copy of it at
#http://www.fsf.org/copyleft/copyleft.html#translations
################################################
#This variable points to the client's executable directory
#change this value to define the location of your client.
#We do NOT need the client to be in your $PATH
SETI_CLIENT_DIR=/usr/scientific/setiathome-3.03
#This direcory contains the root of setiathome's workspace
#you can customize it.
SETI_DIR=/usr/scientific/setiathome-3.03
#This file is generated by setiathome and we need it
SETI_LOG_FILE=$SETI_DIR/state.sah
#this file is lock file we create to ensure one and
#only one client is launched
SETI_LOCK_FILE=/var/lock/seti.lock
case "$1" in
start)
echo -n "Starting computing seti: "
more ${SETI_DIR}/user_info.sah | awk -F = '$1 == "nresults" { print $2}'
cd $SETI_DIR
${SETI_CLIENT_DIR}/setiathome -nice 15 -nolock -proxy 66.28.250.122 >
/dev/null &
touch $SETI_LOCK_FILE
;;
stop)
echo -n "Shutting down seti: "
more ${SETI_DIR}/user_info.sah | awk -F = ' $1 == "nresults" { print
$2 }'
killall setiathome
rm -f $SETI_LOCK_FILE
echo
;;
restart)
$0 stop
$0 start
;;
status)
echo -n "Seti work unit completed: "
more ${SETI_DIR}/user_info.sah | awk -F = ' $1 == "nresults" { print $2}'
running=`ps -A | grep setiathome`
#thanks to Toan for this bug fix
if( [ "${running}" = " " ] )
then
echo "Seti client is not running."
else
echo -n "Seti client runs since "
echo ${running} | awk -F " " '{ print $3 }'
echo -n "The current work unit is completed at "
more $SETI_LOG_FILE | grep prog | awk -F "=" '{ print $2 } '
fi
echo -n "Last result returned at ("
more ${SETI_DIR}/user_info.sah | grep last_result_time | awk -F "(" '{
print $2 }'
echo ""
;;
log)
/bin/date >> $SETI_DIR/log
$0 status >> $SETI_DIR/log
echo "*******************************************" >> $SETI_DIR/log
;;
*)
echo "Usage: seti {start|stop|restart|status}"
exit 1
esac |
|
| |
|
Back to top |
|