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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
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
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.