$ Linux One Liners
Back to commands

Linux Survival Basics

Read-only

Show systemd Timer Unit File

You need the effective timer file and drop-ins.

Command

systemctl cat backup.timer

Before you run this

System impact: Read-only. Low when scoped to the shown target.

When not to use it: Do not edit unit files before reading drop-ins and overrides.

Expected output

The unit file plus any drop-in fragments.

System impact

Read-only. Nothing changes. The command reads current state and prints diagnostic evidence.

Recovery / rollback: no state is changed.

When to use it

Use when the timer exists but fires at the wrong time.

When not to use it

Do not edit unit files before reading drop-ins and overrides.

Common misread

Do not edit unit files before reading drop-ins and overrides.

Example run

Commands shown

These are the commands shown for inspection. Treat them as an example, not proof that your system will behave identically.

  1. systemctl cat backup.timer
  2. systemctl cat backup.timer

next steps

Related commands

Linux Survival Basics Read-only

Read One systemd Timer Status

Timer status shows whether the schedule is loaded and active.

systemctl status backup.timer --no-pager
Linux Survival Basics Can be slow

Read Recent systemd Timer Logs

Timer logs show whether systemd attempted to trigger the task.

journalctl -u backup.timer --since "24 hours ago" --no-pager
Linux Survival Basics Read-only

List systemd Timers and Last Runs

A timer can be inactive, missed, or waiting for the wrong calendar.

systemctl list-timers --all --no-pager

next diagnostic step

Where to go from this command

Study mapping

Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.

  • LPIC-1 style command-line practice
  • LFCS style performance-task practice
  • Linux+ style troubleshooting review

Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.