Home • Explore • Blog • CI
☰



man-pages
13th chunk of `journalctl.man`
0aa1aefcf810d6143ac3f6cd4338287b9e9bb04cca5b16430000000100000d65
 colors, respectively. This can be specified to override the automatic decision based on $TERM and what the console is connected to.

       $SYSTEMD_URLIFY
           The value must be a boolean. Controls whether clickable links should be generated in the output for terminal emulators supporting this. This can be specified to override the decision that systemd makes based on
           $TERM and other conditions.

EXAMPLES
       Without arguments, all collected logs are shown unfiltered:

           journalctl

       With one match specified, all entries with a field matching the expression are shown:

           journalctl _SYSTEMD_UNIT=avahi-daemon.service
           journalctl _SYSTEMD_CGROUP=/user.slice/user-42.slice/session-c1.scope

       If two different fields are matched, only entries matching both expressions at the same time are shown:

           journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097

       If two matches refer to the same field, all entries matching either expression are shown:

           journalctl _SYSTEMD_UNIT=avahi-daemon.service _SYSTEMD_UNIT=dbus.service

       If the separator "+" is used, two expressions may be combined in a logical OR. The following will show all messages from the Avahi service process with the PID 28097 plus all messages from the D-Bus service (from any
       of its processes):

           journalctl _SYSTEMD_UNIT=avahi-daemon.service _PID=28097 + _SYSTEMD_UNIT=dbus.service

       To show all fields emitted by a unit and about the unit, option -u/--unit= should be used.  journalctl -u name expands to a complex filter similar to

           _SYSTEMD_UNIT=name.service
             + UNIT=name.service _PID=1
             + OBJECT_SYSTEMD_UNIT=name.service _UID=0
             + COREDUMP_UNIT=name.service _UID=0 MESSAGE_ID=fc2e22bc6ee647b6b90729ab34a250b1

       (see systemd.journal‐fields(7) for an explanation of those patterns).

       Show all logs generated by the D-Bus executable:

           journalctl /usr/bin/dbus-daemon

       Show all kernel logs from previous boot:

           journalctl -k -b -1

       Show a live log display from a system service apache.service:

           journalctl -f -u apache

SEE ALSO
       systemd(1), systemd‐cat(1), systemd‐journald.service(8), systemctl(1), coredumpctl(1), systemd.journal‐fields(7), journald.conf(5), systemd.time(7), systemd‐journal‐remote.service(8), systemd‐journal‐upload.service(8)

NOTES
        1. Discoverable Partitions Specification
           https://uapi‐group.org/specifications/specs/discoverable_partitions_specification

        2. Journal Export Format
           https://systemd.io/JOURNAL_EXPORT_FORMATS#journal‐export‐format

        3. Journal JSON Format
           https://systemd.io/JOURNAL_EXPORT_FORMATS#journal‐json‐format

        4. Server‐Sent Events
           https://developer.mozilla.org/en‐US/docs/Server‐sent_events/Using_server‐sent_events

        5. JavaScript Object Notation (JSON) Text Sequences
           https://tools.ietf.org/html/rfc7464

        6. Message Catalog Developer Documentation
           https://www.freedesktop.org/wiki/Software/systemd/catalog

systemd 253                                                                                                                                                                                                        JOURNALCTL(1)
Title: Journalctl Examples (cont.) and See Also
Summary
The text continues with examples of journalctl commands, including filtering by the same field, combining expressions with a logical OR, showing all fields for a unit, displaying logs from a specific executable, showing kernel logs from the previous boot, and viewing a live log display from a system service. It then lists related utilities and specifications in the 'SEE ALSO' section, such as systemd, systemctl, coredumpctl, journald.conf, and links to external specifications.