[SkiBikeSki]

I want to run two copies of the SETI CLI for Darwin 1.2 on my friends dual 500, and I am worried about a conflict between the two. I run a single version of SETI on my 867, and it stores its .sah files in my users folder. I would imagine that another copy of SETI put the files in the same place, creating a conflict. I read in the readme that SETI is suppose to store those files in the same directory as the app, but it does not.

So what I'd like to know is, does this happen to anyone else, and can I specify a directory for those files?

[reader50]

The CLI version always places the data/key files in the same directory that the application runs from. I am thinking that either the files you found in your User directory got there another way (copied there during a backup perhaps), or that you ran the client from a crontab without first cd'ing to the client directory.

Regardless, it is safe to try two copies of SETI@home. SETI uses a lock file to make sure only one client has access to the data files at a time. The second copy will quit immediately with an error message.

I have run up to 8 CLI clients at a time for testing purposes, each from it's own folder. Each was started manually, with no problems. And the data files were indeed stored in each client's folder.

[ 10-17-2001: Message edited by: reader50 ]

[SkiBikeSki]

I didn't think it would be unsafe to run two copies, I just didn't want the same unit to be crunched twice, at the same time. That would be a waste.

And those files in my users folder weren'y copied there. They are the files that the CLI does use. If I remove them the the CLI asks me to login again. I haven't done anything with the cron. I'll try downloading it again, maybe I got a bad copy.

[ 10-18-2001: Message edited by: SkiBikeSki ]

[reader50]

CLI problem solved. You are opening a Terminal window, then dragging the SETI@home binary in. This starts the CLI client, but leaves the directory set to your user directory. By default, all Terminal windows are set to your user directory when they are first opened.
[list=1][*]Instead, type "cd " (don't forget the space after the "cd")[*]Drag the CLI client's enclosing folder into the Terminal window.[*]Click in the Terminal window to make it active again, then press return. This sets the terminal window to the client's folder.[*]Type "./setiathome" and press Return. That is a period followed by a slash, and it is the unix Run command. Optionally, you can add the "nice" or "verbose" tags, etc, before pressing Return.[/list=a]
Your client will now start up. And the files will be stored in the client's local folder.

Give a holler if it still messes up.

[SkiBikeSki]

That fixed it. I guess that means the final answer is not that SETI places its files next to the app, but in whatever folder the terminal is set to. Thanks for the help. Now I'm using setidockling, that makes launching it even easier.