Hello, Please note that I am unable to telnet to a newly installed beta 2 node. Regards, _______________________________________________________________________ Joseph Kotran Lead Systems Administrator Lockheed Martin E-mail: jkotran.com Advanced Technology Laboratories Phone: 856.338.4327 1 Federal St A&E 312 Fax: 856.338.4121 Camden NJ USA 08102 Web: http://www.atl.lmco.com
Have you enabled telnet either via chkconfig or setting 'disable=no' in /etc/xinetd.d/telnet after installing the package and then restarted xinetd?
Security bites! :-] (and I'm all for heavy biting)
Hello, I did enable telnet in /etc/xinetd.d/telnet and I sent a HUP signal to the xinetd. I recently restarted xinetd and I can now telnet to the computer. Does xinetd require a restart when you change its configuration? I think that this would cause problems on a server that is accessed by many users. I think that a key service such as inetd should always be running. Regards, Joe Kotran
xinetd should run by default, but a SIGHUP does not restart xinetd. This is a behavior change between inetd and xinetd -- from xinetd(8) SIGHUP causes an internal state dump (the default dump file is /tmp/xinetd.dump; to change the filename, edit config.h and recompile). Therefore, you must do a restart of the service to get the configuration files reread. This is identical behavior to 7.0 except for the fact that telnet is not enabled by default due to security considerations.
This defect is considered MUST-FIX for Florence Gold release
Er.. '/sbin/service xinetd reload' (which sends a SIGUSR2) works just fine, doesn't it? Seems like NOTABUG to me..
That was my thinking but I was going to let Jeff or Joseph make the call :)
We have consensus.