03-01-2013
Releasing a port
one of my system ports are busy and i dont know how to kill it
in netstat -a i see that the port are being used with a given ip but in ps -e i can not find that port being used by a process.
how can i kill that process or release that port.
10 More Discussions You Might Find Interesting
1. IP Networking
I am trying to connect via DBACCESS and Informix server to a server on a different computer. When I execute the connect command from dbaccess I get the following message,
Exec format error cannot bind a name to the port.
As far as I know the port is not being used by another client.
How... (1 Reply)
Discussion started by: lopez
1 Replies
2. UNIX for Dummies Questions & Answers
Hi All, I suspect this is simple but I cannot find any info on it.
I have a logfile on a solaris box (EMS) that I want to tail -f but I want the output of this to be redirected to a TCP port.
I have a second solaris box (PEM) running patrol enterprise manager that I am using as an alarm... (1 Reply)
Discussion started by: mscomms
1 Replies
3. UNIX for Dummies Questions & Answers
Hi
Is there any way to restrict the TCP-IP port usage.
I want to restrict TCP-IP port 1500/1550 to the oracle osuser.
Tanks in advance.
Remi (2 Replies)
Discussion started by: remivisser
2 Replies
4. Solaris
Hi all
I haven't had much experience with Solaris 10 but we've started running into a problem where a process hangs, it is killed and leaves a zombie process. The sysadmins are saying this zombie process is locking a tcp port and not allowing the process to start up.
The process is a usually... (5 Replies)
Discussion started by: casphar
5 Replies
5. UNIX for Dummies Questions & Answers
Hello, I have a service running (ODBC) and every now and then it will hang and I will have to stop and restart the service. The problem is when I stop the service, it indeed stops the service, but netstat reports a tcp port still open with the fin_wait_2 status. Then I must close the client... (1 Reply)
Discussion started by: raidzero
1 Replies
6. IP Networking
Hi. I ran nmap on my server, and I get the following:
Starting Nmap 4.76 ( http://nmap.org ) at 2009-03-19 16:33 EDT
Interesting ports on -------- (-----):
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
6881/tcp open bittorrent-tracker
The... (0 Replies)
Discussion started by: Rledley
0 Replies
7. Shell Programming and Scripting
I have multiple processes running the same program on my linux machine. For each process I want to be able to use a unique (available) TCP port. I have thought of using netstat to check which ports are available for use however, the time-window between checking and selecting might expose some race... (1 Reply)
Discussion started by: timmylita
1 Replies
8. UNIX for Advanced & Expert Users
Hey guys,
I need to kill the process that is currently connected to port 10540. I'm on HP-UX machine.
Below is the result of my netstat.
$ netstat -an |grep 10540
tcp 0 0 129.0.0.1.10540 *.* LISTEN
We don't have lsof command, but we have fuser.
... (3 Replies)
Discussion started by: brichigo
3 Replies
9. Programming
Hello,
I'm trying to write a small c application to test a tcp port. This works fine for the most part but the default timeout on the connect is very long. I have been reading many posts but and it looks like I need to set the socket to be non-blocking and poll for a result. I have been totally... (2 Replies)
Discussion started by: tjones1105
2 Replies
10. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill, broke - print commands to kill processes
SYNOPSIS
kill name
broke
DESCRIPTION
Kill prints commands that will cause all processes called name and owned by the current user to be terminated. Use the send command of
81/2(1), or pipe the output of kill into rc(1) to execute the commands.
Kill suggests sending a kill note to the process; the same message delivered to the process's ctl file (see proc(3)) is a surer, if heavy
handed, kill, but is necessary if the offending process is ignoring notes.
Broke prints commands that will cause all processes in the Broken state and owned by the current user to go away. When a process dies
because of an error caught by the system, it may linger in the Broken state to allow examination with a debugger. Executing the commands
printed by broke lets the system reclaim the resources used by the broken processes.
SOURCE
/rc/bin/kill
/rc/bin/broke
SEE ALSO
ps(1), stop(1), proc(3)
KILL(1)