From owner-freebsd-stable@FreeBSD.ORG Sat Jan 14 15:44:06 2006 Return-Path: X-Original-To: freebsd-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 AF3A516A420 for ; Sat, 14 Jan 2006 15:44:06 +0000 (GMT) (envelope-from ken@abbott.allenmyland.com) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0965D43D46 for ; Sat, 14 Jan 2006 15:44:04 +0000 (GMT) (envelope-from ken@abbott.allenmyland.com) Received: from abbott.allenmyland.com ([68.81.206.140]) by comcast.net (sccrmhc14) with ESMTP id <2006011415440101400f0rn6e>; Sat, 14 Jan 2006 15:44:01 +0000 Received: by abbott.allenmyland.com (Postfix, from userid 1001) id 7969217024; Sat, 14 Jan 2006 10:44:01 -0500 (EST) Date: Sat, 14 Jan 2006 10:44:01 -0500 From: Ken Stevenson To: freebsd-stable@freebsd.org Message-ID: <20060114154401.GA1179@abbott.allenmyland.com> Mail-Followup-To: freebsd-stable@freebsd.org References: <20060114011006.GA83466@abbott.allenmyland.com> <43C88F18.5070902@FreeBSD.org> <20060114141135.G35532@ury.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060114141135.G35532@ury.york.ac.uk> User-Agent: Mutt/1.4.2.1i Subject: Re: postgresql doesn't start on boot-up 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: Sat, 14 Jan 2006 15:44:06 -0000 On Sat, Jan 14, 2006 at 02:12:18PM +0000, Gavin Atkinson wrote: > On Fri, 13 Jan 2006, Doug Barton wrote: > >Ken Stevenson wrote: > >>Also, this is probably a stupid question, but is there a boot.log or > >>something like that shows the bootup messages that come after dmesg? > > > >In /etc/syslog.conf, uncomment the line that mentions console.log, 'touch > >/var/log/console.log', and then reboot after you make the change I > >suggested above. > > ... or "dmesg -a" > > Gavin Thanks, dmesg -a did it. The console log doesn't show the application boot errors I was looking for. With regard to the original problem, it turns out postgresql wasn't starting for the same reason as cups, the startup script is being passed a faststart argument that it doesn't understand. As soon as I figure out how, I'll update the postgresql port which I assume will fix this. -- Ken Stevenson Allen-Myland Inc.