Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
Taking what you said literally, no. "enabling" sounds like "starting" to me rather than "setting to start on boot". httpsd? Not a real service name. Graphical mode? Don't see how that relates to starting a service. If you wrote a suitably informed post and mentioned what you've actually done, what you clicked / typed and said what distro you did it on then we could get further quicker, but on a distro like redhat you'd run "chkconfig httpd on" to make it start on boot.
Nothing to do with networking at all. moved to Linux - Newbie
will the command service httpd restart the apache service if i enable httpsd service in graphical mode
Graphical mode has nothing to do with services running, starting, etc. If the command you mean is "service httpd", that will do nothing. If you mean "service httpd restart", that will stop, then restart the service. HTTPS services are started if you've configured them to...otherwise, it'll just be on whatever port you run your regular http services.
Please write a clear question, and put relevant information in it, like version/distro of Linux, and what you're trying to accomplish.
Nothing to do with networking. Moved to Linux - Newbie.
We can't tell you how to do that, that is all background knowledge on apache which you get from buying a book on apache, reading the apache howto at tldp.org or other reference information very readily available online.
Last edited by acid_kewpie; 12-26-2009 at 01:40 PM.
TB0ne, /etc/httpd/httpd.conf has all your configuration for your server, and /srv/httpd/htdocs/ should contain all of your html.
No, sorry, it doesn't.
httpd.conf has your basic configuration, which tells the Apache engine what OTHER config files to pull in. Those specific ones (like loadmodule, ssl-global, etc.), have module-specific options. Unless you're running a very old Apache server, options have been spread out over multiple files for quite some time now. Also, it may be under /etc/httpd for YOU, but it isn't for me...mine are /etc/apache2, and I've seen different locations, depending on the distro. You can also put the files ANYWHERE YOU'D LIKE, by changing the config/startup script. Which is a safer thing to do.
Second, /srv/httpd/htdocs might, again, be where YOUR docs are, but not where MINE are. Even if that's the system default for you, that's not the case for openSUSE, and certainly not the case if someone decides to put them in another, totally random location.
In your previous post, you mentioned "etc/init.d/rc.d/rc.httpd". "/etc/init.d/apache2" has been used on RedHat, SUSE, FC, CentOS, and probably some other distros, for some time, as the startup script. I don't even HAVE an rc.httpd file on ANY of my systems, and Apache is starting and working fine. 90% of them have not been changed from system defaults, either, since they're not facing the Internet.
Why would anyone ever assume that the way Slackware does *anything* is default somewhere else?!
Agreed. Also, I'm not sure, but I don't think that even Slackware handles a "modprobe" statement as permanent...that is, living through a reboot. I'm fairly certain that you still need to put something in modprobe.conf, as in most other distros...