<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>System Administration on MeerStory</title><link>https://linux.meerstory.com/categories/system-administration/</link><description>Recent content in System Administration on MeerStory</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 17 Oct 2026 02:41:24 +0900</lastBuildDate><atom:link href="https://linux.meerstory.com/categories/system-administration/index.xml" rel="self" type="application/rss+xml"/><item><title>Tuning Linux OOM Killer Scores and Protecting Tasks with choom</title><link>https://linux.meerstory.com/ubuntu/20261017_024039_99/</link><pubDate>Sat, 17 Oct 2026 02:41:24 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261017_024039_99/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>When physical memory runs dangerously low, the Linux kernel invokes its Out of Memory (OOM) Killer to sacrifice selected processes and prevent a total system crash. This guide explores &lt;code>choom&lt;/code>, a focused utility from the &lt;code>util-linux&lt;/code> suite designed to query and fine-tune process termination priorities. Through practical terminal exercises, you will master inspecting live OOM scores, deprioritizing disposable workloads, and shielding mission-critical system daemons from sudden eviction.&lt;/p>
&lt;h2 id="1-understanding-choom-and-verifying-package-prerequisites">1. Understanding choom and Verifying Package Prerequisites&lt;/h2>
&lt;p>Before tuning process survival scores, ensure that the requisite utilities from &lt;code>util-linux&lt;/code> and &lt;code>procps&lt;/code> are present on your host.&lt;/p></description></item><item><title>Mastering the Linux top Command</title><link>https://linux.meerstory.com/ubuntu/20261009_014504_16/</link><pubDate>Fri, 09 Oct 2026 01:45:24 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261009_014504_16/</guid><description>&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>Keeping a close eye on system health is a fundamental responsibility for any systems engineer or DevOps practitioner, and the classic &lt;code>top&lt;/code> utility remains one of the fastest, most dependable tools in the Linux diagnostic toolkit. This tutorial unpacks the standard metrics reported by &lt;code>top&lt;/code>, demonstrates indispensable command-line switches for production troubleshooting, and provides practical examples for tracking system bottlenecks effectively.&lt;/p>
&lt;h2 id="standard-execution--capturing-automated-snapshots-with-batch-mode">Standard Execution &amp;amp; Capturing Automated Snapshots with Batch Mode&lt;/h2>
&lt;p>At its core, &lt;code>top&lt;/code> delivers a live, updating view of processor utilization, physical and virtual memory allocation, and task-level execution states across the operating system.&lt;br>
While its default interactive interface is great for manual inspection, automating log captures or shell scripts requires non-interactive execution. Pairing batch mode (&lt;code>-b&lt;/code>) with an iteration counter (&lt;code>-n 1&lt;/code>) turns the dynamic dashboard into standard text output, which we can pipe directly into &lt;code>head -n 15&lt;/code> for a clean snapshot of overall load averages and top resource consumers.&lt;br>
⚙️ [Essential CLI Flags]&lt;/p></description></item><item><title>Essential Practical ps Command Options and Workflows</title><link>https://linux.meerstory.com/ubuntu/20261009_013732_15/</link><pubDate>Fri, 09 Oct 2026 01:37:53 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261009_013732_15/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>Gaining clear visibility into active system tasks represents the bedrock of day-to-day Linux administration and performance troubleshooting. This handbook breaks down the architecture and command-line mechanics of &lt;code>ps&lt;/code>—the cornerstone utility for auditing running processes. Beyond untangling the historic divergence between &lt;code>ps aux&lt;/code> and &lt;code>ps -ef&lt;/code>, we will examine actionable filtering workflows, resource-ranking pipelines, and practical terminal diagnostics.&lt;/p>
&lt;h2 id="1-inspecting-shell-tasks-and-fundamentals-of-the-ps-utility">1. Inspecting Shell Tasks and Fundamentals of the ps Utility&lt;/h2>
&lt;p>The &lt;code>ps&lt;/code> utility captures an instantaneous snapshot of current operating system tasks. Executing it in isolation queries only the processes bound directly to your active shell session. The default table reports four primary data points: the unique process ID (&lt;code>PID&lt;/code>), the attached controlling terminal device (&lt;code>TTY&lt;/code>), accumulated CPU runtime (&lt;code>TIME&lt;/code>), and the executable binary name (&lt;code>CMD&lt;/code>).&lt;/p></description></item><item><title>Mastering dpkg in Ubuntu</title><link>https://linux.meerstory.com/ubuntu/20261009_013027_14/</link><pubDate>Fri, 09 Oct 2026 01:31:03 +0900</pubDate><guid>https://linux.meerstory.com/ubuntu/20261009_013027_14/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>At the heart of software management on Debian and Ubuntu systems lies &lt;code>dpkg&lt;/code>, the foundational low-level engine responsible for handling &lt;code>.deb&lt;/code> archives. While high-level frontends like &lt;code>apt&lt;/code> manage remote repositories and dependency trees automatically, mastering &lt;code>dpkg&lt;/code> provides administrators with granular control over individual package files. This hands-on tutorial walks through the complete package lifecycle: staging local packages, inspecting archives prior to installation, querying the local database, tracing binary ownership, performing clean uninstalls, and repairing broken dependency states.&lt;/p></description></item></channel></rss>