Originally Posted by vikas027
This does not happen normally, what you can try is
- first stop nfs service
- verify whether 993 is port is freed or not
- start dovecot service
- start nfs service
I think this will work.
It worked. But; it has given rise to few more fundamental questions.
1) So; does this means; that NFS service is so brazen; that it would use even the IANA port assignments.
in the name of random assigning of the ports.?
Following statement is found in RFC 1700.
Portmap does not allocate ports, the kernel allocates ports. The code
that does this is part of nearly every UNIX system in the world (and
since the BSD code is 'free' it is often the same code). RPC services
ask the kernel to allocate them a port by calling the "bind()" system
call. The parameter they pass is "INADDR_ANY" which means "allocate
me any IP port you want". The kernel does that by looking at all of
the ports that are currently in use and picking one that is not
currently used. The number picked is either less that 1024 if the
process is privledged, or greater than 1024 if the process is not
privledged. After the kernel has allocated a port, the service
registers this allocation with portmap. The portmapper is merely a
registry of previously allocated ports. Note "allocated" here is
being used in the sense that they are used by an open socket, not
assigned a well known name.
This statement has amazed me
. It means; next time; whenever I want to start any new service in my system.
- first stop portmap service
- verify whether the assigned port is freed or not
- start new service
- start portmap service.
Any other opinions are welcome.