From owner-freebsd-current@FreeBSD.ORG Wed Oct 6 22:43:17 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8414416A4CE for ; Wed, 6 Oct 2004 22:43:17 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6181143D1F for ; Wed, 6 Oct 2004 22:43:17 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id E4FABF1BFC; Wed, 6 Oct 2004 15:43:14 -0700 (PDT) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01615-04; Wed, 6 Oct 2004 15:43:14 -0700 (PDT) Received: from [24.199.45.54] (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 2EF1CF1970; Wed, 6 Oct 2004 15:43:14 -0700 (PDT) From: Sean McNeil To: Dan Nelson In-Reply-To: <20041006205954.GB3848@dan.emsphone.com> References: <1097095438.1208.7.camel@server> <20041006205954.GB3848@dan.emsphone.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-rGSzP7AJFCELNB2c9osV" Message-Id: <1097102594.1805.4.camel@server> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Wed, 06 Oct 2004 15:43:14 -0700 X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-current@freebsd.org Subject: Re: amd sitting on ldaps port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Oct 2004 22:43:17 -0000 --=-rGSzP7AJFCELNB2c9osV Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-10-06 at 13:59, Dan Nelson wrote: > In the last episode (Oct 06), Sean McNeil said: > > Looking at /etc/services is states that 636 is for ldaps, but I see tha= t > > amd is using it: > >=20 > > server# sockstat | grep 636 > > root amd 468 5 tcp4 *:636 *:* >=20 > That's just a random port rpcbind assigned to the "amd" rpc service.=20 > If you reboot I bet it'll bind to a different port. Run "rpcinfo -p > localhost" to see all the local port numbers assigned to RPC clients. OK, but aren't there rules about rpc allowing assigned ports like that?=20 It actually does not get another port on reboot. It always binds to that one each time. Perhaps if I changed my configuration somewhat it would make a difference. It has always bothered me that the slapd is now in /usr/local/etc/rc.d and doesn't come up until very late in the boot process. Shouldn't something with assigned ports like this either be started much earlier (i.e. before amd) or the ports prevented from being used by anyone that doesn't provide that service? Seems to me that amd is in the wrong here for having that port. So that means that rpcbind is in the wrong for assigning it to amd. Cheers, Sean --=-rGSzP7AJFCELNB2c9osV Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBZHUByQsGN30uGE4RAtMOAJwIx4NsOlOdlg3Lg8ghKOZb5bmv1gCfdni8 ee3lv1fCfxYax7abEJ1qzM4= =i7Ca -----END PGP SIGNATURE----- --=-rGSzP7AJFCELNB2c9osV--