Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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.
What is a different between "apachectl [start]" and "service httpd [start]"?
Not 100% sure; but apachectl uses the httpd script. With the service command uses the /etc/init.d/httpd startup script. Essentialy service httpd start and /etc/init.d/httpd start is the same thing. When you use apachectl you are using the script that came with apache. I think that the startup scripts uses apachectl...I'm not sure though...
In Any event I would use the "service" method or the /etc/init.d method becuase it will start the service as the user "www" (I belive). And apachectl starts it as the user starting it (bad).
Ya, use the service httpd ..., or the /etc/init.d/httpd ... command (same thing). They put the lock and pid files in the appropriate places.
Don't forget "service httpd configtest" which is the same as "apachectl configtest". It can save you from downtime when you typo in the conf files.
Ya, use the service httpd ..., or the /etc/init.d/httpd ... command (same thing). They put the lock and pid files in the appropriate places.
Don't forget "service httpd configtest" which is the same as "apachectl configtest". It can save you from downtime when you typo in the conf files.
I didn't know about 'configtest'! I would always do 'apachectl -t'
I ALWAYS do a a 'apachectl -t' (i.e. a config test) before I do a graceful...even when the change was small change...it has saved me plenty of times
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.