From owner-freebsd-questions@FreeBSD.ORG  Wed Jun  2 07:13:23 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6CAEF16A4CE
	for <questions@freebsd.org>; Wed,  2 Jun 2004 07:13:23 -0700 (PDT)
Received: from lorax.ldc.upenn.edu (lorax.ldc.upenn.edu [158.130.16.184])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 28EB443D39
	for <questions@freebsd.org>; Wed,  2 Jun 2004 07:13:23 -0700 (PDT)
	(envelope-from fuzz@ldc.upenn.edu)
Received: by lorax.ldc.upenn.edu (Postfix, from userid 32822)
	id AC2E622827; Wed,  2 Jun 2004 10:13:22 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1])
	by lorax.ldc.upenn.edu (Postfix) with ESMTP id 9812222820
	for <questions@freebsd.org>; Wed,  2 Jun 2004 10:13:22 -0400 (EDT)
Date: Wed, 2 Jun 2004 10:13:22 -0400 (EDT)
From: "Jason M. Leonard" <fuzz@ldc.upenn.edu>
To: questions@freebsd.org
Message-ID: <20040602100224.T910@lorax.ldc.upenn.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: TCP port 993 hijacked by mountd, rpc.statd
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Jun 2004 14:13:23 -0000

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