Skip to main content
Tweeted twitter.com/ServerFault/status/1417046565278076930
Remove messages tag
Link
faker
  • 17.7k
  • 2
  • 64
  • 71
Add rsyslog.conf
Source Link
MarkDBlackwell
  • 351
  • 1
  • 2
  • 10

How can the messages that scroll by when booting a Debian system be reviewed later?

In other words, how can I review absolutely all of them conveniently? That's the important point to the question; merely a subset of them is insufficient.

Some boot time messages are written only to /var/log/daemon.log and /var/log/syslog, where I have seen messages like: udevd[240]: SYSFS{}= will be removed in a future udev version.

In squeeze, these are not in /var/log/dmesg. Nor are they in /var/log/boot with setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd and package bootlogd installed.

For more details on rsyslogd's various logging locations see your /etc/rsyslog.conf.

How can the messages that scroll by when booting a Debian system be reviewed later?

In other words, how can I review absolutely all of them conveniently? That's the important point to the question; merely a subset of them is insufficient.

Some boot time messages are written only to /var/log/daemon.log and /var/log/syslog, where I have seen messages like: udevd[240]: SYSFS{}= will be removed in a future udev version.

In squeeze, these are not in /var/log/dmesg. Nor are they in /var/log/boot with setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd and package bootlogd installed.

How can the messages that scroll by when booting a Debian system be reviewed later?

In other words, how can I review absolutely all of them conveniently? That's the important point to the question; merely a subset of them is insufficient.

Some boot time messages are written only to /var/log/daemon.log and /var/log/syslog, where I have seen messages like: udevd[240]: SYSFS{}= will be removed in a future udev version.

In squeeze, these are not in /var/log/dmesg. Nor are they in /var/log/boot with setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd and package bootlogd installed.

For more details on rsyslogd's various logging locations see your /etc/rsyslog.conf.

Simplify
Source Link
MarkDBlackwell
  • 351
  • 1
  • 2
  • 10

How can the messages that scroll by when booting a Debian system be reviewed later?

In other words, how can I review absolutely all of them conveniently? That's the important point to the question; merely a subset of them is insufficient.

Some boot time messages are written only to /var/log/daemon.log and /var/log/syslog, where I have seen messages like: udevd[240]: SYSFS{}= will be removed in a future udev version.

In squeeze, these are not found by thein /var/log/dmesg command, nor even with the bootlogd package. Nor are they in /var/log/boot with setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd and package bootlogd installed.

How can the messages that scroll by when booting a Debian system be reviewed later?

In other words, how can I review absolutely all of them conveniently? That's the important point to the question; merely a subset of them is insufficient.

Some boot time messages are written only to /var/log/daemon.log and /var/log/syslog, where I have seen messages like: udevd[240]: SYSFS{}= will be removed in a future udev version.

In squeeze, these are not found by the dmesg command, nor even with the bootlogd package in /var/log/boot.

How can the messages that scroll by when booting a Debian system be reviewed later?

In other words, how can I review absolutely all of them conveniently? That's the important point to the question; merely a subset of them is insufficient.

Some boot time messages are written only to /var/log/daemon.log and /var/log/syslog, where I have seen messages like: udevd[240]: SYSFS{}= will be removed in a future udev version.

In squeeze, these are not in /var/log/dmesg. Nor are they in /var/log/boot with setting BOOTLOGD_ENABLE=yes in /etc/default/bootlogd and package bootlogd installed.

Add backticks
Source Link
MarkDBlackwell
  • 351
  • 1
  • 2
  • 10
Loading
Clarify that all are needed
Source Link
MarkDBlackwell
  • 351
  • 1
  • 2
  • 10
Loading
Source Link
MarkDBlackwell
  • 351
  • 1
  • 2
  • 10
Loading