Knowledge Base · intrvll · Lübeck
Sysadmin guides for Linux, Windows Server, and the network
14 articles in six categories, from a disk that’s full to a certificate that’s about to expire. Each one names the versions it was written against and the day it was last checked.
Free to read, without an account. Press / on any page to search.
- Articles
- 14
- Categories
- 6
- Commands to copy
- 163
- Last checked
- 24 Oct 2026
Articles by category with every article in each
linux/ · 3 articles
Linux
Disks that fill up, jobs that run on a schedule, and the first look at a server that has slowed down. The commands are for systemd distributions: Debian 12, Ubuntu 24.04, and RHEL 9 and its rebuilds.
- The first five minutes on a slow server
- Find what’s filling a disk
- Run a job on a schedule with systemd timers
networking/ · 3 articles
Networking
Find out what’s listening on a port, test whether a port is reachable from somewhere else, and capture the packets when the answer still isn’t clear.
- Find which process is listening on a port
- Test whether a TCP port is reachable
- Capture traffic with tcpdump
dns/ · 2 articles
DNS
Query records the way a resolver does, tell an authoritative answer from a cached one, and plan a change so it takes effect when you expect it to.
All DNS articlestls/ · 2 articles
TLS and certificates
Read what a server’s certificate says, find out when it expires, and convert keys and certificates between the formats different software asks for.
All TLS and certificates articlesssh/ · 2 articles
SSH
Log in with keys instead of passwords, turn passwords off without locking yourself out, and keep every host’s connection details in one config file.
All SSH articleswindows/ · 2 articles
Windows Server
Read the event log, test connections, and look up DNS from PowerShell, with commands that work on Windows Server 2019, 2022, and 2025.
All Windows Server articlesWhen a server slows down start with these eight commands
Linux · 5 min
The first five minutes on a slow server
Eight commands, in the order to run them, that show whether a slow server is short of CPU, memory, or disk, or whether the problem is somewhere else, before you change anything. Read the article
- 1. Load average with uptime
- 2. Kernel messages with dmesg
- 3. CPU, memory, and waits with vmstat
- 4. Each CPU with mpstat
- 5. Busy processes with pidstat
- 6. Disk latency with iostat
- 7. Available memory with free
- 8. Network traffic with sar and ss
$ uptime 14:02:11 up 41 days, 3:17, 2 users, load average: 11.84, 9.02, 4.10$ nproc4$ vmstat 1 3procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu----- r b swpd free buff cache si so bi bo in cs us sy id wa st 2 9 1572864 81240 10212 412880 612 904 9812 1204 2210 4120 6 4 22 68 0 1 11 1574912 79112 10212 409744 588 1012 10240 988 2301 4388 5 5 19 71 0# 71% of the time waiting for disk, and swapping: memory first
Recently checked against the versions named on each
Missing an article?
Tell us the task you were trying to do and the system it was on. Mail to intrvll is answered within a business day, from Lübeck.