Sponsored Content
Full Discussion: connection to host lost
Top Forums UNIX for Dummies Questions & Answers connection to host lost Post 2172 by Neo on Wednesday 25th of April 2001 11:45:15 AM
Old 04-25-2001
TCP/IP connections use keep-alive signals to keep the connection open. Some client implementations of TCP/IP do not generate these signals properly and the connection die. There are other reasons that connections die too. Anytime the keep-alive signals are not (1) generated or (2) received, idle connection will time-out.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Not on System Console; Connection to host lost.

hi all, When I telnet my W2k machine to my Solaris8 machine, after typing my login name and password prompt, I get the following msg immediately. ==== Not on System Console. Connection to host lost. ==== The 2 machines are connected on the same kingston workgroup hub. Can someone pls help? (3 Replies)
Discussion started by: andrec
3 Replies

2. UNIX for Dummies Questions & Answers

Connection Lost from Unix Server....

This morning I was working by Xwindow to my unix server (hp-ux, 11 version), without any problem but this afteernoon, the connections was refused, and triying to connect using telnet, sometimes I can establish the connection and refuses me in a minute, the error message that appears is "your... (1 Reply)
Discussion started by: fvicente
1 Replies

3. UNIX for Dummies Questions & Answers

Connection to host lost

I keep receiving this message when trying to connect using telnet to SunOS 5.8 running Solaris 8 from W2k. I checked system and inetd.conf and they seem to be ok. I can ping the host ok. ftp also works fine. Any suggestion would be greatly appreciated. (2 Replies)
Discussion started by: goose
2 Replies

4. Debian

Killing host connection

Hi All Is there a command (or set of commands) that can be used to kill a connection listed in the netstat table? Say there is a host connected to a certain port on your machine, and it is listed via a 'netstat -an', is there a way to issue some commands to 'disconnect' or kill that connection? ... (5 Replies)
Discussion started by: saabir
5 Replies

5. IP Networking

FTP - Connection Closed By Remote Host

Hi, I am having a problem with our AIX 4.3.3 Server accessing FTP. The error is " Connection Closed By Remote Host". Scenario: Since i put a default gateway on the server FTP connection is having a problem but when i remove the default gateway it will works fine.. Is there any way not... (1 Reply)
Discussion started by: mouglybean
1 Replies

6. HP-UX

SCP transfer failed, lost connection

Hello, We try to do an SCP of a Sybase dump file of 4Go between two production HP-UX servers. Each time the transfer stopn at 299Mo and we have the message "connection lost". The destination FS has largefiles option activated. Could you help ? (7 Replies)
Discussion started by: ohemeg
7 Replies

7. UNIX for Dummies Questions & Answers

ssh_exchange_identification: Connection closed by remote host Connection closed

Hi Everyone, Good day. Scenario: 2 unix servers -- A (SunOS) and B (AIX) I have an ftp script to sftp 30 files from A to B which happen almost instantaneously i.e 30 sftp's happen at the same time. Some of these sftp's fail with the following error: ssh_exchange_identification: Connection... (1 Reply)
Discussion started by: jeevan_fimare
1 Replies

8. Solaris

ILOM - lost connection

Hello, In my server Sun Enterprise T5140 I have unusual problem with ILOM. After several, several days, I can not connect to the ILOM. For connection to the ILOM I turn off the server power and then turn it on. Where is the problem? Regards (10 Replies)
Discussion started by: bieszczaders
10 Replies

9. HP-UX

Connection closed by foreign host

I am trying to connect to my HP server from remote machine. It gets connected but once credential are provided the connection is closed. adroit:/home/seo/hitendra 32 ] telnet myserv1 Trying... Connected to myserv1. Escape character is '^]'. Local flow control on Telnet TERMINAL-SPEED... (4 Replies)
Discussion started by: hiten.r.chauhan
4 Replies

10. Ubuntu

[TCPDUMP] Connection lost

I'm on Ubuntu – but it's the same on Debian. I'm using tcpdump in order to track the connection of computers on my private network. At some point, the internet connection of the computers launching the script is lost as well as the targeted computers. Here's the command line: tcpdump -i wlan0... (0 Replies)
Discussion started by: Skirmjan
0 Replies
sigtrap(3pm)						 Perl Programmers Reference Guide					      sigtrap(3pm)

NAME
sigtrap - Perl pragma to enable simple signal handling SYNOPSIS
use sigtrap; use sigtrap qw(stack-trace old-interface-signals); # equivalent use sigtrap qw(BUS SEGV PIPE ABRT); use sigtrap qw(die INT QUIT); use sigtrap qw(die normal-signals); use sigtrap qw(die untrapped normal-signals); use sigtrap qw(die untrapped normal-signals stack-trace any error-signals); use sigtrap 'handler' => &my_handler, 'normal-signals'; use sigtrap qw(handler my_handler normal-signals stack-trace error-signals); DESCRIPTION
The sigtrap pragma is a simple interface to installing signal handlers. You can have it install one of two handlers supplied by sigtrap itself (one which provides a Perl stack trace and one which simply "die()"s), or alternately you can supply your own handler for it to install. It can be told only to install a handler for signals which are either untrapped or ignored. It has a couple of lists of signals to trap, plus you can supply your own list of signals. The arguments passed to the "use" statement which invokes sigtrap are processed in order. When a signal name or the name of one of sigtrap's signal lists is encountered a handler is immediately installed, when an option is encountered it affects subsequently installed handlers. OPTIONS
SIGNAL HANDLERS These options affect which handler will be used for subsequently installed signals. stack-trace The handler used for subsequently installed signals outputs a Perl stack trace to STDERR and then tries to dump core. This is the default signal handler. die The handler used for subsequently installed signals calls "die" (actually "croak") with a message indicating which signal was caught. handler your-handler your-handler will be used as the handler for subsequently installed signals. your-handler can be any value which is valid as an assignment to an element of %SIG. See perlvar for examples of handler functions. SIGNAL LISTS sigtrap has a few built-in lists of signals to trap. They are: normal-signals These are the signals which a program might normally expect to encounter and which by default cause it to terminate. They are HUP, INT, PIPE and TERM. error-signals These signals usually indicate a serious problem with the Perl interpreter or with your script. They are ABRT, BUS, EMT, FPE, ILL, QUIT, SEGV, SYS and TRAP. old-interface-signals These are the signals which were trapped by default by the old sigtrap interface, they are ABRT, BUS, EMT, FPE, ILL, PIPE, QUIT, SEGV, SYS, TERM, and TRAP. If no signals or signals lists are passed to sigtrap, this list is used. For each of these three lists, the collection of signals set to be trapped is checked before trapping; if your architecture does not implement a particular signal, it will not be trapped but rather silently ignored. OTHER untrapped This token tells sigtrap to install handlers only for subsequently listed signals which aren't already trapped or ignored. any This token tells sigtrap to install handlers for all subsequently listed signals. This is the default behavior. signal Any argument which looks like a signal name (that is, "/^[A-Z][A-Z0-9]*$/") indicates that sigtrap should install a handler for that name. number Require that at least version number of sigtrap is being used. EXAMPLES
Provide a stack trace for the old-interface-signals: use sigtrap; Ditto: use sigtrap qw(stack-trace old-interface-signals); Provide a stack trace on the 4 listed signals only: use sigtrap qw(BUS SEGV PIPE ABRT); Die on INT or QUIT: use sigtrap qw(die INT QUIT); Die on HUP, INT, PIPE or TERM: use sigtrap qw(die normal-signals); Die on HUP, INT, PIPE or TERM, except don't change the behavior for signals which are already trapped or ignored: use sigtrap qw(die untrapped normal-signals); Die on receipt one of an of the normal-signals which is currently untrapped, provide a stack trace on receipt of any of the error-signals: use sigtrap qw(die untrapped normal-signals stack-trace any error-signals); Install my_handler() as the handler for the normal-signals: use sigtrap 'handler', &my_handler, 'normal-signals'; Install my_handler() as the handler for the normal-signals, provide a Perl stack trace on receipt of one of the error-signals: use sigtrap qw(handler my_handler normal-signals stack-trace error-signals); perl v5.12.1 2010-04-26 sigtrap(3pm)
All times are GMT -4. The time now is 12:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy