09-14-2009
That's upercase "LISTEN" or "grep -i listen".
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
how do u check if a daemon is running in AIX..
Is it ps -ef|grep daemon
lssrc -s demon ???
Thanks! (0 Replies)
Discussion started by: karthikosu
0 Replies
2. UNIX for Advanced & Expert Users
disregard solved (0 Replies)
Discussion started by: calamine
0 Replies
3. AIX
How can i check which service is activated on my AIX Box?
how one can check particular port is open or not (like ftp/telnet port)?
I dont have admin rights (1 Reply)
Discussion started by: ashish4422
1 Replies
4. Shell Programming and Scripting
I write a script which will stop an application, then restart it.
Sometimes it is succesful, sometimes not.
The problem is, when stop the application, some ports are still listenning (or not released). When start the application, it reports that ports are used, and can't continues.
I use... (1 Reply)
Discussion started by: rdcwayx
1 Replies
5. Solaris
Hi there
I am in the process of writing a script to check whether a port on a remote system is up or not.
Here's what I have so far:
#!/bin/bash
telnet xx.xx.xx.xx 80 | (echo "^]")
if ]; then
echo "Please check Web services " | mailx -s "Please check webservices... (1 Reply)
Discussion started by: notreallyhere
1 Replies
6. Shell Programming and Scripting
Hi
I was going through one of my pjct script .Please let me know the logic for the deamon is running or not as i think the condtn should be vice-versa.
daemon_list = 'idp1278'
FAIL=0
for p in ${daemon_list}
do
fail=0
ps -fu workarea | grep ${p} > /dev/null 2>&1
if ] then
... (1 Reply)
Discussion started by: mani_isha
1 Replies
7. Programming
Does anyone know if there is a C API call to get the status of a TCP port? As opposed to running netstat and parsing the results. At the moment I have to attempt to bind() and pick up on the address in use error which isn't very elegant
Thanks
---------- Post updated at 10:42 AM ----------... (0 Replies)
Discussion started by: janra
0 Replies
8. UNIX for Dummies Questions & Answers
Hi,
When process listing, I came across a process running as user daemon.
daemon 23576 23574 0 07:32:04 ? 0:07 oracle (DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))
root 27526 27444 1 07:38:43 ttyp5 0:00 grep 23574
why a process runs as user daemon, when it should be... (3 Replies)
Discussion started by: wilsonee
3 Replies
9. AIX
Hi
I am currently testing SCOM2012 on my AIX systems for monitoring. I tested it on 3 systems and immediately i got the following errors:
Alert: Network Status Monitor daemon (rpcstat) is not running
Source: AIX 7.1
Path: (left blank)
Last modified by: (left blank)
Last modified time:... (3 Replies)
Discussion started by: jsabo40
3 Replies
LEARN ABOUT REDHAT
listen
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)