12-13-2010
9 More Discussions You Might Find Interesting
1. Cybersecurity
/* Linux Slackware */
Nmap shows the following ports open on the gateway.
21/tcp ftp
22/tcp ssh
23/tcp telnet
25/tcp smtp
37/tcp time
80/tcp http
113/tcp auth
515/tcp printer
587/tcp submission
1024/tcp kdm
6000/tcp x11
-------------------------------
i would like to close as... (10 Replies)
Discussion started by: LowOrderBit
10 Replies
2. UNIX for Dummies Questions & Answers
When I scan my linux box for open ports, i have several of them, but they shouldn't be open. I removed the lines for them in /etc/services, and left just stuff like telnet, ssh, ftp. Why are they still open? I've restarted the network, and I've even restarted my box, but they still apear as open.... (4 Replies)
Discussion started by: sTorm
4 Replies
3. UNIX for Dummies Questions & Answers
hello all,
in order for me to close ports and remove services that could be a danger to my system i have edited the /etc/initd.conf file, /etc/system file, and renamed some of the r commands. However i wanted to know if anyone knows how to turn off all services and close ALL known ports, so i... (3 Replies)
Discussion started by: Holistic
3 Replies
4. Linux
how can i open ports i need in red hat server vs root access ? (7 Replies)
Discussion started by: Sirius
7 Replies
5. AIX
Hi Every body,
What is the command on AIX 5.2 that can be used to get all open ports? (2 Replies)
Discussion started by: aldowsary
2 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I have a number of Solaris 8 Sun servers that have open ports that I cannot identify. I see some with 1012-1020 (which are reserved ports according to the IANA. Lsof does not identify these. One server has all these on and one server just has 1017.
*.1023 ... (3 Replies)
Discussion started by: csross
3 Replies
7. Solaris
Hello,
I have a number of Solaris 8 Sun servers that have open ports that I cannot identify. I see some with 1013-1023 (which are reserved ports according to the IANA. Lsof does not identify these. I rebooted the server and they went off, but this morning I saw they were all back on again. Any... (1 Reply)
Discussion started by: csgonan
1 Replies
8. Solaris
hi guys,
may i know the exact steps to open a port in solaris.i have some rough idea - which is adding the port number in /etc/services.
but i am not sure the correct conventions, steps or any other steps.
kindly advise.thanks guys ! (1 Reply)
Discussion started by: cromohawk
1 Replies
9. Linux
Hi Team,
I am using RHEL 7.3.
I had added few port numbers in
/proc/sys/net/ipv4/ip_local_reserved_ports.
Now how do I verify that kernel does not allow to a service which requests random ports for its services.
Thanks in Advance
Hariharan Gopal (0 Replies)
Discussion started by: hariharan.gopal
0 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)