[edddeduck]

I cannot run two instances of seti...

[localhost:~] duck% /seti2/setiathome
Couldn't get lock file. This is probably because
another instance of SETI@home is running in this directory.
Each instance of SETI@home must run in a separate directory.

The other version was in a folder called seti1 the weird thing was it was creating temp files in my home directory any clues???

I am sure this used to work just fine...

Cheers Edd

EDIT su appears broken ie when I type su it asks for pass when i type it in it says sorry... but that is my pass and I am the adim of the machine.. Hope this might help EDIT

[ 12-18-2001: Message edited by: edddeduck ]

[reader50]

You are having problems running two instances of SETI because you are not first setting the Terminal window to each folder.

When you open a new Terminal window, it comes up set to your home directory. Type "cd " in a new Terminal window, drag the Seti1 folder into the window, click in the Terminal window again, and press Return. That window will now be set to the Seti1 folder. You can now type "./setiathome", it will fire up, and it's data files will be in that folder.

Do this with each additional seti folder, and get as many CLI clients running as you wish.

"su" may not work because the root user has not been enabled yet. Go to our Seti CLI Tips page, and scroll down to the "Enable Root User" section. That should do it.

[ 12-19-2001: Message edited by: reader50 ]

[edddeduck]

Cheers kind of stupid of me not to see that one... Was very tired was 4am in the UK at the time. The su problem is a wierd problem but unrelated I feel...

Cheers Edd