From owner-freebsd-questions@FreeBSD.ORG Mon Aug 22 11:49:55 2005 Return-Path: X-Original-To: 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 776A116A41F for ; Mon, 22 Aug 2005 11:49:55 +0000 (GMT) (envelope-from Martin.Ward@durham.ac.uk) Received: from hermes.dur.ac.uk (hermes.dur.ac.uk [129.234.4.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id BEED043D45 for ; Mon, 22 Aug 2005 11:49:53 +0000 (GMT) (envelope-from Martin.Ward@durham.ac.uk) Received: from smtphost2.dur.ac.uk (smtphost2.dur.ac.uk [129.234.4.209]) by hermes.dur.ac.uk (8.11.7-20030923/8.11.7) with ESMTP id j7MBndP13543; Mon, 22 Aug 2005 12:49:39 +0100 (BST) Received: from localhost (procyon.dur.ac.uk [129.234.4.82]) by smtphost2.dur.ac.uk (8.12.10+Sun/8.11.7) with ESMTP id j7MBnVNg009584; Mon, 22 Aug 2005 12:49:31 +0100 (BST) From: Martin Ward To: fuzz@ldc.upenn.edu Date: Mon, 22 Aug 2005 12:49:31 +0100 User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508221249.31288.Martin.Ward@durham.ac.uk> X-DurhamAcUk-MailScanner: Found to be clean, Found to be clean Cc: freebsd-questions@freebsd.org Subject: Re: TCP port 993 hijacked by mountd, rpc.statd X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Aug 2005 11:49:55 -0000 Way back on Wed Jun 2 07:13:23 PDT 2004 on freebsd-questions you wrote: > 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 just had the same problem with my Linux Mandrake system. I found your message via Google. One solution I found is to tell mountd and statd to use a particular port, instead of the random one assigned by portmap, using the -p option. On my system, mountd and statd are started up by /etc/rc.d/init.d/nfs which reads /etc/sysconfig/nfs for confif options. I just had to uncomment two lines in /etc/sysconfig/nfs: # Pin mountd to a given port rather than random one from portmapper MOUNTD_PORT=4002 # Set fixed port for statd STATD_PORT=4000 If you can find the startup script that starts mountd and statd and add "-p 4002" to mountd and "-p 4000" to statd, then that should fix the problem. /etc/sysconfig/nfs has similar entries for lockd: LOCKD_TCPPORT=4001 LOCKD_UDPPORT=4001 But the man page says that rpc.lockd "is usually not requred". -- Martin Martin.Ward@durham.ac.uk http://www.cse.dmu.ac.uk/~mward/ Erdos number: 4 G.K.Chesterton web site: http://www.cse.dmu.ac.uk/~mward/gkc/