03-18-2002
You can use "netstat -a" to see current inbound/outbound connections. You can close ports by stopping the associated services. If you really want to "close" them fully you will need to setup a firewall.
Last edited by PxT; 03-18-2002 at 05:01 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I'm new to the forum and would like to know how to check
inbound traffic on various port numbers.
I would also like to know how to open and close various ports
on a unix box running solaris 8.
Thanks in advance.
sunoracle (1 Reply)
Discussion started by: sunoracle
1 Replies
2. Shell Programming and Scripting
Hi All
Has anyone written any script that would listen for inbound mail and based on its subject process the body ?
Thx
J (3 Replies)
Discussion started by: jhansrod
3 Replies
3. Shell Programming and Scripting
Hello, i need a script (bash type maybe?..), which would check open ports on 127.0.0.1 and then compare open ports with "registered/allowed" port list and try to kill the program who uses unregistered ports. It would be great that script would be started lets say every 5 or 10 minutes.
You see i... (2 Replies)
Discussion started by: MorchiuS
2 Replies
4. Shell Programming and Scripting
Good day,
I'm new to linux environment...Is there any scripts available for me to check ports (lets say port 80 and 21) through shell with just a single commandline?
Any response is very much appreciated..
thanks (4 Replies)
Discussion started by: arsonist
4 Replies
5. Cybersecurity
Hi All,
I've been using this to verify if ports is open on a server. For example I would like to check port 5887, "telnet ip.of.server 5887" using on dos. If there's response on it then I can say it's open, if not then it's close.
Is that assumption accurate?
Thanks for any comments you... (4 Replies)
Discussion started by: itik
4 Replies
6. Solaris
Hello All,
I am trying find a command that would show me the stats of outgoing traffic on UPD ports on a Solaris 10 box. I would appreciate if anybody could help me out on this.
Thank you much!!!
Best Regards
Sudharma. (7 Replies)
Discussion started by: sudharma
7 Replies
7. Shell Programming and Scripting
Hi
I'd like to check that a bunch of firewall rules have been applied and, therefore, want to write a script that basically does the following:
telnet serverA port1
telnet serverA port2
telnet serverB port1
telnet serverB port2
I would just compile the list in excel and run it as a... (2 Replies)
Discussion started by: jibberish
2 Replies
8. AIX
Hi,
I am trying to implement a service on AIX based on ONCRPC protocal and I want to use a RPC library called oncrpc4j because it is a non-blocked i/o library. I found it works fine on my work machine (WIndows 7) but failed on my AIX work station. The author of oncrpc4j told me that check that... (1 Reply)
Discussion started by: derekhsu
1 Replies
9. Shell Programming and Scripting
Hi. I need to add code to my KSH script to automatically assign an open port number from a pre-defined range to an Oracle listener.
Should I use:
lsof -i
or
netstat -vatn
or something else?
Thanks. (9 Replies)
Discussion started by: user052009
9 Replies
LEARN ABOUT HPUX
stopping
stopping(7) Miscellaneous Information Manual stopping(7)
NAME
stopping - event signalling that a job is stopping
SYNOPSIS
stopping JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopping event is generated by the Upstart init(8) daemon when an instance of a job begins stopping. The JOB environment variable con-
tains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job is stopping normally, the RESULT environment variable will be ok, otherwise if the job is stopping because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job is stopping because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) will wait for all services started by this event to be running, all tasks started by this event to have finished and all jobs
stopped by this event to be stopped before allowing the job to continue stopping.
This allows jobs to depend on other jobs, safely stopping themselves before their dependency goes away. This event is typically combined
with the started(7) event by services.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopping event. See
init(5) for more details.
EXAMPLE
A service that wishes to depend on another service might use:
start on started apache
stop on stopping apache
A task that must be run before another task or service is stopped might use:
start on stopping postgresql RESULT=ok
SEE ALSO
starting(7) started(7) stopped(7) init(5)
Upstart 2009-07-09 stopping(7)