What is the difference between inetd and init.d

Williams 11 2 2 bronze badges. Thomas 5, 8 8 gold badges 23 23 silver badges 32 32 bronze badges. And that manufacturer can do things however they like for a myriad of reasons which is why you can and will find subtle differences such as this.

The rc is a framework which is largely followed by everyone giving out a linux distribution, but realize it is a framework and it really comes down to how they write all that code in the run commands to make the operating system start up and shutdown. The mention of the old way of SysVinit and now the current way of SystemD. These two items are and old way vs the new [modern] way of service and system management in linux that encompasses everything inclusive of start up to shut down.

But the code [files] that make this up resides under the run commands directory framework. And for backwards compatibility basically all new linux distributions running SystemD still support all the old SysVInit way of doing things by simply keeping the existing directory rc framework and linking [redirecting] the old sysvinit commands to the corresponding systemd ones I have not seen any yet that do not.

It's not one versus the other. They go hand in hand, the primary reason so that only one copy of a run command [script] is located in one place in RHEL7. It's all about managing the mess [of files]. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Does ES6 make JavaScript frameworks obsolete? Podcast Do polyglots have an edge when it comes to mastering programming Featured on Meta.

Now live: A fully responsive profile. Related Hot Network Questions. Question feed. In this article, we will discuss and solve following all queries one-by-one. What init is? What is systemd? Why init needed to be replaced? What features systemd will own. What is init? If you liked this article, then do subscribe to email alerts for Linux tutorials. If you have any questions or doubts? Related Posts.

If you planned to do so, what a better option than to stuff the very process that controls everything in a machine and is so large that it makes it very hard to detect its flaws… Reply. Why there was a need to replace init? Thanks you for good information Reply. Got something to say? Join the discussion. Cancel reply Have a question or suggestion? Comment Name Email Website Save my name, email, and website in this browser for the next time I comment.

Linux Distribution. Yes, Debian 8 codename Jessie will have systemd by default. Yes, but needs to be downloaded, installed and configure side with custom init. No Though it has not been adopted till now in slackware, Patric Volkerding has not shown any indication if it will be adopted or not.

Yes, needs to be installed and configured with Upstream. DBus Dependency — Mandatory. Device based Activation. Device dependency configuration with udev. Timer based Activation. Quota Management. Automatic Service Dependency Handling. Kills users Process at logout. Swap Management. SELinux integration. Support for Encrypted HDD. Static kernle module loading. Is it difficult to parse it out in a morning? Absolutely difficult.

Is it necessary to be so complicated. XINETD inherits the design of the inetd and modularity it, meaning that each service can exist in its own configuration file. Modular configuration means that you can distribute the service to multiple machines by copying the service to the XINETD.

D directory, or you can remove it in a similar way. You can even specify an additional include directory. But no problem, use inetd for RPC, and use xinetd for all other services. It's like hiring two operators, one speaking Spanish, the other speaking all the other languages. In a word, it is a program. There is nothing magical about handling inbound network connections. Can be handled using Perl, Python, or Java. XINETD is written in C, and it is as fast as its predecessor inetd, if not faster for example, the TCP wrapper does not have to be executed for each inbound connection; they are starting fashion into memory.

Because it is under development, XINETD security vulnerabilities can be quickly remedied, not as weak as inetd, which usually takes a long time to make up. Of course, XINETD is delivered with the source code, so you can review the source code and find out where it might be vulnerable. How do I use xinetd to define a service? D inherits these defaults and specifies its own parameters.

Here, the Telnet service is defined at the top-level, not in the subdirectory. This is great, this modularity allows for complex configurations. Just send a USR2 signal to it. What those parameters mean. Let's read through the entire list. You can also use man xinetd. General parameters Id The unique name of the service. The service name is specified before the curly braces, but the ID makes the logically identical service likely to have multiple protocols. This is a restricted use for temporary users.

On Red Hat Linux 7. Type This should actually be called a "special type" because it applies only to special services. Flags All the extra flags are placed here. Disable Unless you want to disable a service, always set it to "no". Red Hat Linux's chkconfig program turns the "disable" parameter on or off for you; on Red Hat, enabling and disabling specific services with Chkconfig may be simpler than manual methods. So for the example in Listing 2 above, Chkconfig will not turn telnet on or off at the request.

You can think of it as an error or attribute, depending on your point of view. This parameter can also be set to "raw" and "Seqpacket", but very rare. Wait If set to ' No ', xinetd will start a new handler for the service on each connection. In most cases, this parameter is "no". The handler name should not appear in the parameter, as in the inetd environment.

Port The port of the service. Therefore, a firewall-protected host can accept security traffic through a central xinetd forwarder without having to establish a connection to the external network. In some jobs, this feature can be used to perform failover services between two hosts.