Changes between Version 17 and Version 18 of ReportingBugs


Ignore:
Timestamp:
Apr 5, 2019, 3:09:59 PM (6 months ago)
Author:
waddlesplash
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ReportingBugs

    v17 v18  
    5454
    5555=== Syslog ===
    56 '''This is the preferred method for gaining information from a non-booting system.'''[[BR]]
    57 The syslog (short for system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It's usually a good idea to attach it to the kernel related Trac ticket. The syslog is written to the file `/boot/system/var/log/syslog`. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDL sessions).
     56'''This is the preferred method for gaining information from a non-booting or crashing system.'''
    5857
    59 The option ''Enable debug syslog'' in the boot loader's ''Debug menu'' makes the syslog somewhat persistent in memory. By default the option is enabled. "Somewhat persistent" means that it survives a reset and will still be accessible when you enter the boot loader menu directly afterwards. Booting an operating system (Haiku definitely, others likely) destroys the information, though. So you have to enter the boot loader menu, e.g. by holding down the `Shift` key. In the boot loader's ''Debug menu'' you should now find the entries ''Display syslog from previous session'' and ''Save syslog from previous session''. The former displays the syslog on screen, the latter allows you to save it as a file to disk. Note that at the moment only FAT32 volumes are supported for writing the file to. If you want to use a USB stick, but have plugged it in too late so that it isn't recognized yet, you can reset the machine and re-enter the boot loader menu. But again: Don't accidentally boot any operating system or the data will be lost.
     58The syslog (system log) contains valuable information about what has happened in your system, including the output of KDL sessions. It can be found at **`/var/log/syslog`**. Since writing to a file requires a working system, the most recent output might not have made it to the syslog when a kernel problem occurs (particularly on spontaneous reboots or uncontinuable KDLs.)
     59
     60The option ''Enable debug syslog'' in the boot loader's ''Debug menu'' makes the syslog somewhat persistent in memory. (By default, the option is enabled.) This means that it will (usually) survive a reset. If you are lucky, it will be saved to **`/var/log/previous_syslog`** on reboot; if you are not, you will have to enter the boot loader menu, and choose ''Debug menu'' and then ''Display syslog from previous session'' or ''Save syslog from previous session''. The former displays the syslog on screen, the latter allows you to save it as a file to disk. (Note that at the moment only FAT32 volumes are supported for writing the file to.) If you want to use a USB stick, but have plugged it in too late so that it isn't recognized, you can reset the machine and re-enter the boot loader menu.
     61
     62When attaching the syslog to a ticket, just attach it directly, *don't* put it inside a zipfile or other archive.
    6063
    6164=== On Screen Debug Output ===