shame on the previous respondant.. you shouldn't need to reboot the whole machine for ONE service. Daemon's would be in the PS listing, and since its an XINETD provided service, you...
only need to restart XINETD to have changes take effect!
/etc/init.d/xinetd restart
Under most normal circumstances, XINETD will restart without dropping you, leaving your socket open, its that smart.
Also, you can further attempt to restrict access by building an /etc/hosts.deny file and in it put
in.telnetd : all
** in the hosts.deny file, listings like the one above will DENY ALL ip addresses to the service "in.telnetd"
in some cases you can also list it in the /etc/hosts.allow file like this
in.telnetd : all : DENY
wording, syntax, etc. are important and which file you use. hosts.deny has precident over hosts.allow.
if you open TWO ssh sessions, in one, su to root, and then TAIL your log file. In the other window, issue the /etc/init.d/xinetd restart command.
if there is a syntax error, you will see it show up in your messages file (that you have tail'd in your other connection.
tail -f /var/log/messages
(must be root to view messages file if your system is standardly secured, and yes, you could just tail -100 to see the last one hundred lines, but if you follow the tail of the file, you can see your changes as they are made)