From: J Sloan <jjs@pobox.com>
To: linuxlist@visto.com
Cc: linux-kernel@vger.kernel.org
Subject: [OT] Re: no inetd.conf file
Date: Sun, 25 Nov 2001 21:21:59 -0800 [thread overview]
Message-ID: <3C01D177.98E82405@pobox.com> (raw)
In-Reply-To: <3BE1CB8E0013F650@iso2.vistocorporation.com> (added by administrator@vistocorporation.com)
rohit prasad wrote:
> Hi,
>
> I have installed 2.4.7 version of the kernel in my machine.
> I am facing a problem with telnet where all connections are refused.
Sounds like iptables and tcp wrappers are working?
Or you haven't enabled telnetd?
> When I grep for telnetd there is no telnetd running.
No, it wouldn't be running unless someone
has connected via telnet.
> If I try to start it the error reported is ,
>
> "telnetd:getpeername:socket operation on non-socket"
Right you don't start telnet by hand, its
invoked from inetd,or rather xinetd.
> I checked for the inetd.conf file it is not present in the /etc directory.
inetd has been replaced by xinetd, which
does seem to have some advantages.
> I want to know does this xinetd.conf file helps or,
> what else could I do to start telnetd.
Why not run "ntsysv", and select telnet?
Or, edit /etc/xinetd.d/telnet and then type
"service xinetd restart".
> I have done a "Everything" (All packages) installation of RH7.2 but no inetd.conf
That's as it should be
There is one thing - telnet is not a good thing
to have running, you really want to use secure
shell instead. If you have any concern at all
for security that is.
Finally, this has nothing to do with kernel
development, so try to reserve this list
for actual kernel related questions.
cu
jjs
next prev parent reply other threads:[~2001-11-26 5:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-26 4:06 no inetd.conf file rohit prasad
2001-11-26 5:21 ` J Sloan [this message]
2001-11-26 16:32 ` SpaceWalker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C01D177.98E82405@pobox.com \
--to=jjs@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxlist@visto.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox