Date: Wed, 2 Jun 2004 10:13:22 -0400 (EDT) From: "Jason M. Leonard" <fuzz@ldc.upenn.edu> To: questions@freebsd.org Subject: TCP port 993 hijacked by mountd, rpc.statd Message-ID: <20040602100224.T910@lorax.ldc.upenn.edu>
next in thread | raw e-mail | index | archive | help
Greetings, I have a production mail server that runs imaps. Sometimes when I reboot, tcp port 993 (imaps according to /etc/services) is taken by either rpc.statd or (currently) mountd before inetd starts, which causes imaps to fail. I tried rearranging things in rc.d, but the RPC bits seem pretty determined to start before the inetd bits. I can manually stop rpc.statd or mountd, restart inetd, then restart rpc.statd or mountd, but that seems to screw up RPC for my Sun workstation NFS clients. In fact they won't even boot because they can't mount /var/mail. So right now I have the option of providing email service to my IMAP clients or providing them with functioning workstations, but not both. Any suggestions? Any idea wow can I reserve TCP port 993 so that RPC will leave it alone? This is 5.2.1-RELEASEp5 running uw-imap; I can provide more details if necessary. :Fuzz
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040602100224.T910>