Sponsored Content
Operating Systems Linux Red Hat No process ID for listening ports Post 302361901 by Padow on Wednesday 14th of October 2009 09:57:43 AM
Old 10-14-2009
These ports were actually part of NFS.

I added this to /etc/modprobe.conf to control the ports used so i can exclude them from scans:

options lockd nlm_tcpport=<PORT> nlm_udpport=<PORT>
Padow
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

TCP Listening Ports

Hello all, Can someone instruct me on how to change the listening port for ftp ( or any tcp service) from 21 to another port number? Thanks in advance.. -AJ (3 Replies)
Discussion started by: jacobsa
3 Replies

2. UNIX for Dummies Questions & Answers

unix process that frees ports

Hello, I know that there is a unix system process that checks periodically the ports and if it finds any zombies then it frees them (the period is set by a kernel parameter). Can anyone tell me the name of the process and the kernel parameter ? Thanks :) (2 Replies)
Discussion started by: FunnyCats
2 Replies

3. UNIX for Dummies Questions & Answers

What prot is a process listening on?

Hi, Bit of a newbie question . . . How can I detrimine what TCP port a particular process is listening on? TIA. (2 Replies)
Discussion started by: Le Badger
2 Replies

4. Solaris

List TCP ports with process

Hello, One of our developers is asking for a command/script in Solaris similar to "netstat -anp" in Linux. He gave this output as an example: root@xxx:~# netstat -anp | grep LISTEN tcp 0 0 0.0.0.0:7937 0.0.0.0:* LISTEN 16082/nsrexecd tcp 0 ... (7 Replies)
Discussion started by: vimes
7 Replies

5. Shell Programming and Scripting

Finding the process id of the process using the ports

Hi Any idea how to get the process id of the process using the ports lsof -i :portnumber does not work in my machine. I am on sun Solaris SPARC. Any suggestion is highly appreciated (1 Reply)
Discussion started by: kinny
1 Replies

6. UNIX for Dummies Questions & Answers

Processes listening on Ports(Solaris)

Howdy Experts, This is my first post here and I am posting because I have not been able to find an answer for this question. How do you find out what process is listening on a given port? I do not have "lsof" available and how do we find this out without logging in as Root. I know that this... (5 Replies)
Discussion started by: KingaKoopa
5 Replies

7. UNIX for Dummies Questions & Answers

How do i list running process with the ports they are using?

How do i list the running process and also view the ports they are listening to at the same time? (3 Replies)
Discussion started by: mena
3 Replies

8. AIX

Process running but not listening

Hello guys I am experiencing a very strange behavior on one of our AIX servers. We have an application with several processes that listen on several port numbers. Sometimes we receive complains that people cannot connect to the server on a specific port that is used by one the application... (6 Replies)
Discussion started by: abohmeed
6 Replies

9. UNIX for Advanced & Expert Users

Finding process that turned on ports

I have 2 identical solaris 10 servers that are simply apache servers, running a version of apache I installed. # uname -a SunOS wilber 5.10 Generic_147440-25 sun4u sparc SUNW,Sun-Fire-V245 I did a netstat on one of the servers and see 2 ports that are on. These are only on on one of the... (2 Replies)
Discussion started by: csross
2 Replies

10. Ubuntu

PID of listening ports

I ran 'sudo netstat -ntpl' and got the following without PID tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:38977 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:34253 ... (3 Replies)
Discussion started by: tt77
3 Replies
RPC.LOCKD(8)						    BSD System Manager's Manual 					      RPC.LOCKD(8)

NAME
rpc.lockd -- NFS file locking daemon SYNOPSIS
rpc.lockd [-d debug_level] [-g grace period] [-h bindip] [-p port] DESCRIPTION
The rpc.lockd utility provides monitored and unmonitored file and record locking services in an NFS environment. To monitor the status of hosts requesting locks, the locking daemon typically operates in conjunction with rpc.statd(8). Options and operands available for rpc.lockd: -d The -d option causes debugging information to be written to syslog, recording all RPC transactions to the daemon. These messages are logged with level LOG_DEBUG and facility LOG_DAEMON. Specifying a debug_level of 1 results in the generation of one log line per protocol operation. Higher debug levels can be specified, causing display of operation arguments and internal operations of the dae- mon. -g The -g option allow to specify the grace period, in seconds. During the grace period rpc.lockd only accepts requests from hosts which are reinitialising locks which existed before the server restart. Default is 30 seconds. -h bindip Specify specific IP addresses to bind to. This option may be specified multiple times. If no -h option is specified, rpc.lockd will bind to INADDR_ANY. Note that when specifying IP addresses with -h, rpc.lockd will automatically add 127.0.0.1 and if IPv6 is enabled, ::1 to the list. -p The -p option allow to force the daemon to bind to the specified port, for both AF_INET and AF_INET6 address families. Error conditions are logged to syslog, irrespective of the debug level, using log level LOG_ERR and facility LOG_DAEMON. The rpc.lockd utility must NOT be invoked by inetd(8) because the protocol assumes that the daemon will run from system start time. Instead, it should be configured in rc.conf(5) to run at system startup. FILES
/usr/include/rpcsvc/nlm_prot.x RPC protocol specification for the network lock manager protocol. SEE ALSO
syslog(3), rc.conf(5), rpc.statd(8) STANDARDS
The implementation is based on the specification in "Protocols for X/Open PC Interworking: XNFS, Issue 4", X/Open CAE Specification C218, ISBN 1 872630 66 9. HISTORY
A version of rpc.lockd appeared in SunOS 4. BUGS
The current implementation serialises locks requests that could be shared. BSD
November 2, 2007 BSD
All times are GMT -4. The time now is 09:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy