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
LEARN ABOUT SUSE
nbd-client
NBD-CLIENT(8) NBD-CLIENT(8)
NAME
nbd-client - connect to a server running nbd-server(1), to use its exported block device
SYNOPSIS
nbd-client [ bs=blocksize ] [ timeout=seconds ] host port nbd-device [ -sdp ] [ -swap ] [ -persist ] [ -nofork ]
nbd-client -d nbd-device
nbd-client -c nbd-device
DESCRIPTION
With nbd-client, you can connect to a server running nbd-server, thus using raw diskspace from that server as a blockdevice on the local
client.
To do this, support from the Linux Kernel is necessary, in the form of the Network Block Device (NBD). When you have that, either in the
kernel, or as a module, you can connect to an NBD server and use its exported file through a block special file with major mode 43.
OPTIONS
The following options are supported:
bs=blocksize
Use a blocksize of "blocksize". Default is 1024; allowed values are either 512, 1024, 2048 or 4096
host The hostname of the machine running nbd-server.
timeout=seconds
Set the connection timeout to "seconds". For this to work, you need a kernel with support for the NBD_SET_TIMEOUT ioctl; this was
introduced into Linus' tree on 2007-10-11, and will be part of kernel 2.6.24.
port The TCP port on which nbd-server is running at the server.
nbd-device
The block special file this nbd-client should connect to.
-c Check whether the specified nbd device is connected.
If the device is connected, nbd-client will exit with an exit state of 0 and print the PID of the nbd-client instance that connected
it to stdout.
If the device is not connected or does not exist (for example because the nbd module was not loaded), nbd-client will exit with an
exit state of 1 and not print anything on stdout.
If an error occurred, nbd-client will exit with an exit state of 2, and not print anything on stdout either.
-d Disconnect the specified nbd device from the server
-persist
When this option is specified, nbd-client will immediately try to reconnect an nbd device if the connection ever drops unexpectedly
due to a lost server or something similar.
-sdp Connect to the server using the Socket Direct Protocol (SDP), rather than IP. See nbd-server(1) for details.
-swap Specifies that this NBD device will be used as swapspace. This option attempts to prevent deadlocks by performing mlockall() at an
appropriate time. It does not however guarantee that such deadlocks can be avoided.
-nofork
Specifies that the NBD client should not detach and daemonize itself. This is mostly useful for debugging.
EXAMPLES
Some examples of nbd-client usage:
o To connect to a server running on port 2000 at host "server.domain.com", using the client's block special file "/dev/nb0":
nbd-client server.domain.com 2000 /dev/nb0
o To connect to a server running on port 2001 at host "swapserver.domain.com", using the client's block special file "/dev/nb1", for swap
purposes:
nbd-client swapserver.domain.com 2001 /dev/nb1 -swap
o To disconnect the above connection again (after making sure the block special file is not in use anymore):
nbd-client -d /dev/nb1
SEE ALSO
nbd-server (1).
AUTHOR
The NBD kernel module and the NBD tools have been written by Pavel Macheck (pavel@ucw.cz).
The kernel module is now maintained by Paul Clements (Paul.Clements@steeleye.com), while the userland tools are maintained by Wouter Ver-
helst (wouter@debian.org)
This manual page was written by Wouter Verhelst (<wouter@debian.org>) for the Debian GNU/Linux system (but may be used by others). Permis-
sion is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, version 2, as published
by the Free Software Foundation.
26 May 2009 NBD-CLIENT(8)