|
Size: 699
Comment: Single user logging issue fixed since sysvinit 2.86.ds1-11 (BTS #213028), drop woody references, drop dummy category, formatting.
|
Size: 1192
Comment: add new section "Reading /var/log/boot file"
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 17: | Line 17: |
| = Reading /var/log/boot file = Parts of a boot message sometimes can be wrapped with an ASCII color sequences, e.g. "failed" string after unsuccessful init action. bootlogd writes `^[` characters to its log file instead of actual ASCII escape character. To view colored strings via `less` as expected, you must replace `^[` characters with actual escape character and tell `less` to output ASCII color escape sequences in "raw" form: {{{ sed $'s/\^\[/\E/g' /var/log/boot | less -R }}} |
Bootlogd records boot messages.
Activate bootlogd
You do this by editing /etc/default/bootlogd, this is not enabled by default:
# Run bootlogd at startup ? BOOTLOGD_ENABLE=yes
When the system is restarted, userspace messages will be logged to /var/log/boot.
Reading /var/log/boot file
Parts of a boot message sometimes can be wrapped with an ASCII color sequences, e.g. "failed" string after unsuccessful init action. bootlogd writes ^[ characters to its log file instead of actual ASCII escape character. To view colored strings via less as expected, you must replace ^[ characters with actual escape character and tell less to output ASCII color escape sequences in "raw" form:
sed $'s/\^\[/\E/g' /var/log/boot | less -R