Date: Sat, 14 Jan 2006 10:44:01 -0500 From: Ken Stevenson <ken@abbott.allenmyland.com> To: freebsd-stable@freebsd.org Subject: Re: postgresql doesn't start on boot-up Message-ID: <20060114154401.GA1179@abbott.allenmyland.com> In-Reply-To: <20060114141135.G35532@ury.york.ac.uk> References: <20060114011006.GA83466@abbott.allenmyland.com> <43C88F18.5070902@FreeBSD.org> <20060114141135.G35532@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060114154401.GA1179>