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.
Well its actually the string the program is using in its wrapper check, if the program doesn't specify anything or you are using external wrappers then it defaults to the name of the program. So in this instance I'd guess your are using an external wrapper and your tftpd program is called in.tftpd.
tcp wrappers provides both a library and a program
if programs use the tcpwrappers library they can set their wrapper string to something arbitrary, by wrapper string I mean the string you use in the host.deny host.allow files (this would be using the wrappers internally to the program).
if you use the program for tcp wrappers (usually tcpd) then the wrapper string is set to the name of the program you are wrapping.
The second example in the tcpd manpage gives an idea of the second usage (which I referred to as "using external wrappers").
Why is it in.tftpd and not just tftpd? Can someone please explain?
Why it is not in.telnetd too instead of just telnetd?
Fernandoch,
These basic services were typically started by a master TCP listener/launcher program called "inetd", thus the in. prefix.
Some systems still use inetd, while many of today's Linux distributions typically use xinetd, a more modern replacement for inetd.
The idea is - rather than start all the services at boot time, start them only when a network connection is initiated. And once the network connection was terminated, inetd would terminate the service and go back to a listening state. This saved valuable system memory, but it had the downside of creating a delay before the service was ready to service a request.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.