• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Having trouble with seti in linux

E

Epyon9283

Senior member
Im sot of new to linux and I want to have seti starting when the computer starts. What would be the best way to do this?
 
This is startup problem #2 you asked and didnt provide enough detail to. But I decided to be nice this time and looked at your rigs. I hope thats accurate 🙂

Add a script to /etc/init.d. The script should be something like (script is between the ---'s which you should not include 🙂):

-------------------------------
#!/bin/bash


cd /home/your-user/seti/
./setiathome 2&1> /dev/null
--------------------------------

Name the file something like eccp.sh. Then create a simlink in /etc/rc?.d (where ? is the runlevel you run at). This simlink should be something like S99eccp (which is what I have it as). The S is important. Im not sure what the 99 means in mine though, but the others were numbered so I numbered this one. I am running Debian, but it should be similar for Mandake.

Let me know if you have any problems or just never reboot 🙂
 


<< This is startup problem #2 you asked and didnt provide enough detail to. But I decided to be nice this time and looked at your rigs. I hope thats accurate 🙂

Add a script to /etc/init.d. The script should be something like (script is between the ---'s which you should not include 🙂):

-------------------------------
#!/bin/bash


cd /home/your-user/seti/
./setiathome 2&1> /dev/null
--------------------------------

Name the file something like eccp.sh. Then create a simlink in /etc/rc?.d (where ? is the runlevel you run at). This simlink should be something like S99eccp (which is what I have it as). The S is important. Im not sure what the 99 means in mine though, but the others were numbered so I numbered this one. I am running Debian, but it should be similar for Mandake.

Let me know if you have any problems or just never reboot 🙂 >>


yeah i added a script to my rc2.d for something else, i just used S40 or soemthing, i dont even know what the S## is for :Q

it works, but problem is, it also tried to run it when i shutdown 😛

oh well no harm done.😛
 
Where are ya Poof? 😉

:Q

LOL!

Sorry! I was over on DSLR reading about how Comcast is spying on me! :| 😉

And thanks n0c! 😀

BTW, know this - who boots Linux anyway???????? 😛
AND... Whenever I want to start something like that at boot (boot = power outage.. LOL), I stick it in either boot.local or rc.local, including a "&" at the end of the commandline in order to make sure it forks into the background. 🙂
 


<< Where are ya Poof? 😉:QLOL!Sorry! I was over on DSLR reading about how Comcast is spying on me! :| 😉And thanks n0c! 😀BTW, know this - who boots Linux anyway???????? 😛AND... Whenever I want to start something like that at boot (boot = power outage.. LOL), I stick it in either boot.local or rc.local, including a "&" at the end of the commandline in order to make sure it forks into the background. 🙂 >>



Thats what Im here for. In Debian I didnt notice an rc.local or anything of the sort so I didnt have that option (and I dont feel comfy enough with SysV init to set it up) or I would have done it. The "2&1>/dev/null" should send all output to /dev/null and fork it into the background. I do it that way because of eccp. It likes to print to the screen even when its put in the background.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top