[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7APBR1DHB5RY90BT3BKAQMB":3,"skill-same:01M7APBR1DHB5RY90BT3BKAQMB":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7APBR1DHB5RY90BT3BKAQMB","sysadmin-reference",null,"Use when checking a sysadmin anti-pattern, looking up a kernel or system limit, confirming a distribution lifecycle or kernel LTS date (verified August 2026), finding the books, or needing the fifteen commands that carry most of the load, a first-five-minutes routine for an unfamiliar sick box, and a pre-change checklist. Companion to the other linux-server-admin skills.","the-vibey-project\u002Fvibey","the-vibey-project","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F329298758?v=4","01M7AJHGZ9722CTJ4JNQZVRH0Q","the vibey project","01M7AJHGZVMG2K7TGXQ6XFHVG3",5,"MIT","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Flinux-server-admin\u002Fskills\u002Fsysadmin-reference\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sysadmin-reference\ndescription: \"Use when checking a sysadmin anti-pattern, looking up a kernel or system limit, confirming a distribution lifecycle or kernel LTS date (verified August 2026), finding the books, or needing the fifteen commands that carry most of the load, a first-five-minutes routine for an unfamiliar sick box, and a pre-change checklist. Companion to the other linux-server-admin skills.\"\n---\n\n# Linux Server Administration: Anti-Patterns, Limits, Lifecycle Dates, and Command Reference\n\n> **Part 5 of 5** of the *Linux Server Administration* reference (plugin `linux-server-admin`), covering §15–§20. Sibling skills: `sysadmin-filesystem-permissions-and-processes` (§0–§3), `sysadmin-systemd-storage-and-networking` (§4–§6), `sysadmin-packages-boot-and-hardening` (§7–§9), `sysadmin-observability-troubleshooting-and-operations` (§10–§14). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The core — POSIX semantics, kernel subsystems, systemd, networking — is stable; distribution lifecycle dates and kernel LTS windows move. See §17 below for the dated table.\n\n> **How to read this.** Command-dense and operational. Assumes you can already use a\n> shell; this is about understanding the machine well enough to fix it under pressure.\n>\n> **⚠️ GOTCHA** boxes mark what causes outages or silent data loss.\n>\n> **The three mental models that make everything else make sense:**\n> 1. **⚠️ Everything is a file descriptor, and the kernel is the only thing that can\n>    actually do anything.** Userspace asks via syscalls. **When something \"doesn't work,\"\n>    the question is always: which syscall failed, and what errno?** — and `strace` will\n>    tell you (§12 → `sysadmin-observability-troubleshooting-and-operations`).\n> 2. **⚠️ State lives in four places and they disagree**: what's on disk, what's in the\n>    kernel's memory, what the running process loaded at start, and what your config\n>    management thinks. **Most confusing bugs are a disagreement between these** (§11.2 → `sysadmin-observability-troubleshooting-and-operations`).\n> 3. **⚠️ A server is a cache of your configuration management, not a pet.** If you cannot\n>    rebuild it from source control, you don't have a server — you have an artifact\n>    nobody understands (§15).\n\n---\n\n## §15. Anti-Patterns\n\n| Anti-pattern | Why |\n|---|---|\n| **Disabling SELinux** | ⚠️ **Fix the label. Two commands** (§9.2 → `sysadmin-packages-boot-and-hardening`) |\n| Editing vendor unit files in `\u002Fusr\u002Flib` | ⚠️ **Overwritten on update. Use `systemctl edit`** (§4.1 → `sysadmin-systemd-storage-and-networking`) |\n| Forgetting `daemon-reload` | Your edit isn't loaded (§4.1 → `sysadmin-systemd-storage-and-networking`) |\n| `Requires=` without `After=` | ⚠️ **Starts in parallel; fails** (§4.2 → `sysadmin-systemd-storage-and-networking`) |\n| `\u002Fdev\u002FsdX` in fstab | ⚠️ **Names aren't stable. Use UUID** (§5.3 → `sysadmin-systemd-storage-and-networking`) |\n| Rebooting without `mount -a` | ⚠️ **Stranded at emergency shell** (§5.3 → `sysadmin-systemd-storage-and-networking`) |\n| `kill -9` first | Skips flush and cleanup (§3 → `sysadmin-filesystem-permissions-and-processes`) |\n| Panicking about low \"free\" memory | ⚠️ **Read `available`. Cache is doing its job** (§10.2 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Enabling a firewall before allowing SSH | ⚠️ **Lockout** (§6.3 → `sysadmin-systemd-storage-and-networking`) |\n| Changing firewall rules with no rollback timer | Same (§6.3 → `sysadmin-systemd-storage-and-networking`) |\n| Password SSH auth | ⚠️ **Keys only is the biggest single win** (§9.4 → `sysadmin-packages-boot-and-hardening`) |\n| Reloading sshd without `sshd -t` | Console trip (§9.4 → `sysadmin-packages-boot-and-hardening`) |\n| `net.ipv4.tcp_tw_recycle` | ⚠️ **Removed from the kernel; broke NAT clients** (§6.4 → `sysadmin-systemd-storage-and-networking`) |\n| Ignoring `.rpmnew`\u002F`.dpkg-dist` | ⚠️ **Running old config plus a file you never read** (§7 → `sysadmin-packages-boot-and-hardening`) |\n| Using `strace` on a hot production process | ⚠️ **ptrace stops it on every syscall** (§10.4 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Treating LVM snapshots as backups | They fill and break (§5.2 → `sysadmin-systemd-storage-and-networking`) |\n| Untested backups | ⚠️ **Not backups** (§14 → `sysadmin-observability-troubleshooting-and-operations`) |\n| File-copying a running database | ⚠️ **Corrupt restore** (§14 → `sysadmin-observability-troubleshooting-and-operations`) |\n| `--privileged` containers | Kernel is shared (§12 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Alerting on CPU% instead of symptoms | Noise, then ignored alerts (§10.5 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Manual fixes with config management running | ⚠️ **Reverted in 30 minutes** (§11.2 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Theorizing before asking \"what changed?\" | ⚠️ **The highest-yield question** (§11.1 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Volatile journal on a production box | ⚠️ **No logs from the crash** (§4.4 → `sysadmin-systemd-storage-and-networking`) |\n| Running as root because it's easier | Capabilities and systemd sandboxing exist (§2.2 → `sysadmin-filesystem-permissions-and-processes`, §4.3 → `sysadmin-systemd-storage-and-networking`) |\n| `ifconfig`\u002F`netstat` muscle memory | Deprecated; `ip`\u002F`ss` show more (§6.1 → `sysadmin-systemd-storage-and-networking`) |\n\n---\n\n## §16. Numbers and Limits\n\n```\nSIGNALS      TERM 15 · KILL 9 · HUP 1 · INT 2 · QUIT 3 · USR1 10 · USR2 12\nPERMISSIONS  r4 w2 x1 · setuid 4000 · setgid 2000 · sticky 1000 · umask 022\nEXIT CODES   0 ok · 1 general · 2 misuse · 126 not executable · 127 not found\n             ⚠️ 128+N = killed by signal N (137 = SIGKILL, 143 = SIGTERM)\nPORTS        \u003C1024 privileged (⚠️ or CAP_NET_BIND_SERVICE)\n             22 SSH · 25 SMTP · 53 DNS · 80\u002F443 HTTP(S) · 123 NTP · 3306 MySQL\n             5432 Postgres · 6379 Redis · 9090 Prometheus\nLIMITS       Default nofile often 1024 ⚠️ (far too low for servers — set 65535)\n             PID max default 4194304 on 64-bit\n             Ephemeral ports default 32768–60999\nLOAD         Divide by core count; ⚠️ includes D-state (I\u002FO), not just CPU\nFS           ext4 max file 16 TiB · XFS ⚠️ cannot shrink · inode exhaustion is separate\nTIME         ⚠️ Always UTC on servers. `timedatectl set-timezone UTC`\n```\n\n---\n\n## §17. Lifecycle Dates — verified August 2026\n\n**⚠️ Lifecycle dates are the one genuinely perishable thing in this document. Verify\nagainst the vendor before planning a migration.**\n\n| Distribution | Status as of August 2026 |\n|---|---|\n| **RHEL 10** | Released **20 May 2025**. Full support to ~**May 2030**, maintenance to ~**May 2035**. Latest minor **10.2** (May 2026) |\n| **RHEL 9** | Full support to **31 May 2027**, maintenance to **31 May 2032** |\n| **RHEL 8** | ⚠️ **Full support ended 31 May 2024**; 8.10 is the final minor, maintenance to **31 May 2029** |\n| **RHEL 7** | ⚠️ **Maintenance ended 30 June 2024**; ELS extended to **31 May 2029** |\n| **Ubuntu 26.04 LTS** | Current LTS, released **April 2026**, standard support to **30 April 2031** |\n| **Ubuntu 24.04 LTS** | Supported to **31 May 2029** |\n| **Ubuntu 25.10** | ⚠️ **EOL 1 July 2026** — interim releases get 9 months |\n\n**⚠️ RHEL's lifecycle is unusually complex** — overlapping **Full Support → Maintenance\nSupport → Extended Life → ELS** phases, each meaning something different about which\npatches you actually receive. **\"Is it EOL?\" is the wrong question; \"which phase, and does\nthat phase still ship security errata?\" is the right one.** **Ubuntu LTS is 5 years\nstandard, extendable via Pro\u002FESM.**\n\n**⚠️ Kernel LTS windows have been volatile**: historically six years, **cut to a 2-year\ndefault in 2023** as maintainers cited burnout, then **partially extended again in early\n2026 after industry pushback.** ⚠️ **But upstream kernel.org lifecycle usually isn't what\ngoverns you — your distribution's backporting is.** **A RHEL 9 kernel gets security fixes\nlong after the upstream branch is dead.**\n\n⚠️ **One claim I encountered and am flagging rather than repeating as fact**: a source\nasserts a **Linux 7.0** release in 2026 following the 6.x series. **I could not corroborate\nthis against kernel.org and have not built anything in this document on it.** Version\nnumbering in Linux is arbitrary by policy, so it's plausible — **verify before quoting.**\n\n**eBPF tooling** (§10.4 → `sysadmin-observability-troubleshooting-and-operations`) is mature and stable in interface: **BCC** ships **80+ ready-made\ntools**, **bpftrace** is the one-liner language, and **libbpf + CO-RE** is the production\npath for custom programs. ⚠️ **This is now baseline knowledge rather than specialist\ntooling.**\n\n---\n\n## §18. Books\n\n| Author | Work | Why |\n|---|---|---|\n| **Nemeth et al.** | ***UNIX and Linux System Administration Handbook*** | ⚠️ **The one book. Comprehensive, opinionated, current** |\n| **Gregg** | ***Systems Performance*** | ⚠️ **§10 → `sysadmin-observability-troubleshooting-and-operations`'s method. The definitive performance text** |\n| **Gregg** | ***BPF Performance Tools*** | §10.4 → `sysadmin-observability-troubleshooting-and-operations`, from the person who built most of them |\n| **Love** | *Linux System Programming* | What syscalls actually do |\n| **Bovet & Cesati** | *Understanding the Linux Kernel* | Deeper, older, still clarifying |\n| **Kerrisk** | ***The Linux Programming Interface*** | ⚠️ **The syscall reference. Enormous and authoritative** |\n| **Beyer et al.** | ***Site Reliability Engineering*** | ⚠️ **Free online. The operational philosophy** |\n| **Limoncelli et al.** | *The Practice of System and Network Administration* | The process side |\n| **Barrett et al.** | *SSH: The Definitive Guide* | §9.4 → `sysadmin-packages-boot-and-hardening` in depth |\n| **Ward** | *How Linux Works* | ⚠️ **The best entry point if the model isn't solid yet** |\n\n**Primary and practical**: **`man` pages** (⚠️ **`man 7 capabilities`, `man 5 systemd.exec`\nand `man 7 signal` in particular — better than most blog posts**), **`systemd.io`**,\n**Arch Wiki** (⚠️ **the best Linux documentation on the internet regardless of your\ndistro**), **Red Hat and Ubuntu documentation**, **`brendangregg.com`**, **`ebpf.io`**,\n**`endoflife.date`** for §17.\n\n---\n\n## §19. Command Reference\n\n### 19.1 The fifteen that carry most of the load\n```\nsystemctl status|list-units --failed|cat|edit      service truth\njournalctl -u X -f | -p err -b | -b -1             log truth\nss -tulpn                                          what's listening\nip -br a · ip r get IP                             network truth\nlsblk -f · df -h · df -i                           storage truth\ndu -xh --max-depth=1 \u002F                             where did the space go\nlsof +L1                                           ⚠️ deleted-but-open files\nfree -m                                            ⚠️ read \"available\"\nvmstat 1 · iostat -xz 1 · mpstat -P ALL 1          saturation\ndmesg -T | tail -50                                ⚠️ OOM, hardware, resets\nps auxf · pstree -p                                process tree\nstrace -f -p PID  \u002F  execsnoop, opensnoop          ⚠️ what is it actually doing\nausearch -m avc -ts recent                         SELinux denials\nnft list ruleset                                   firewall truth\nfind \u002Fetc -name '*.rpmnew' -o -name '*.dpkg-dist'  ⚠️ config drift after updates\n```\n\n### 19.2 First five minutes on an unfamiliar sick box\n```\nuptime; w                          load, who's on, how long up\nsystemctl list-units --failed      ⚠️ start here\njournalctl -p err -b --no-pager | tail -50\ndmesg -T | tail -50                ⚠️ OOM? disk errors? link flaps?\ndf -h; df -i                       ⚠️ both\nfree -m                            available, and swap activity\nss -tulpn                          expected listeners present?\nvmstat 1 5; iostat -xz 1 5         where's the saturation\nip -br a; ip r                     network sane?\ntimedatectl                        ⚠️ clock right? NTP synced?\nlast -n 20; journalctl -u sshd | tail   who's been on\n```\n\n### 19.3 Pre-change checklist\n- [ ] Do I know what this currently does, and have I captured it? (`systemctl cat`, backup the file)\n- [ ] Is there a rollback, and can I execute it without network access? (§6.3 → `sysadmin-systemd-storage-and-networking`)\n- [ ] Second SSH session open before touching sshd or the firewall? (§9.4 → `sysadmin-packages-boot-and-hardening`)\n- [ ] `sshd -t` \u002F `nft -c` \u002F `visudo` \u002F `mount -a` — syntax validated? (§5.3 → `sysadmin-systemd-storage-and-networking`, §9.4 → `sysadmin-packages-boot-and-hardening`)\n- [ ] `daemon-reload` after unit changes? (§4.1 → `sysadmin-systemd-storage-and-networking`)\n- [ ] Will config management revert this? (§11.2 → `sysadmin-observability-troubleshooting-and-operations`)\n- [ ] Is this change in source control? (§13 → `sysadmin-observability-troubleshooting-and-operations`)\n- [ ] Do I know how to tell whether it worked, and whether anything else broke?\n\n---\n\n## §20. Method\n\n**§1–§16 → `sysadmin-filesystem-permissions-and-processes`, `sysadmin-systemd-storage-and-networking`, `sysadmin-packages-boot-and-hardening`, `sysadmin-observability-troubleshooting-and-operations` and §19 rest on stable material** — POSIX file semantics, kernel subsystems,\nsystemd, TCP\u002FIP, and standard tooling — plus the reference works in §18, chiefly\n**Nemeth**, **Gregg's *Systems Performance*** for the observability method, and\n**Kerrisk** for syscall behaviour. ⚠️ **None of that needed web verification; the man\npages and those books are the authority and they change slowly.**\n\n**Two searches were run in August 2026**, confined to what genuinely perishes:\n**distribution lifecycle dates** and the **eBPF tooling landscape**.\n\n**Confidence.** **High** in §1–§16 → `sysadmin-filesystem-permissions-and-processes`, `sysadmin-systemd-storage-and-networking`, `sysadmin-packages-boot-and-hardening`, `sysadmin-observability-troubleshooting-and-operations` and §19 — these are mechanisms and commands I've stated\nwith their failure modes, and the failure modes are the valuable part. **High** in §10.4 → `sysadmin-observability-troubleshooting-and-operations`'s\neBPF characterization, which is consistent across sources and matches the primary tooling\ndocumentation.\n\n⚠️ **Lower confidence on §17's dates specifically, and I want to be direct about why.**\n**Most sources returned for lifecycle questions are EOL-tracking aggregator sites**, several\nof which are commercial services with an interest in urgency, and they occasionally\ndisagree at the margins. **The RHEL dates are consistent across several of them and align\nwith Red Hat's published phase structure; the Ubuntu dates follow the documented\n5-year LTS policy.** **But before you plan a migration on these, check Red Hat's own\nlifecycle page or Canonical's release-cycle page** — ⚠️ **vendors extend ELS windows, and\nRHEL 7's ELS extension to 2029 is exactly that kind of change.**\n\n⚠️ **And I have explicitly declined to assert one claim**: a source stated Linux 7.0\nshipped in 2026. **I could not corroborate it and nothing here depends on it.** Version\nnumbers in Linux are chosen arbitrarily rather than by semantic rule, so it is plausible —\nbut **an uncorroborated version claim is not something to put in a reference document\nunflagged.**\n","# Linux Server Administration: Anti-Patterns, Limits, Lifecycle Dates, and Command Reference\n\n> **Part 5 of 5** of the *Linux Server Administration* reference (plugin `linux-server-admin`), covering §15–§20. Sibling skills: `sysadmin-filesystem-permissions-and-processes` (§0–§3), `sysadmin-systemd-storage-and-networking` (§4–§6), `sysadmin-packages-boot-and-hardening` (§7–§9), `sysadmin-observability-troubleshooting-and-operations` (§10–§14). Section numbers are shared across the set; a reference written as §N → `skill` points into that sibling skill.\n>\n> **Currency:** The core — POSIX semantics, kernel subsystems, systemd, networking — is stable; distribution lifecycle dates and kernel LTS windows move. See §17 below for the dated table.\n\n> **How to read this.** Command-dense and operational. Assumes you can already use a\n> shell; this is about understanding the machine well enough to fix it under pressure.\n>\n> **⚠️ GOTCHA** boxes mark what causes outages or silent data loss.\n>\n> **The three mental models that make everything else make sense:**\n> 1. **⚠️ Everything is a file descriptor, and the kernel is the only thing that can\n>    actually do anything.** Userspace asks via syscalls. **When something \"doesn't work,\"\n>    the question is always: which syscall failed, and what errno?** — and `strace` will\n>    tell you (§12 → `sysadmin-observability-troubleshooting-and-operations`).\n> 2. **⚠️ State lives in four places and they disagree**: what's on disk, what's in the\n>    kernel's memory, what the running process loaded at start, and what your config\n>    management thinks. **Most confusing bugs are a disagreement between these** (§11.2 → `sysadmin-observability-troubleshooting-and-operations`).\n> 3. **⚠️ A server is a cache of your configuration management, not a pet.** If you cannot\n>    rebuild it from source control, you don't have a server — you have an artifact\n>    nobody understands (§15).\n\n---\n\n## §15. Anti-Patterns\n\n| Anti-pattern | Why |\n|---|---|\n| **Disabling SELinux** | ⚠️ **Fix the label. Two commands** (§9.2 → `sysadmin-packages-boot-and-hardening`) |\n| Editing vendor unit files in `\u002Fusr\u002Flib` | ⚠️ **Overwritten on update. Use `systemctl edit`** (§4.1 → `sysadmin-systemd-storage-and-networking`) |\n| Forgetting `daemon-reload` | Your edit isn't loaded (§4.1 → `sysadmin-systemd-storage-and-networking`) |\n| `Requires=` without `After=` | ⚠️ **Starts in parallel; fails** (§4.2 → `sysadmin-systemd-storage-and-networking`) |\n| `\u002Fdev\u002FsdX` in fstab | ⚠️ **Names aren't stable. Use UUID** (§5.3 → `sysadmin-systemd-storage-and-networking`) |\n| Rebooting without `mount -a` | ⚠️ **Stranded at emergency shell** (§5.3 → `sysadmin-systemd-storage-and-networking`) |\n| `kill -9` first | Skips flush and cleanup (§3 → `sysadmin-filesystem-permissions-and-processes`) |\n| Panicking about low \"free\" memory | ⚠️ **Read `available`. Cache is doing its job** (§10.2 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Enabling a firewall before allowing SSH | ⚠️ **Lockout** (§6.3 → `sysadmin-systemd-storage-and-networking`) |\n| Changing firewall rules with no rollback timer | Same (§6.3 → `sysadmin-systemd-storage-and-networking`) |\n| Password SSH auth | ⚠️ **Keys only is the biggest single win** (§9.4 → `sysadmin-packages-boot-and-hardening`) |\n| Reloading sshd without `sshd -t` | Console trip (§9.4 → `sysadmin-packages-boot-and-hardening`) |\n| `net.ipv4.tcp_tw_recycle` | ⚠️ **Removed from the kernel; broke NAT clients** (§6.4 → `sysadmin-systemd-storage-and-networking`) |\n| Ignoring `.rpmnew`\u002F`.dpkg-dist` | ⚠️ **Running old config plus a file you never read** (§7 → `sysadmin-packages-boot-and-hardening`) |\n| Using `strace` on a hot production process | ⚠️ **ptrace stops it on every syscall** (§10.4 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Treating LVM snapshots as backups | They fill and break (§5.2 → `sysadmin-systemd-storage-and-networking`) |\n| Untested backups | ⚠️ **Not backups** (§14 → `sysadmin-observability-troubleshooting-and-operations`) |\n| File-copying a running database | ⚠️ **Corrupt restore** (§14 → `sysadmin-observability-troubleshooting-and-operations`) |\n| `--privileged` containers | Kernel is shared (§12 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Alerting on CPU% instead of symptoms | Noise, then ignored alerts (§10.5 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Manual fixes with config management running | ⚠️ **Reverted in 30 minutes** (§11.2 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Theorizing before asking \"what changed?\" | ⚠️ **The highest-yield question** (§11.1 → `sysadmin-observability-troubleshooting-and-operations`) |\n| Volatile journal on a production box | ⚠️ **No logs from the crash** (§4.4 → `sysadmin-systemd-storage-and-networking`) |\n| Running as root because it's easier | Capabilities and systemd sandboxing exist (§2.2 → `sysadmin-filesystem-permissions-and-processes`, §4.3 → `sysadmin-systemd-storage-and-networking`) |\n| `ifconfig`\u002F`netstat` muscle memory | Deprecated; `ip`\u002F`ss` show more (§6.1 → `sysadmin-systemd-storage-and-networking`) |\n\n---\n\n## §16. Numbers and Limits\n\n```\nSIGNALS      TERM 15 · KILL 9 · HUP 1 · INT 2 · QUIT 3 · USR1 10 · USR2 12\nPERMISSIONS  r4 w2 x1 · setuid 4000 · setgid 2000 · sticky 1000 · umask 022\nEXIT CODES   0 ok · 1 general · 2 misuse · 126 not executable · 127 not found\n             ⚠️ 128+N = killed by signal N (137 = SIGKILL, 143 = SIGTERM)\nPORTS        \u003C1024 privileged (⚠️ or CAP_NET_BIND_SERVICE)\n             22 SSH · 25 SMTP · 53 DNS · 80\u002F443 HTTP(S) · 123 NTP · 3306 MySQL\n             5432 Postgres · 6379 Redis · 9090 Prometheus\nLIMITS       Default nofile often 1024 ⚠️ (far too low for servers — set 65535)\n             PID max default 4194304 on 64-bit\n             Ephemeral ports default 32768–60999\nLOAD         Divide by core count; ⚠️ includes D-state (I\u002FO), not just CPU\nFS           ext4 max file 16 TiB · XFS ⚠️ cannot shrink · inode exhaustion is separate\nTIME         ⚠️ Always UTC on servers. `timedatectl set-timezone UTC`\n```\n\n---\n\n## §17. Lifecycle Dates — verified August 2026\n\n**⚠️ Lifecycle dates are the one genuinely perishable thing in this document. Verify\nagainst the vendor before planning a migration.**\n\n| Distribution | Status as of August 2026 |\n|---|---|\n| **RHEL 10** | Released **20 May 2025**. Full support to ~**May 2030**, maintenance to ~**May 2035**. Latest minor **10.2** (May 2026) |\n| **RHEL 9** | Full support to **31 May 2027**, maintenance to **31 May 2032** |\n| **RHEL 8** | ⚠️ **Full support ended 31 May 2024**; 8.10 is the final minor, maintenance to **31 May 2029** |\n| **RHEL 7** | ⚠️ **Maintenance ended 30 June 2024**; ELS extended to **31 May 2029** |\n| **Ubuntu 26.04 LTS** | Current LTS, released **April 2026**, standard support to **30 April 2031** |\n| **Ubuntu 24.04 LTS** | Supported to **31 May 2029** |\n| **Ubuntu 25.10** | ⚠️ **EOL 1 July 2026** — interim releases get 9 months |\n\n**⚠️ RHEL's lifecycle is unusually complex** — overlapping **Full Support → Maintenance\nSupport → Extended Life → ELS** phases, each meaning something different about which\npatches you actually receive. **\"Is it EOL?\" is the wrong question; \"which phase, and does\nthat phase still ship security errata?\" is the right one.** **Ubuntu LTS is 5 years\nstandard, extendable via Pro\u002FESM.**\n\n**⚠️ Kernel LTS windows have been volatile**: historically six years, **cut to a 2-year\ndefault in 2023** as maintainers cited burnout, then **partially extended again in early\n2026 after industry pushback.** ⚠️ **But upstream kernel.org lifecycle usually isn't what\ngoverns you — your distribution's backporting is.** **A RHEL 9 kernel gets security fixes\nlong after the upstream branch is dead.**\n\n⚠️ **One claim I encountered and am flagging rather than repeating as fact**: a source\nasserts a **Linux 7.0** release in 2026 following the 6.x series. **I could not corroborate\nthis against kernel.org and have not built anything in this document on it.** Version\nnumbering in Linux is arbitrary by policy, so it's plausible — **verify before quoting.**\n\n**eBPF tooling** (§10.4 → `sysadmin-observability-troubleshooting-and-operations`) is mature and stable in interface: **BCC** ships **80+ ready-made\ntools**, **bpftrace** is the one-liner language, and **libbpf + CO-RE** is the production\npath for custom programs. ⚠️ **This is now baseline knowledge rather than specialist\ntooling.**\n\n---\n\n## §18. Books\n\n| Author | Work | Why |\n|---|---|---|\n| **Nemeth et al.** | ***UNIX and Linux System Administration Handbook*** | ⚠️ **The one book. Comprehensive, opinionated, current** |\n| **Gregg** | ***Systems Performance*** | ⚠️ **§10 → `sysadmin-observability-troubleshooting-and-operations`'s method. The definitive performance text** |\n| **Gregg** | ***BPF Performance Tools*** | §10.4 → `sysadmin-observability-troubleshooting-and-operations`, from the person who built most of them |\n| **Love** | *Linux System Programming* | What syscalls actually do |\n| **Bovet & Cesati** | *Understanding the Linux Kernel* | Deeper, older, still clarifying |\n| **Kerrisk** | ***The Linux Programming Interface*** | ⚠️ **The syscall reference. Enormous and authoritative** |\n| **Beyer et al.** | ***Site Reliability Engineering*** | ⚠️ **Free online. The operational philosophy** |\n| **Limoncelli et al.** | *The Practice of System and Network Administration* | The process side |\n| **Barrett et al.** | *SSH: The Definitive Guide* | §9.4 → `sysadmin-packages-boot-and-hardening` in depth |\n| **Ward** | *How Linux Works* | ⚠️ **The best entry point if the model isn't solid yet** |\n\n**Primary and practical**: **`man` pages** (⚠️ **`man 7 capabilities`, `man 5 systemd.exec`\nand `man 7 signal` in particular — better than most blog posts**), **`systemd.io`**,\n**Arch Wiki** (⚠️ **the best Linux documentation on the internet regardless of your\ndistro**), **Red Hat and Ubuntu documentation**, **`brendangregg.com`**, **`ebpf.io`**,\n**`endoflife.date`** for §17.\n\n---\n\n## §19. Command Reference\n\n### 19.1 The fifteen that carry most of the load\n```\nsystemctl status|list-units --failed|cat|edit      service truth\njournalctl -u X -f | -p err -b | -b -1             log truth\nss -tulpn                                          what's listening\nip -br a · ip r get IP                             network truth\nlsblk -f · df -h · df -i                           storage truth\ndu -xh --max-depth=1 \u002F                             where did the space go\nlsof +L1                                           ⚠️ deleted-but-open files\nfree -m                                            ⚠️ read \"available\"\nvmstat 1 · iostat -xz 1 · mpstat -P ALL 1          saturation\ndmesg -T | tail -50                                ⚠️ OOM, hardware, resets\nps auxf · pstree -p                                process tree\nstrace -f -p PID  \u002F  execsnoop, opensnoop          ⚠️ what is it actually doing\nausearch -m avc -ts recent                         SELinux denials\nnft list ruleset                                   firewall truth\nfind \u002Fetc -name '*.rpmnew' -o -name '*.dpkg-dist'  ⚠️ config drift after updates\n```\n\n### 19.2 First five minutes on an unfamiliar sick box\n```\nuptime; w                          load, who's on, how long up\nsystemctl list-units --failed      ⚠️ start here\njournalctl -p err -b --no-pager | tail -50\ndmesg -T | tail -50                ⚠️ OOM? disk errors? link flaps?\ndf -h; df -i                       ⚠️ both\nfree -m                            available, and swap activity\nss -tulpn                          expected listeners present?\nvmstat 1 5; iostat -xz 1 5         where's the saturation\nip -br a; ip r                     network sane?\ntimedatectl                        ⚠️ clock right? NTP synced?\nlast -n 20; journalctl -u sshd | tail   who's been on\n```\n\n### 19.3 Pre-change checklist\n- [ ] Do I know what this currently does, and have I captured it? (`systemctl cat`, backup the file)\n- [ ] Is there a rollback, and can I execute it without network access? (§6.3 → `sysadmin-systemd-storage-and-networking`)\n- [ ] Second SSH session open before touching sshd or the firewall? (§9.4 → `sysadmin-packages-boot-and-hardening`)\n- [ ] `sshd -t` \u002F `nft -c` \u002F `visudo` \u002F `mount -a` — syntax validated? (§5.3 → `sysadmin-systemd-storage-and-networking`, §9.4 → `sysadmin-packages-boot-and-hardening`)\n- [ ] `daemon-reload` after unit changes? (§4.1 → `sysadmin-systemd-storage-and-networking`)\n- [ ] Will config management revert this? (§11.2 → `sysadmin-observability-troubleshooting-and-operations`)\n- [ ] Is this change in source control? (§13 → `sysadmin-observability-troubleshooting-and-operations`)\n- [ ] Do I know how to tell whether it worked, and whether anything else broke?\n\n---\n\n## §20. Method\n\n**§1–§16 → `sysadmin-filesystem-permissions-and-processes`, `sysadmin-systemd-storage-and-networking`, `sysadmin-packages-boot-and-hardening`, `sysadmin-observability-troubleshooting-and-operations` and §19 rest on stable material** — POSIX file semantics, kernel subsystems,\nsystemd, TCP\u002FIP, and standard tooling — plus the reference works in §18, chiefly\n**Nemeth**, **Gregg's *Systems Performance*** for the observability method, and\n**Kerrisk** for syscall behaviour. ⚠️ **None of that needed web verification; the man\npages and those books are the authority and they change slowly.**\n\n**Two searches were run in August 2026**, confined to what genuinely perishes:\n**distribution lifecycle dates** and the **eBPF tooling landscape**.\n\n**Confidence.** **High** in §1–§16 → `sysadmin-filesystem-permissions-and-processes`, `sysadmin-systemd-storage-and-networking`, `sysadmin-packages-boot-and-hardening`, `sysadmin-observability-troubleshooting-and-operations` and §19 — these are mechanisms and commands I've stated\nwith their failure modes, and the failure modes are the valuable part. **High** in §10.4 → `sysadmin-observability-troubleshooting-and-operations`'s\neBPF characterization, which is consistent across sources and matches the primary tooling\ndocumentation.\n\n⚠️ **Lower confidence on §17's dates specifically, and I want to be direct about why.**\n**Most sources returned for lifecycle questions are EOL-tracking aggregator sites**, several\nof which are commercial services with an interest in urgency, and they occasionally\ndisagree at the margins. **The RHEL dates are consistent across several of them and align\nwith Red Hat's published phase structure; the Ubuntu dates follow the documented\n5-year LTS policy.** **But before you plan a migration on these, check Red Hat's own\nlifecycle page or Canonical's release-cycle page** — ⚠️ **vendors extend ELS windows, and\nRHEL 7's ELS extension to 2029 is exactly that kind of change.**\n\n⚠️ **And I have explicitly declined to assert one claim**: a source stated Linux 7.0\nshipped in 2026. **I could not corroborate it and nothing here depends on it.** Version\nnumbers in Linux are chosen arbitrarily rather than by semantic rule, so it is plausible —\nbut **an uncorroborated version claim is not something to put in a reference document\nunflagged.**\n",{"name":5,"description":7},"develop","ae32736a1aabddabca5d2c96d665aa0ebc7d8700","src\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Flinux-server-admin\u002Fskills\u002Fsysadmin-reference",3,"https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey","https:\u002F\u002Fthe-vibey-project.github.io\u002Fvibey\u002F","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project","https:\u002F\u002Fvibewithadam.matthewsteinberger.com","freedom for software engineers","2026-11-15 05:47:42",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add the-vibey-project\u002Fvibey --skill sysadmin-reference",{"tool":40,"command":41},"bunx","bunx skills add the-vibey-project\u002Fvibey --skill sysadmin-reference",{"tool":43,"command":44},"pnpm","pnpm dlx skills add the-vibey-project\u002Fvibey --skill sysadmin-reference","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Flinux-server-admin\u002Fskills\u002Fsysadmin-reference\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7AT1FQJAE1FQYAMDTF490Y4","white-paper-writing","Use when writing white papers, technical reports, policy documents, thought leadership pieces, or any long-form authoritative document. Triggers on requests to write, structure, outline, or review white papers, technical reports, position papers, policy briefs, or evidence-driven arguments. Also use for B2B content marketing strategy, technical documentation requiring authority, academic-style reports, or any document that must educate while persuading. Use when someone asks \"how should I structure this\" for a long-form document.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fwhite-paper-writing\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7AT16BJRJJKK2MASXRZS76G","prose-technical-mechanics","Use when editing or writing prose at a technical\u002Fmechanical level: choosing between Anglo-Saxon and Latinate diction, placing information in topic vs stress positions, writing periodic vs cumulative sentences, handling sentence rhythm, punctuation as logic, transitions, paragraph structure, or phonesthetics. Use when someone wants to understand WHY prose works or doesn't, not just surface-level style advice. Triggers on word choice, sentence structure, emphasis, rhythm, diction, or any deep writing mechanics question.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-technical-mechanics\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7AT0W9HT0ZZ9Y287NW99MR3","prose-mechanics","Use when writing, editing, or analyzing prose style; when trying to avoid generic AI-sounding writing; when applying specific prose styles such as journalistic, academic, narrative, KJV biblical, Hemingway plain, Latinate\u002FJamesian, Orwellian, Augustan, Victorian, Early Modern (Bacon, Browne, Milton), or free indirect discourse; or when coaching someone on writing voice and mechanics. Triggers on any request to improve, analyze, or write in a specific prose style, to fix \"AI-sounding\" writing, to make prose more vivid or concrete, to vary sentence rhythm, or to understand how a particular writer achieves their effects.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fprose-mechanics\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7AT0KR635JX66X2X6F3E2CP","narrative-structure","Use when structuring stories, pitches, presentations, white papers, or any persuasive narrative; analyzing the hero's journey in fiction or non-fiction; applying StoryBrand for business communication; designing narrative arcs for thought leadership; or understanding Vogler, Snyder, Propp, or Campbell frameworks. Triggers on any narrative structure, storytelling, pitch structure, StoryBrand, hero's journey, three-act structure, Freytag, Save the Cat, narrative arc, or \"how should I structure this story\u002Fpitch\u002Fpresentation\" request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fnarrative-structure\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AT0AKGW09NKKZDYBT8VRDE","legal-brief-writing","Use when writing legal briefs, motions, or any court filing; when analyzing judicial cognition and persuasion; when applying elite brief-writing techniques from Roberts, Clement, Kagan, Garner; or when structuring legal arguments for maximum persuasion. Also use for autistic\u002Fneurodivergent advocates who need to understand how their natural communication style maps to elite legal advocacy. Triggers on any legal writing, brief drafting, motion preparation, or legal argument structuring request.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Flegal-brief-writing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7AT00VWPS4Q8B5VEMXX9NQT","journal-publishability-criteria","Use whenever a research paper, article or preprint is being written, revised, reviewed or published, and specifically before every publication of docs\u002Fpaper.md. Covers what legitimate journals actually gate on, in order of gating — the editor's desk screen (scope, novelty, package problems), what reviewers judge (methodological soundness, claims the evidence can carry, statistical and qualitative reporting), EQUATOR reporting guidelines, the ICMJE authorship criteria, COPE's view of text recycling, the near-universal generative-AI policy (no AI author, disclosure, author responsibility), TOP 2025 transparency standards, how to verify a journal is legitimate, submitting without an institution, and a pre-submission checklist. Triggers on requests to evaluate, review, prepare or submit a paper, to judge publishability, to write a declarations or data-availability section, to disclose AI use, or to check a journal.","https:\u002F\u002Fgithub.com\u002Fthe-vibey-project\u002Fvibey\u002Fblob\u002Fdevelop\u002Fsrc\u002Fvibey_tools\u002Fskills\u002Fplugins\u002Fwriting-craft\u002Fskills\u002Fjournal-publishability-criteria\u002FSKILL.md",[],[]]