From owner-freebsd-stable@FreeBSD.ORG Wed Feb 22 21:43:15 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6860D16A420; Wed, 22 Feb 2006 21:43:15 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from ns1.jnielsen.net (ns1.jnielsen.net [69.55.238.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 60D3C43D75; Wed, 22 Feb 2006 21:43:07 +0000 (GMT) (envelope-from lists@jnielsen.net) Received: from localhost (jn@ns1 [69.55.238.237]) (authenticated bits=0) by ns1.jnielsen.net (8.12.9p2/8.12.9) with ESMTP id k1MLh2Cn009186; Wed, 22 Feb 2006 13:43:03 -0800 (PST) (envelope-from lists@jnielsen.net) From: John Nielsen To: stable@freebsd.org, rc@freebsd.org, sysadmin@alexdupre.com Date: Wed, 22 Feb 2006 16:42:09 -0500 User-Agent: KMail/1.9.1 X-Face: #X5#Y*q>F:]zT!DegL3z5Xo'^MN[$8k\[4^3rN~wm=s=Uw(sW}R?3b^*f1Wu*. X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on ns1.jnielsen.net X-Virus-Status: Clean Cc: Subject: mysql50-server not starting correctly on FreeBSD 6.1-PRERELEASE (ldconfig, rcorder) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2006 21:43:15 -0000 I installed mysql50-server from an up-to-date ports tree on a new server I'm setting up running FreeBSD 6.1. The port adds the appropriate paths to ldconfig, but the startup script does not require ldconfig. This was causing mysqld not to start up correctly since on my system the mysql-server.sh script was being run before /etc/rc.d/ldconfig. The mysql script failed with errors about libraries being unavailable, etc. Running the mysql-server.sh script again once the system is up works fine. I'm not entirely conversant with the new rc script syntax, but I tried adding "ldconfig" to the REQUIRES line of mysql-server.sh and that seems to have fixed the problem. I now have two questions: 1) Is this a correct fix? 2) If so, should I file a PR with a patch or can someone just get this committed? Thanks, JN