rquotad stole port 993 from imaps!

RHEL4-AS, running an older rpm of imap: imap-2002d-11.

Anyway, last night, after a restart, the portmap gave port 993 to
rpc.rquotad. And thus when imaps tried to start, it failed:

rpc.rquotad stole 993:

> zeus:/var/log# lsof -i :993
> COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
> rpc.rquot 3341 root 4u IPv4 7401 TCP *:imaps (LISTEN)

this, imaps failed to start because it's forced to use 993:

> Nov 19 21:06:22 zeus xinetd[3297]: bind failed (Address already in use (errno = 98)). service = imaps

I realize portmap assigns ports (that aren't in use?) to rpc services,
giving it some port number below 1024. But why would portmap give it
993? Shouldn't portmap never give out 993? OR did portmap think that
993 wasn't being used (because imaps failed at boot?) and thus when
portmap gave 993 to rquotad, imaps was destined to fail unless we
killed rquotad first (which we did).

Anyway, our problem is fixed now, we killed rquotad, and started
portmap on 993, and then started rquotad (portmap gave it855 and 870
this time). How do I stop portmap from giving any service port 993? Or
am I missing some understanding of how portmap works?

Alex

On 20 Nov 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>, (E-Mail Removed)
wrote:

>Anyway, last night, after a restart, the portmap gave port 993 to
>rpc.rquotad. And thus when imaps tried to start, it failed:

>> zeus:/var/log# lsof -i :993
>> COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
>> rpc.rquot 3341 root 4u IPv4 7401 TCP *:imaps (LISTEN)

PID 3341

>> Nov 19 21:06:22 zeus xinetd[3297]: bind failed (Address already in use (errno
>= 98)). service = imaps

PID 3297 In theory, you might put a delay between the processes to
allow xinetd to grab the needed ports before portmapper hands it out.

>I realize portmap assigns ports (that aren't in use?) to rpc services,
>giving it some port number below 1024. But why would portmap give it
>993?

Why not? Not every one is using every one of the "well known ports".

>Shouldn't portmap never give out 993?

Well, I'm not running IMAPS, so why shouldn't portmap hand it out? ;-)

>How do I stop portmap from giving any service port 993? Or am I missing
>some understanding of how portmap works?

-rw-rw-r-- 1 gferg ldp 127205 Aug 26 2002 NFS-HOWTO

Section 6.4

In kernels 2.4.13 and later with nfs-utils 0.3.3 or later you no longer have
to worry about the floating of ports in the portmapper. Now all of the
daemons pertaining to nfs can be "pinned" to a port. Most of them nicely take
a -p option when they are started; those daemons that are started by the
kernel take some kernel arguments or module options.

There's a lot more material in that HOWTO.

Old guy