File: include-dmesg

package info (click to toggle)
linux 5.10.13-1
  • links: PTS, VCS
  • area: main
  • in suites: bullseye
  • size: 1,182,916 kB
  • sloc: ansic: 19,488,074; asm: 263,676; sh: 73,873; makefile: 44,685; perl: 34,640; python: 32,386; cpp: 6,070; yacc: 4,755; lex: 2,742; awk: 1,214; ruby: 25; sed: 5
file content (21 lines) | stat: -rw-r--r-- 688 bytes parent folder | download | duplicates (40)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
add_dmesg() {
  local got_log=
  echo '** Kernel log:' >&3
  if [ "$(cat /proc/sys/kernel/dmesg_restrict)" = 0 ]; then
    dmesg > >(tail -n 100 >&3) && got_log=y
  elif command -v sudo >/dev/null; then
    yesno "Use sudo to read the kernel log? " yep
    if [ "$REPLY" = yep ]; then
      sudo dmesg > >(tail -n 100 >&3) && got_log=y
    fi
  fi
  test "$got_log" || echo 'Unable to read kernel log; any relevant messages should be attached' >&3
  echo >&3
}

ask_dmesg() {
  # Remind the user to attach the kernel log.  This should also trigger
  # a reminder in some MUAs if the user tries to send without it.
  echo '** Kernel log: boot messages should be attached' >&3
  echo >&3
}