On Sun, 2005-07-17 at 11:16 -0500, Jeff Vian wrote: > On Sun, 2005-07-17 at 10:42 +0100, Ben Roberts wrote: > > The last messages in my boot.log are > > > > sshd: sshd -TERM succeeded > > sshd: succeeded > > xinetd: xinetd -HUP succeeded > > > > I saw somewhere on google groups that someone mentioned that boot > > logs are now written to anaconda.log but surely that can't be the > > case !! > > > > My FC4 system is an upgrade from FC3 - it's also a remote system > > so I really would like the boot log working !! > > > > It would appear that something has changed in the kernel logging > facility (init or something similar) that the boot messages are no > longer given local7 status. I think it is bugzilla time for someone who > can test and confirm this. > > I checked /etc/syslog.conf and the same line is there on both FC3 and > FC4: > # Save boot messages also to boot.log > local7.* /var/log/boot.log > Yet on my system as well, boot.log is empty on FC4 and has the expected > entries on FC3. > > > > > > -----Original Message----- > > From: Jim Cornette [mailto:fc-cornette@xxxxxxxxxxxxxx] > > Sent: 17 July 2005 02:47 > > To: For users of Fedora Core releases > > Subject: Re: FC4 boot.log no longer being written to > > > > > > Matthew Saltzman wrote: > > > > > On Sat, 16 Jul 2005, Jim Cornette wrote: > > > > > >> Ben Roberts wrote: > > >> > > >>> /var/log/dmesg provides different information to what is > > >>> contained in the usual boot.log file under FC2 or FC3 though > > ??? > > >>> > > >>> I am concerned because boot.log is a valuable source of > > >>> information, and since upgrading to FC4 it hasn't been > > updated, > > >>> despite a fair few reboots while configuring the system > > etc.... I > > >>> was wondering if I've removed some rpm package that was > > needed to > > >>> facilitate the writing of boot.log whilst purging my system > > of > > >>> unneeded packages ?? > > >>> > > >>> > > >>> > > >> I read this log on occasion also. It quit working on my > > systemand I > > >> assumed the same thing. Anomther person who upgraded from FC3 > > to FC4 > > >> mentioned the same problem with no more boot logs. > > > > > > > > > I checked, out of curiosity, as I have a fresh FC4 install. > > > /var/log/boot.log contains only messages about > > /sbin/dhclient-script > > > updating /etc/resolv.conf. Otherwise, it's empty. > > > > Messages regarding dhclient are also all that I see in the > > boot.log. I > > didn't mention the /sbin/dhclient messages because I ran dhclient > > to try > > to get my stock kernel to get my network running. It is useful > > information to know that at least the log is useful to resolve > > ethernet > > connection problems? My Installation is an upgrade, so I guess > > the > > problem is not unique to upgrades vs. fresh installations. > > > > Jim > > > > -- > > fedora-list mailing list > > fedora-list@xxxxxxxxxx > > To unsubscribe: > > http://www.redhat.com/mailman/listinfo/fedora-list > > > > > > -- > > No virus found in this incoming message. > > Checked by AVG Anti-Virus. > > Version: 7.0.323 / Virus Database: 267.9.0/50 - Release Date: > > 16/07/2005 > > > > -- > > No virus found in this outgoing message. > > Checked by AVG Anti-Virus. > > Version: 7.0.323 / Virus Database: 267.9.0/50 - Release Date: > > 16/07/2005 > > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151238
