Kyle Hargraves wrote:
>> service inetd status
>> or
>> service xinetd status
>
>
> Now the follwing is weired !
>
> [root@purcell xinetd.d]# service inetd status
> inetd: unrecognized service
>
> BUT
oops, should have been:
service inet status
>
>
> [root@purcell xinetd.d]# ps aux |grep inet
> root 369 0.0 0.3 1100 520 ? S Jan21 0:00 inetd
> root 5888 0.0 0.7 1940 944 ? S 10:58 0:00 xinetd -reuse -pi
>
> Now, there are appropriate entries in /etc/inetd.conf for telnet but
> they don't seem to observed. There is nothing in xinetd.d for telnet
> which is probably the problem. That is, it seems that xinetd seems
> to have taken over. (BTW I started it from inet.d)
>
> could someone send me an /etc/xinetd.d/telnet.conf please ?
There may only be very few people that have ever set-up telnet, because
of the security issue.
>
>
> Also, someone asked about the security level
>
> [root@purcell xinetd.d]# echo $SECURE_LEVEL
> 4
>
To access your telnet server you would therefore need an appropriate
entry in hosts.allow:
telnetd:youripnumberhere
Andreas
--
Prof. Dr. Andreas J. Guelzow
Chair of Science
Concordia University College of Alberta
[EMAIL PROTECTED]
http://www.math.concordia.ab.ca/aguelzow
