BootLogd

Differences between revisions 4 and 5
⇤ ← Revision 4 as of 2005-04-25 00:04:02 →
Size: 1188
Editor: intern146
Comment:
← Revision 5 as of 2005-04-26 01:51:19 → ⇥
Size: 2122
Editor: intern146
Comment:
Deletions are marked like this. Additions are marked like this.
Line 44: Line 44:
 * How early should it be enabled? One of the suggestions (#272428) included starting bootlogd from initrd, so that everything gets logged.
Line 47: Line 48:
 * Research the problems which resulted in Debian when enabling bootlogd the last time (udev related?)  Bootlogd is started (in debian) from S05 (after udev, mountvirtfs, and mdadm), and logs to /var/log/boot. The
(sysvinit) author considers it broken/experimental, and has disabled it by default.

 Known problems include:
   * #205724: Since it runs before fsck, it logs all spinner changes. This causes huge logfiles, and slows down
     fsck considerably since it fsyncs after every line/write. Joeyh proposed only writing upon newlines...
   * #237056: udev was not providing /dev/ttyzf, which bootlogd needs. This appears to no longer be the case; at
     least w/ debian's udev_056-2 + 2.6.11, as well a hoary's udev (w/ 2.6.10), /dev/ttyzf is created.
   * #213028: bootlogd needs to not run while in single user mode, otherwise things like passwords, fsck, and
     lots of unnecessary stuff end up getting logged to a world-writable log file.
 
 Suggestions by the author

UbuntuDevel/BootLogd

Status

Introduction

Preserve output from the system initialization process.

Rationale

Much useful information is discarded, especially due to early gdm startup, and later UbuntuDevel/USplash.

Scope and Use Cases

Implementation Plan

Data Preservation and Migration

Packages Affected

User Interface Requirements

Outstanding Issues

UDU BOF Agenda

  • What needs to be done in order to enable bootlogd?
  • Enable it and start fixing the bugs
  • How early should it be enabled? One of the suggestions (#272428) included starting bootlogd from initrd, so that everything gets logged.

UDU Pre-Work

  • Bootlogd is started (in debian) from S05 (after udev, mountvirtfs, and mdadm), and logs to /var/log/boot. The

(sysvinit) author considers it broken/experimental, and has disabled it by default.

  • Known problems include:
    • #205724: Since it runs before fsck, it logs all spinner changes. This causes huge logfiles, and slows down
      • fsck considerably since it fsyncs after every line/write. Joeyh proposed only writing upon newlines...
    • #237056: udev was not providing /dev/ttyzf, which bootlogd needs. This appears to no longer be the case; at
      • least w/ debian's udev_056-2 + 2.6.11, as well a hoary's udev (w/ 2.6.10), /dev/ttyzf is created.
    • #213028: bootlogd needs to not run while in single user mode, otherwise things like passwords, fsck, and
      • lots of unnecessary stuff end up getting logged to a world-writable log file.
    Suggestions by the author

UbuntuDownUnder/BOFs/BootLogd (last edited 2010-03-31 07:46:27 by pool-71-173-140-218)