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. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
