Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
It is in the newest version of Apache, installed by default, and it works as I tested it on my hosting plan.
What is the purpose of it and is it something outdated and a backward compatibility thing? I think that all the things that it does can be achieved with systemctl too?
It is a "front end to the Apache server". "It is designed to help the administrator control the functioning of the Apache httpd daemon."
How does it work? There is no good info about it on the Internet.
Last edited by AdultFoundry; 12-19-2015 at 03:35 AM.
The page you pointed at is literally the manual page for the command. So unless you clarify what you mean with "There is no good info about it on the Internet" that's just plain wrong. Also, unless / until you can 'sudo systemctl configtest httpd.service;' 'sudo apachectl configtest;' still has its role to play.
I meant that I couldnt find info about why it is needed, but I guess the commands that you mentioned have its use. So, like 80% of what it does can be achieved with systemctl, and 20% is still useful, type of thing. So that 80% of what it does could be probably considered outdated, probably... I dont want to sound like I am too particular about things, but I am going over a book and some other materials, and I try to figure out all the smaller things like this (second one so far, there is not a lot of this) that I dont understand.
Last edited by AdultFoundry; 12-19-2015 at 05:18 AM.
Clear. Try to see it like this: 'systemctl' ships with systemd. That means it applies to Linux distribution versions that use systemd (so fore example Fedora-server, CentOS 7 but not CentOS 5 or 6). 'apachectl' OTOH is provided by the Apache foundation httpd package. It is a distro-agnostic command, and will work on any OS that exposes the command.
How does it work? There is no good info about it on the Internet.
It is just a shell script so you can peruse the source with "less" and even if you do not program still get something out of it. One of the reasons there is not much about it on the net is that it is pretty simple.
As unSpawn mentions, it's there for cross-platform compatibility. apachectl will be present on the Linuxes, the BSDs (even OS X), and Solaris. So if you use it, it will be the same more or less everywhere. While the disto you are actually using might have something that supercedes it, that will not be portable. But it's not a big deal either way.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.