On Sat, Jul 25, 2009 at 3:29 PM, Dan McGee<dpmc...@gmail.com> wrote: > On Sat, Jul 25, 2009 at 4:49 PM, David C. > Rankin<drankina...@suddenlinkmail.com> wrote: >> Listmates, >> >> Seems like a simple question, but I've searched /var/log and can't >> find a file that contains the boot history showing all the "fail" messages >> during boot. For some reason after the latest update, my i686 box showed a >> half dozen or so "fail" messages. I need to find the log of what died. >> >> The upside to this? This was my i686 box that would no longer start >> kde after the next-previous set of updates. Now kde4 starts fine again. >> >> Whatever failed can't be that critical because the box is functioning >> fine, but I still want to find out what failed. If the file is in /var/log, >> then I just flat missed it. I thought it would be daemons.log, but I found >> no fail messages. > > This might not actually be logged anywhere now that I think about it. > To devs- am I wrong, or maybe we should add some syslog foo in here so > this stuff is more easily traceable? > > I personally disable the VC on tty1 in inittab on all machines so that > no console overwrites the boot screen.
Nope, not logged anywhere. Those messages, however, are arch messages. The daemon itself that fails should write its output somewhere. If you just want a list of what isn't running, you can always look in... hmm whatever the dir is... /var/run/daemons I think, and compare that to rc.conf. syslogging this is acceptable if someone wants to supply a patch
