{"id":17364,"date":"2026-01-28T17:15:28","date_gmt":"2026-01-28T11:45:28","guid":{"rendered":"https:\/\/www.youstable.com\/blog\/?p=17364"},"modified":"2026-01-28T17:15:30","modified_gmt":"2026-01-28T11:45:30","slug":"top-command-in-linux","status":"publish","type":"post","link":"https:\/\/www.youstable.com\/blog\/top-command-in-linux","title":{"rendered":"Top Command in Linux Explained With Examples in 2026"},"content":{"rendered":"\n<p><strong>The top command in Linux is <\/strong>a real time process monitor that displays CPU, memory, load average, and per-process usage. It helps you find resource hungry tasks, sort by CPU or memory, kill or renice processes, and troubleshoot performance issues. <\/p>\n\n\n\n<p>Use top for live monitoring, or batch mode to log snapshots for later analysis. If you manage servers or develop on Linux, learning the top command is essential. <\/p>\n\n\n\n<p>This guide explains the top command in Linux with examples, shortcuts, and practical workflows used in production environments, so you can quickly diagnose high CPU, memory leaks, load spikes, and slow applications.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"what-is-the-top-command-in-linux\">What is the Top Command in Linux?<\/h2>\n\n\n\n<p><strong>The Linux top command shows a<\/strong> live, continuously updating view of system performance. <\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1280\" height=\"720\" src=\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/01\/What-is-the-Top-Command-in-Linux.jpg\" alt=\"Top Command in Linux\" class=\"wp-image-17638\" srcset=\"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/01\/What-is-the-Top-Command-in-Linux.jpg 1280w, https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/01\/What-is-the-Top-Command-in-Linux-150x84.jpg 150w\" sizes=\"auto, (max-width: 1280px) 100vw, 1280px\" \/><\/figure>\n\n\n\n<p>It lists running processes and key metrics like CPU, memory, swap, and system load. You can sort, filter, kill, or renice processes directly within the interface. It\u2019s installed by default on most distributions <strong>(Ubuntu, Debian, CentOS, Rocky, Fedora)<\/strong>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"how-to-read-top-output-header-breakdown\">How to Read Top Output (Header Breakdown)<\/h2>\n\n\n\n<p>When you run top, you\u2019ll first see the summary header, then the process list. Understanding the header saves time and helps you act confidently.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"uptime-and-load-average\"><strong>Uptime and Load Average<\/strong><\/h3>\n\n\n\n<p>The first line shows current time, how long the system has been up, logged in users, and load average over 1, 5, and 15 minutes. Load average roughly represents runnable processes. On a 4-core CPU, a sustained load of 4.00 means full utilization.<\/p>\n\n\n\n<p>Rule of thumb: If the 15 minute load average consistently exceeds your CPU core count, investigate CPU, I\/O wait, or lock contention.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"tasks-and-process-states\">Tasks and Process States<\/h3>\n\n\n\n<p>The tasks line shows the number of processes and their states: running, sleeping, stopped, and zombie. Many zombies indicate improper child process handling. Many sleeping tasks are normal on servers.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"cpu-utilization\">CPU Utilization<\/h3>\n\n\n\n<p>The CPU line breaks down usage by type: us (user), sy (system), ni (nice), id (idle), wa (I\/O wait), hi\/si (hardware\/software interrupts), st (steal in virtualized environments). High wa suggests disk or network bottlenecks; high st indicates host level contention in VPS environments.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"memory-and-swap\">Memory and Swap<\/h3>\n\n\n\n<p>Memory lines show total, used, free, and buffers\/cache. On modern Linux, \u201cused\u201d includes page cache; focus on available memory. Frequent swap in\/out plus high wa means memory pressure. If swap is heavily used, find memory hungry processes or leaks.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"key-process-columns-explained\">Key Process Columns Explained<\/h3>\n\n\n\n<p>By default, top shows these important columns:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>PID\/USER: <\/strong>Process ID and owner.<\/li>\n\n\n\n<li><strong>PR\/NI:<\/strong> Priority and nice value (lower PR runs first; higher NI means \u201cnicer,\u201d i.e., lower priority).<\/li>\n\n\n\n<li><strong>VIRT\/RES\/SHR:<\/strong> Virtual, resident, and shared memory.<\/li>\n\n\n\n<li><strong>S: <\/strong>Process state (R running, S sleeping, D uninterruptible, T stopped, Z zombie).<\/li>\n\n\n\n<li><strong>%CPU\/%MEM:<\/strong> CPU and memory share per process.<\/li>\n\n\n\n<li><strong>TIME+:<\/strong> Cumulative CPU time used.<\/li>\n\n\n\n<li><strong>COMMAND:<\/strong> Process name or full command line (toggle with c).<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"basic-usage-top-command-examples\">Basic Usage: Top Command Examples<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"launch-top-and-update-interval\">Launch Top and Update Interval<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>top\ntop -d 1      # refresh every 1 second\ntop -d 0.5    # faster refresh (may increase CPU usage)<\/code><\/pre>\n\n\n\n<p>Use -d to control delay between updates. For servers, 1\u20133 seconds is usually sufficient.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"sort-by-cpu-or-memory\">Sort by CPU or Memory<\/h3>\n\n\n\n<p>Interactively press P to sort by %CPU, M for %MEM, N for PID, or T for TIME+. You can toggle reverse order with R.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Start top sorted by memory (procps-ng supports -o)\ntop -o %MEM\n\n# Start top sorted by CPU\ntop -o %CPU<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"show-per-cpu-core-usage\">Show Per-CPU\/Core Usage<\/h3>\n\n\n\n<p>Press 1 to toggle per-core CPU lines. This helps identify single threaded bottlenecks when one core is saturated while total CPU looks fine.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"filter-by-user-or-pid\">Filter by User or PID<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Only show processes for a specific user\ntop -u ubuntu\n\n# Monitor selected PIDs only\ntop -p 1234,2345,3456<\/code><\/pre>\n\n\n\n<p>This is handy on multi tenant servers, CI runners, or application hosts with multiple services.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"show-threads-and-full-commands\">Show Threads and Full Commands<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Show threads for each process\ntop -H\n\n# Toggle full command line while running top\nc<\/code><\/pre>\n\n\n\n<p>Thread view (-H) is useful for debugging multi threaded apps (e.g., Java, Nginx worker threads, PHP-FPM pools).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"kill-or-renice-a-process-from-top\">Kill or Renice a Process from Top<\/h3>\n\n\n\n<p>Act carefully on production servers. Try graceful signals first.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Inside top:\nk            # kill prompt\n1234         # enter PID\n15           # SIGTERM (try first). Use 9 for SIGKILL if it won't exit.\n\nr            # renice prompt\n1234         # PID\n10           # new nice value (higher = lower priority)<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"batch-mode-for-logging-and-automation\">Batch Mode for Logging and Automation<\/h3>\n\n\n\n<p>Batch mode doesn\u2019t require a terminal and is perfect for scripts or <a href=\"https:\/\/www.youstable.com\/blog\/install-cron-jobs-on-linux\/\">cron jobs<\/a>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># One snapshot\ntop -b -n 1 &gt; \/tmp\/top-snapshot.txt\n\n# 5 snapshots, 2 seconds apart\ntop -b -d 2 -n 5 | tee \/tmp\/top-log.txt<\/code><\/pre>\n\n\n\n<h3 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"reduce-noise-and-enable-color\">Reduce Noise and Enable Color<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code># Ignore idle\/zombie processes\ni\n\n# Toggle color\/mono (if supported)\nz<\/code><\/pre>\n\n\n\n<p>Press h or ? inside top to view help and all available interactive commands on your system.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"interactive-shortcuts-youll-use-daily\">Interactive Shortcuts You\u2019ll Use Daily<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>P \/ M \/ N \/ T: <\/strong>Sort by CPU, memory, PID, or time.<\/li>\n\n\n\n<li><strong>R: <\/strong>Reverse sort order.<\/li>\n\n\n\n<li><strong>1: <\/strong>Toggle per-core CPU view.<\/li>\n\n\n\n<li><strong>c:<\/strong> Show full command line.<\/li>\n\n\n\n<li><strong>i:<\/strong> Hide idle processes.<\/li>\n\n\n\n<li><strong>k:<\/strong> Kill; r: Renice.<\/li>\n\n\n\n<li><strong>f:<\/strong> Field manager; use s inside to set sort field, space to toggle columns, Enter to apply.<\/li>\n\n\n\n<li><strong>z:<\/strong> Color mode; b: bold\/bright (varies by build).<\/li>\n\n\n\n<li><strong>t \/ m:<\/strong> Toggle CPU and memory summary styles.<\/li>\n\n\n\n<li><strong>h or ?:<\/strong> Help; q: Quit.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"real-world-troubleshooting-with-top-scenarios\">Real World Troubleshooting with Top (Scenarios)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>High CPU on web server:<\/strong> Press P to sort by CPU. Press 1 to check a single core pinned at 100%. If PHP-FPM or a Java thread dominates, capture a stack trace or temporarily renice; investigate application hot paths.<\/li>\n\n\n\n<li><strong>Memory leak suspicion:<\/strong> Press M to sort by %MEM; watch RES column over time. Use top -H to see thread level behavior. Correlate with swap usage and OOM events in dmesg or system logs.<\/li>\n\n\n\n<li><strong>Load average spikes: <\/strong>Compare us\/sy\/wa fields. High wa suggests disk\/db latency; investigate with iostat, iotop, or database slow logs.<\/li>\n\n\n\n<li><strong>Zombie processes:<\/strong> Check the Tasks line. Persistent Z state implies a parent not reaping children, inspect parent process and application code.<\/li>\n\n\n\n<li><strong>Multi tenant VPS: <\/strong>Run top -u user or top -p with specific PIDs to focus on a client or service. Use batch mode to create incident timelines during traffic surges.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"interpreting-metrics-and-when-to-act\">Interpreting Metrics and When to Act<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Load average:<\/strong> Investigate if 15\u2011minute load &gt; core count for sustained periods.<\/li>\n\n\n\n<li><strong>CPU us vs sy:<\/strong> High sy (kernel time) may indicate heavy networking, system calls, or context switching.<\/li>\n\n\n\n<li><strong>I\/O wait (wa):<\/strong> &gt;10\u201320% sustained is a red flag for storage bottlenecks.<\/li>\n\n\n\n<li><strong>Memory pressure:<\/strong> Growing RES on a process, swap-in\/out, and low available memory. Consider tuning, fixing leaks, or scaling RAM.<\/li>\n\n\n\n<li><strong>Steal time (st): <\/strong>On VPS, high st implies noisy neighbors or under provisioned host, consider migrating or upgrading.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"top-vs-htop-vs-other-monitoring-tools\">Top vs Htop vs Other Monitoring Tools<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>top:<\/strong> Ubiquitous, lightweight, script friendly (batch mode). Interface is spartan but powerful.<\/li>\n\n\n\n<li><strong>htop:<\/strong> More visual UI, easier scrolling, mouse support, tree view, quick filters. Not always preinstalled.<\/li>\n\n\n\n<li><strong>glances\/bpytop:<\/strong> Rich dashboards with multiple subsystems (CPU, disk, network). Heavier dependencies.<\/li>\n\n\n\n<li><strong>ps, vmstat, free, iostat, sar:<\/strong> Great for snapshots, historical data, and narrow diagnostics.<\/li>\n<\/ul>\n\n\n\n<p>Learn top first for universality, then add htop for comfort and glances for dashboards.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"best-practices-for-servers-from-12plus-years-in-hosting\">Best Practices for Servers (From 12+ Years in Hosting)<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Set a sensible refresh: <\/strong>-d 1\u20133 to minimize overhead while keeping visibility.<\/li>\n\n\n\n<li><strong>Prefer graceful actions: <\/strong>Try SIGTERM (15) before SIGKILL (9) to avoid data loss.<\/li>\n\n\n\n<li><strong>Combine tools: <\/strong>Use top to spot the issue, then drill down with strace, perf, iotop, ss, or db slow logs.<\/li>\n\n\n\n<li><strong>Monitor trends:<\/strong> Use top -b with cron during incidents to capture snapshots for postmortems.<\/li>\n\n\n\n<li><strong>Harden production:<\/strong> Limit dangerous interactive actions to privileged users; log change windows.<\/li>\n\n\n\n<li><strong>Scale before pain:<\/strong> If load and memory trend upward with normal traffic, plan upgrades or horizontal scaling.<\/li>\n<\/ul>\n\n\n\n<p>Running apps on VPS or cloud? YouStable\u2019s optimized hosting and managed servers include proactive monitoring and right sized resources, so your top output stays calm even during peak hours. When you need more CPU, RAM, or faster NVMe storage, scaling up is seamless.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"advanced-top-tips-and-customization\">Advanced Top Tips and Customization<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Persist your layout:<\/strong> Customize fields (f), sort key (s inside field manager), colors (z), then write settings with W (uppercase) to save to ~\/.toprc.<\/li>\n\n\n\n<li><strong>Wide output:<\/strong> On newer versions, -w adjusts width; try top -w 512 to reduce line wrapping in small terminals.<\/li>\n\n\n\n<li><strong>Filter in-session:<\/strong> Use field manager (f) to hide noise columns; focus on PID, USER, %CPU, %MEM, RES, TIME+, COMMAND.<\/li>\n\n\n\n<li><strong>Cumulative time:<\/strong> Toggle cumulative mode to include dead children\u2019s CPU time; helpful for services that spawn workers (varies by build).<\/li>\n\n\n\n<li><strong>Thread vs process view: <\/strong>Switch with -H or toggle inside top when analyzing multi threaded CPU spikes.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"common-top-command-examples-copy-paste\"><strong>Common Top Command Examples (Copy\/Paste)<\/strong><\/h2>\n\n\n\n<pre class=\"wp-block-code\"><code># Start top with 2s delay, sorted by CPU\ntop -d 2 -o %CPU\n\n# Focus on a single service user\ntop -u www-data\n\n# Investigate a specific app by PIDs\ntop -p 1122,2244,5566\n\n# Batch log 10 samples for incident review\ntop -b -d 3 -n 10 &gt; \/var\/log\/top-incident.log\n\n# Show threads and full command lines\ntop -H -c<\/code><\/pre>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"troubleshooting-checklist-using-top\">Troubleshooting Checklist Using Top<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Is load average above core count?<\/strong> Check which processes are on top and per-core usage (1).<\/li>\n\n\n\n<li><strong>Is I\/O wait high?<\/strong> Correlate with disk metrics and database activity.<\/li>\n\n\n\n<li><strong>Is memory tight?<\/strong> Sort by M, look at RES and swap; confirm available memory.<\/li>\n\n\n\n<li><strong>Is one service hogging CPU?<\/strong> Consider renice, scaling, or code level optimization.<\/li>\n\n\n\n<li><strong>Do you see zombies?<\/strong> Fix parent process handling and review service supervision configs.<\/li>\n<\/ul>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"faqs\">FAQs<\/h2>\n\n\n<div id=\"rank-math-faq\" class=\"rank-math-block\">\n<div class=\"rank-math-list \">\n<div id=\"faq-question-1768387047593\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"what-does-the-top-command-do-in-linux\">What does the top command do in Linux?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>top provides a live, updating view of running processes, CPU and memory usage, load averages, and system state. It lets you sort, filter, kill, and renice processes directly from the interface, making it a go to tool for performance monitoring and troubleshooting.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768387058294\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"how-do-i-sort-by-memory-or-cpu-in-top\">How do I sort by memory or CPU in top?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Press M to sort by memory and P to sort by CPU. You can also start top sorted by a field using -o, for example: top -o %MEM or top -o %CPU on most Linux distributions that use procps-ng.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768387066477\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"how-do-i-kill-a-process-in-top-safely\">How do I kill a process in top safely?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Inside top, press k, enter the PID, and send signal 15 (SIGTERM) first for a graceful stop. If the process won\u2019t exit, use 9 (SIGKILL) as a last resort. On production servers, confirm the process owner and impact before killing.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768387075067\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"what-is-the-difference-between-top-and-htop\">What is the difference between top and htop?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>top is minimal and installed by default, ideal for scripts and remote servers. htop provides a friendlier interface with color bars, mouse support, easier filtering, and process tree views. Learn top first for universality, then add htop for convenience.<\/p>\n\n<\/div>\n<\/div>\n<div id=\"faq-question-1768387082539\" class=\"rank-math-list-item\">\n<h3 class=\"rank-math-question \" class=\"rank-math-question \" id=\"why-is-my-load-average-high-even-when-cpu-isnt-100percent\">Why is my load average high even when CPU isn\u2019t 100%?<\/h3>\n<div class=\"rank-math-answer \">\n\n<p>Load average includes processes waiting on CPU and I\/O. High I\/O wait (wa) or lock contention can increase load with moderate CPU usage. In top, check wa on the CPU line; investigate disks, databases, or network saturation accordingly.<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity is-style-wide\"\/>\n\n\n\n<h2 class=\"wp-block-heading\" class=\"wp-block-heading\" id=\"conclusion\">Conclusion<\/h2>\n\n\n\n<p>The top command in Linux is a cornerstone of system monitoring. Master the header, learn the key shortcuts, and practice with realistic scenarios. If your business relies on stable, fast servers, YouStable\u2019s optimized hosting and managed stacks help ensure your top output stays green even under heavy traffic.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>The top command in Linux is a real time process monitor that displays CPU, memory, load average, and per-process usage. [&hellip;]<\/p>\n","protected":false},"author":21,"featured_media":18184,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[350],"tags":[],"class_list":["post-17364","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-knowledgebase"],"acf":[],"featured_image_src":"https:\/\/www.youstable.com\/blog\/wp-content\/uploads\/2026\/01\/Top-Command-in-Linux-Explained-With-Examples.jpg","author_info":{"display_name":"Sanjeet Chauhan","author_link":"https:\/\/www.youstable.com\/blog\/author\/sanjeet"},"_links":{"self":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/17364","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/users\/21"}],"replies":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/comments?post=17364"}],"version-history":[{"count":8,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/17364\/revisions"}],"predecessor-version":[{"id":18186,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/posts\/17364\/revisions\/18186"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media\/18184"}],"wp:attachment":[{"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/media?parent=17364"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/categories?post=17364"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.youstable.com\/blog\/wp-json\/wp\/v2\/tags?post=17364"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}