File: include-dmesg

package info (click to toggle)
linux 4.19.249-2
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 968,784 kB
  • sloc: ansic: 16,810,930; asm: 272,263; makefile: 38,450; sh: 33,900; perl: 27,702; python: 21,148; cpp: 5,068; yacc: 4,650; lex: 2,584; awk: 1,386; ruby: 25; sed: 5
file content (21 lines) | stat: -rw-r--r-- 688 bytes parent folder | download | duplicates (37)
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
}