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
lockd(1M)						  System Administration Commands						 lockd(1M)

NAME
lockd - network lock daemon SYNOPSIS
/usr/lib/nfs/lockd [-g graceperiod] [-l listen_min_backlog] [-t timeout] [nthreads] DESCRIPTION
The lockd utility is part of the NFS lock manager, which supports record locking operations on NFS files. See fcntl(2) and lockf(3C). The lock manager provides the following two functions: o It forwards fcntl(2) locking requests for NFS mounted file systems to the lock manager on the NFS server. o It generates local file locking operations in response to requests forwarded from lock managers running on NFS client machines. State information kept by the lock manager about these locking requests can be lost if the lockd is killed or the operating system is rebooted. Some of this information can be recovered as follows. When the server lock manager restarts, it waits for a grace period for all client-site lock managers to submit reclaim requests. Client-site lock managers, on the other hand, are notified by the status monitor dae- mon, statd(1M), of the restart and promptly resubmit previously granted lock requests. If the lock daemon fails to secure a previously granted lock at the server site, then it sends SIGLOST to a process. Administrators can make changes to the startup parameters for lockd by logging in as root and editing the /etc/default/nfs file (See nfs(4)). OPTIONS
The following options are supported: -g graceperiod Deprecated in favor of GRACE_PERIOD. Specify the number of seconds that all clients (both NLM and NFSv4) have to reclaim locks after the server reboots. It also controls the NFSv4 lease interval. This option is equivalent to the LOCKD_GRACE_PERIOD parameter. -l listen_min_backlog Specify the listener backlog (listen_min_backlog). listen_min_backlog is the number connect requests that are queued and waiting to be processed before new connect requests start to get dropped. -t timeout Specify the number of seconds to wait before retransmitting a lock request to the remote server. The default value is 15 seconds. Equivalent of the LOCKD_RETRANSMIT_TIMEOUT parameter in the nfs file. OPERANDS
nthreads Specify the maximum number of concurrent threads that the server can handle. This concurrency is achieved by up to nthreads threads created as needed in the kernel. nthreads should be based on the load expected on this server. If nthreads is not specified, the maximum number of concurrent threads will default to 20. Equivalent of the LOCKD_SERVERS parameter in the nfs file. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnfscu | +-----------------------------+-----------------------------+ SEE ALSO
svcs(1), automountd(1M), clear_locks(1M), mount_nfs(1M), share(1M), share_nfs(1M), statd(1M), svcadm(1M), fcntl(2), lockf(3C), nfs(4), attributes(5), smf(5) NOTES
The lockd service is managed by the service management facility, smf(5), under the service identifier: svc:/network/nfs/nlockmgr Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser- vice's status can be queried using the svcs(1) command. If it is disabled, it will be enabled by mount_nfs(1M), share_nfs(1M), and automountd(1M) unless its application/auto_enable prop- erty is set to false. This daemon might not exist in a future release of Solaris. SunOS 5.10 17 Nov 2004 lockd(1M)
All times are GMT -4. The time now is 07:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy