Sponsored Content
Full Discussion: fail to telnet localhost 106
Operating Systems Linux Ubuntu fail to telnet localhost 106 Post 302151648 by porter on Sunday 16th of December 2007 08:39:26 PM
Old 12-16-2007
Quote:
Originally Posted by satimis
$ sudo netstat -an | grep LISTEN
Code:
Password:
tcp        0      0 0.0.0.0:106             0.0.0.0:*               LISTEN

Yup, something's there. All you need to find out is what it is.

Is there anything in the syslog?

Can you confirm you can execute the command line indicated in /etc/inetd.conf for port 106 from the command prompt?
 

3 More Discussions You Might Find Interesting

1. Linux

Telnet fail

Hi, I try to telnet to server: # telnet xx.xxx.1.72 1521 Trying xx.xxx.1.72... telnet: connect to address xx.xxx.1.72: Connection refused telnet: Unable to connect to remote host: Connection refused iptables is off: # service iptables status Firewall is stopped. # And I have edit... (4 Replies)
Discussion started by: mehrdad68
4 Replies

2. Shell Programming and Scripting

If Telnet fail abort other command..??

Hi Team, I my script i telent my node ip and after loging i run some commands...But some time login fail so i want to stop script at that time.. CONFIG_CHNG.sh printf 'Please Input Node ID : ' read node node="$node" #exec > node_log_$node.log 2>&1 #set -x >... (2 Replies)
Discussion started by: Ganesh Mankar
2 Replies

3. UNIX for Beginners Questions & Answers

Telnet failed to localhost.

Hi, I am trying telnet to localhost 514. But the connection is refusing. Port does not appear in netstat. IP table service is also off. (5 Replies)
Discussion started by: Nishit
5 Replies
LISTEN(7)							   SQL Commands 							 LISTEN(7)

NAME
LISTEN - listen for a notification SYNOPSIS
LISTEN name INPUTS name Name of notify condition. OUTPUTS LISTEN Message returned upon successful completion of registration. WARNING: Async_Listen: We are already listening on name If this backend is already registered for that notify condition. DESCRIPTION
LISTEN registers the current PostgreSQL backend as a listener on the notify condition name. Whenever the command NOTIFY name is invoked, either by this backend or another one connected to the same database, all the backends cur- rently listening on that notify condition are notified, and each will in turn notify its connected frontend application. See the discussion of NOTIFY for more information. A backend can be unregistered for a given notify condition with the UNLISTEN command. Also, a backend's listen registrations are automati- cally cleared when the backend process exits. The method a frontend application must use to detect notify events depends on which PostgreSQL application programming interface it uses. With the libpq library, the application issues LISTEN as an ordinary SQL command, and then must periodically call the routine PQnotifies to find out whether any notify events have been received. Other interfaces such as libpgtcl provide higher-level methods for handling notify events; indeed, with libpgtcl the application programmer should not even issue LISTEN or UNLISTEN directly. See the documentation for the library you are using for more details. NOTIFY [notify(7)] contains a more extensive discussion of the use of LISTEN and NOTIFY. NOTES name can be any string valid as a name; it need not correspond to the name of any actual table. If notifyname is enclosed in double-quotes, it need not even be a syntactically valid name, but can be any string up to 63 characters long. In some previous releases of PostgreSQL, name had to be enclosed in double-quotes when it did not correspond to any existing table name, even if syntactically valid as a name. That is no longer required. USAGE
Configure and execute a listen/notify sequence from psql: LISTEN virtual; NOTIFY virtual; Asynchronous NOTIFY 'virtual' from backend with pid '8448' received. COMPATIBILITY
SQL92 There is no LISTEN in SQL92. SQL - Language Statements 2002-11-22 LISTEN(7)
All times are GMT -4. The time now is 12:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy