03-01-2013
i tried but it didnt work it seems that the netsat tell me that such pid exist but in real there is not such a process.
here is the scenario
i connected to this server as a client and run a backup application on client.
the server use the port 5914 for this application.
withnetsat i can see that this port is in listening state and even the connection between server and client is in establishment state but there is not really anything about that pid in ps or lsof
is it really possible?
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
DHISD(8) BSD System Manager's Manual DHISD(8)
NAME
dhisd -- Dynamic Host Information System server.
SYNOPSIS
dhisd [-D] [-p port] [-d database] [-s services] [-l logfile] [-P pidfile]
DESCRIPTION
DHIS is a client-server architecture meant to update databases for systems which are assigned a dynamic IP[v4] address.
By the means of a DHIS client a host which is assigned a dynamic IP address (either from its ISP or from DHCP) is able to communicate with a
DHIS server in order to advertise its newly acquired IP address.
DHIS comprises a UDP based protocol to achieve this purpose.
A DHIS client has a unique identification number and a set of authentication keys, runs in background, and attempts to reach its server.
The DHIS server (permanently online) listens to UDP messages from its clients and authenticates these against its knowledge of keys. When
authentication is successful the DHIS server updates one or more databases with the newly received IP address for the given client.
The server then keeps sending, every period of time, check requests to each of its connected clients. These need to be acknowledged. If not
the server will consider, on an individual basis, that the client has disconnected and will again update the databases to an offline state.
Alternativelly the server may receive an OFFLINE_REQ packet from the client, in which case the DNS record is updated at once and the online
state droped.
OPTIONS
-D Increase debug level.
-p port
Specify port to listen on. If not specified, the default is port 58800.
-d database
Use an alternative database file instead of /etc/dhis-server/dhis.db.
-s services
Use an alternative database file instead of /etc/dhis-server/services.db.
-l logfile
Use an alternative log file instead of /var/log/dhisd.log.
-P pidfile
Use an alternative PID file instead of /var/run/dhisd.pid.
FILES
/etc/dhis-server/dhis.db
DHIS client database. Contains the credentials of clients.
/etc/dhis-server/services.db
DHIS service database. Contains a list of services and the location of the corresponding DHIS engine plugins.
SEE ALSO
dhis-genkeys(8)
AUTHOR
dhisd has been written by Joao Cabral <jcnc@dhis.org>.
This manual page was written by Guus Sliepen <guus@debian.org> for the Debian GNU/Linux system.
Debian GNU/Linux June 1, 2019 Debian GNU/Linux