1847205 Members
2941 Online
110263 Solutions
New Discussion

about telnet closed?

 
huanghongjie
Occasional Contributor

about telnet closed?

I had a new server, os is HP-UX11i. Today i find a question. I telnet to the HP server from another host (sco unix),and executed a monitor's shell.After 30 minute, i found that the shell was closed with message "Connection closed by foreign host" . I had checked kernel configure parameter,but not found any about telnet timeout. How can i resolve the question,because the monitor's shell must be run in 24 hours.
thanks
6 REPLIES 6
RAC_1
Honored Contributor

Re: about telnet closed?

Once you login , do TMOUT=0.

Also does it give anything in syslog when you get logged out? Are you coming to hp box through firewall? And has anything defined on firewall to log you out after particular period?

Anil
There is no substitute to HARDWORK
sinhass
Regular Advisor

Re: about telnet closed?

check /etc/profile or .profile and find put the TMOUT value and change it to 0

-sinhass
huanghongjie
Occasional Contributor

Re: about telnet closed?

NO,the two machines is in same lan,and at the back of firewall . The monitor shell is not quit, so it must be connected to the HP SERVER. I had found another thing that the shell process is runing in server with "ps -ef|grep ???" , and if had many the dead process, the value of CPU sys is higher than normal with command "sar -u ". It can reach 30%-40%. But i kill the dead process ,the value is down.
ashish_24
Occasional Advisor

Re: about telnet closed?

hello
check the file /var/adm/inetd.sec file..it contains an entry telnet allow make an entry there of the server u want to be able to access..that's it

bye
KapilRaj
Honored Contributor

Re: about telnet closed?

Surely it is a firewall timeout for an idle session . I face the same issue with one or two DMZ nodes here.

Catch hold of the firewall expert !

Kaps
Nothing is impossible
Borislav Perkov
Respected Contributor

Re: about telnet closed?

Hi,
The best way is to execute shell script in background or with nohup, or at, or crontab. Then you can be sure that nothing will disconnect the session while the script is running.
Regards,
Boris