Need help running 2 CLIs under Linux

[Swanny]

Hello all,

I just put Mandrake 9.1 on my old BP-6 Celery rig. I'm trying to get SETI to run 2 processes, but can't. I have it set up in two seperate folders, but the second one keeps using the first's folder so they can't run seperately. The paths are:
'/home/swan/SETI 0/setiathome0' -proxy 10.51.5.28:5517
'/home/swan/SETI 1/setiathome1' -proxy 10.51.5.28:5517

So how do I keep them running seperately? I'm pretty new to Linux, so keep all suggestions step by step, please. I've read the readme on this topic, but I don't understand what it is saying.

Also, is there a switch that runs the processes on seperate CPUs? I didn't see one in the readme where all the other switches are.



Thanks,
Swan

 

[Ken g6]

SETI runs in the folder you launch it from. You could even have one "setiathome" program in /home/swan, cd to SETI0 and SETI1, and run ../setiathome from each folder.

I'm not sure about the CPU affinity.

 

[Swanny]

Originally posted by: Ken_g6
SETI runs in the folder you launch it from. You could even have one "setiathome" program in /home/swan, cd to SETI0 and SETI1, and run ../setiathome from each folder.

I'm not sure about the CPU affinity.

Ok, the paths I have in my 1st post are from the shortcuts on my desktop. How do I need to change them so the program will run in the /home/swan/SETI 0 or SETI 1 folders and be seperate?

 

[ProviaFan]

Originally posted by: Swanny

Originally posted by: Ken_g6
SETI runs in the folder you launch it from. You could even have one "setiathome" program in /home/swan, cd to SETI0 and SETI1, and run ../setiathome from each folder.

I'm not sure about the CPU affinity.

Linux should take care of that automatically.

Ok, the paths I have in my 1st post are from the shortcuts on my desktop. How do I need to change them so the program will run in the /home/swan/SETI 0 or SETI 1 folders and be seperate?

That depends on what desktop environment you're using. I would suggest starting your two SETI clients automatically from your initscripts. Unfortunately, I've had no experience with Mandrake 9.1, and each distro does the init scripts differently. But here are the commands you'd use (you could ask nicely in the OS forum and someone familiar with your OS could point you in the right direction).

To set up the SETI client One Of The Right Ways (TM):

cd /usr/bin
mkdir seti
Then as root download the SETI client in this folder.
mkdir 01
mkdir 02
cd 01
Run the SETI client the first time with whatever config switch it needs to get it set up.
cd ../02
Run the SETI client again with the config switch that it needs to get set up.

Now for the commands that go wherever they tell you in your init scripts...

cd /usr/bin/seti/01
../setiathome -proxy 10.51.5.28:5517 &
cd ../02
../setiathome -proxy 10.51.5.28:5517 &

Hope this works (it should work in theory but I run F@H on my Linux box and only used the Linux SETI@Home client a long time ago so I can't remember how it works). Good luck with your adventure of learning Linux.

 

[Swanny]

Thanks jliechty, but I'd rather just do it in the GUI, as my own user, and with shortcuts on the desktop instead of scripts to run it at logon. What I really need is to know how to make the program run in it's own folder. Everything else is set up the way I want it.


Thanks,
Swan

 

[Swanny]

Ok, I did what jliechty said. The only problem is that I can't run the programs from my user, only from root (in the command line environment). What did I do wrong? I'd like to be able to run them in the KDE Konsole. That way it saves the session when I shut down and they start back up again after reboot.

The error message I get when I try to run from my user is that the lock.sah file is already in use. I know that can't be true since this is right after a reboot.


Thanks,
Swan

 

[n0cmonkey]

#!/bin/bash


cd /home/swan/SETI0
./setiathome0 -proxy 10.51.5.28:5517 > /dev/null 2>&1
cd ../SETI1
./setiathome0 -proxy 10.51.5.28:5517 > /dev/null 2>&1


Save that as something along the lines of seti.sh, set executable permissions, and run it like: ./seti.sh and report errors here.

I believe lock.sah is there when the process is already running. If it did not exit cleanly, lock.sah will be in the directory possibly keeping you from running Seti multiple times. Check their readmes though.