<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: telnet in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930066#M46182</link>
    <description>&lt;BR /&gt;This problem likely happens if you have started a daemon from the telnet session which does not release the current tty and continues to use it as its default tty.&lt;BR /&gt;&lt;BR /&gt;If you are running some daemon then try to run it in the background with all tty operations redirected to /dev/null (or some where else).&lt;BR /&gt;&lt;BR /&gt;It should solve your problem. But i am not sure why it can not allow any more new telnet sessions.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Gopi</description>
    <pubDate>Thu, 29 Sep 2005 03:00:26 GMT</pubDate>
    <dc:creator>Gopi Sekar</dc:creator>
    <dc:date>2005-09-29T03:00:26Z</dc:date>
    <item>
      <title>telnet</title>
      <link>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930064#M46180</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;i cannot terminate telnet session to the remote machine, it just hangs and also it doesnt allow any more new telnet sessions. &lt;BR /&gt;&lt;BR /&gt;which process on the remote machine is suppose to handle this kind of satuation?&lt;BR /&gt;&lt;BR /&gt;if you have any docuements on How telnet works please share it with me.</description>
      <pubDate>Thu, 29 Sep 2005 02:33:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930064#M46180</guid>
      <dc:creator>Chakravarthi</dc:creator>
      <dc:date>2005-09-29T02:33:52Z</dc:date>
    </item>
    <item>
      <title>Re: telnet</title>
      <link>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930065#M46181</link>
      <description>it the remote machine is redhat:&lt;BR /&gt;then issuing command&lt;BR /&gt;service xinetd restart will restart (among others) also the telnet server.&lt;BR /&gt;Anyway the executable's name is in.telnetd&lt;BR /&gt;so issuing &lt;BR /&gt;ps -ef |grep in.telnetd should reveal the PID</description>
      <pubDate>Thu, 29 Sep 2005 02:53:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930065#M46181</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2005-09-29T02:53:29Z</dc:date>
    </item>
    <item>
      <title>Re: telnet</title>
      <link>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930066#M46182</link>
      <description>&lt;BR /&gt;This problem likely happens if you have started a daemon from the telnet session which does not release the current tty and continues to use it as its default tty.&lt;BR /&gt;&lt;BR /&gt;If you are running some daemon then try to run it in the background with all tty operations redirected to /dev/null (or some where else).&lt;BR /&gt;&lt;BR /&gt;It should solve your problem. But i am not sure why it can not allow any more new telnet sessions.&lt;BR /&gt;&lt;BR /&gt;Hope this helps,&lt;BR /&gt;Gopi</description>
      <pubDate>Thu, 29 Sep 2005 03:00:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930066#M46182</guid>
      <dc:creator>Gopi Sekar</dc:creator>
      <dc:date>2005-09-29T03:00:26Z</dc:date>
    </item>
    <item>
      <title>Re: telnet</title>
      <link>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930067#M46183</link>
      <description>thx</description>
      <pubDate>Thu, 29 Sep 2005 05:33:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/telnet/m-p/4930067#M46183</guid>
      <dc:creator>Chakravarthi</dc:creator>
      <dc:date>2005-09-29T05:33:46Z</dc:date>
    </item>
  </channel>
</rss>

