Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Place /usr/loca/alpha/bin/alpha.sh in your /etc/rc.local file (again, this depends on your distro, but for the most part your distro should have this file).
So using your favorite text editor open up your rc.local file, and place this line in there:
/usr/loca/alpha/bin/alpha.sh
i think the questin is how will chkconfig know where is that alpha you are trying to run... never used it like that. only services which are located in /etc/init.d
chkconfig can only be used with proper daemon control services, not general applications. if running "/usr/local/alpha/bin/alpha.sh" works on a command line then it MUST work running it in rc.local, just remember to add a & to the end to make sure it forks.
alpha is started when system initiates, i can locate it in processes, but it is not working properly.
actually, "alpha" is a web server. i added
/usr/local/alpha/bin/alpha.sh start &
to /etc/rc.d/rc.local, rebooted the machine, but alpha is not serving as it is expected to. i ran ps -axu, and found it among the process
When you run ps -aux who does it say the process is running as? When you run the process by hand after the install (assuming it's not in rc.local) what user do you run it as?
if "ps -aux | grep alpha" does not return a line about alpha, does it mean alpha is not started at all?
that is the case now, though i have added "/usr/local/alpha/bin/alpha.sh start &" to /etc/rc.d/rc.local
what do you think i should do?
I would start alpha like normal from a command line, see if I can find what it looks like using ps, and then try to find that same info using ps after I try rebooting with alpha.sh in rc.local. That's the vague answer to a vague alpha.sh.
I would wonder why rc.local isn't kicking stuff off the way it should. Maybe you could try putting other scripts in there to see if alpha.sh has problems or if rc.local has problems? Maybe just an echo "HI I'M IN RC.LOCAL" for you to watch for during boot?
I'm new to Linux too, this is just stuff I would look for.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.