What is using a port?
Find which process is listening on or connected to a port.
Fast reference for setup and troubleshooting work. Search by command name, what it does, the problem being solved, or words like logs, port, disk, permissions, service, or dns. Each card explains when to use it, why it matters, common arguments, and copy-pasteable examples.
Find which process is listening on or connected to a port.
Check status first, then read its recent logs.
Look for files modified in the last day or hour.
Check filesystem usage, then drill into big directories.
Inspect live resource usage by process.
Read the end of a log and optionally follow it live.
Query DNS records directly.
Test reachability at host or port level.
Confirm identity, groups, and current shell context.
Check kernel and hardware-level visibility.
Run it in a persistent session or detached mode.
Copy a backup, inspect metadata, then edit.
Check whether the interface, phy, and capabilities exist at all.
Confirm boot overlay lines and look for SPI device nodes.
Check module presence and read module metadata.
Check route choice, neighbor resolution, and packet presence.
Use it for packaging backups, logs, or source trees.
Why it mattersIt is the standard archive tool on Linux.
ExamplesUse it to shrink text logs, dumps, or archives.
Why it mattersIt is simple and widely supported.
ExamplesUse it when sharing files with systems or users that expect zip format.
Why it mattersZip is widely compatible, especially across platforms.
ExamplesUse it to unpack downloaded software or shared bundles.
Why it mattersEssential for handling zip packages.
ExamplesUse it for backups, deployments, mirrors, and incremental copies.
Why it mattersIt only transfers changed data and preserves metadata well.
ExamplesUse it when you need a quick secure copy to or from another host.
Why it mattersIt is simple for one-off remote transfers.
ExamplesUse it when you want a session for browsing and transferring remote files securely.
Why it mattersUseful when you need multiple remote file operations in one session.
ExamplesUse it for remote administration, commands, tunneling, and copying.
Why it mattersIt is the core remote admin tool on Linux.
ExamplesUse it when setting up passwordless login or deploy access.
Why it mattersSSH keys are more secure and more convenient than passwords.
ExamplesUse it for long-running jobs over SSH that must survive disconnects.
Why it mattersPrevents work from dying when your connection drops.
ExamplesUse it to find which process is using a file, directory, or network port.
Why it mattersIt is one of the best commands for 'what is holding this open?' problems.
ExamplesUse it when a command fails mysteriously, hangs, or gets permission/file errors.
Why it mattersIt shows what the program is trying to do at the OS level.
ExamplesUse it when checking detected hardware like NICs, GPUs, or storage controllers.
Why it mattersGood first step for hardware identification.
ExamplesUse it when checking whether USB hardware is detected.
Why it mattersUseful for adapters, dev boards, radios, storage, and keyboards.
ExamplesUse it when checking overheating or fan-related issues.
Why it mattersIt helps explain throttling and unexpected shutdowns.
ExamplesUse it when disks act strangely, throw errors, or you suspect failing hardware.
Why it mattersIt gives direct health info from the drive.
ExamplesUse it when a system feels slow and you suspect disk bottlenecks.
Why it mattersIt helps separate CPU problems from storage problems.
ExamplesUse it when you need to answer what happened earlier, not just right now.
Why it mattersIt is valuable for retrospective performance analysis.
ExamplesUse it when tuning build jobs or checking CPU core availability.
Why it mattersHandy for parallelism settings like make -j.
ExamplesUse it to auto-answer simple prompts or generate endless output for testing.
Why it mattersSmall but surprisingly handy in scripts and pipelines.
ExamplesUse it anytime you need to see whether the radio exists, what capabilities it has, whether it is linked, or what peers and surveys look like.
Why it mattersFor modern Linux wireless work, this is one of the main tools and is much more useful than legacy wireless tools.
ExamplesUse it when the radio seems missing or will not transmit and you suspect a kill switch or soft block.
Why it mattersIt quickly tells you whether Linux itself is blocking the wireless device.
ExamplesUse it only when checking older scripts or legacy driver setups that still reference wireless extensions.
Why it mattersIt still appears in a lot of older how-tos, so it is useful to recognize, but for modern work iw is usually the better tool.
ExamplesUse it when association looks fine but peers still cannot actually exchange traffic.
Why it mattersIt helps separate a layer-2 neighbor problem from a higher-level routing or application problem.
ExamplesUse it when packets leave but do not arrive cleanly, or when you suspect a path or MTU problem.
Why it mattersIt is a fast next step after ping when basic reachability exists but something still breaks.
ExamplesUse it when you need to confirm what module you have, where it lives, which version it is, or what firmware and parameters it expects.
Why it mattersThis is one of the quickest ways to validate driver/module assumptions during bring-up.
ExamplesUse it when you need to see whether the expected wireless, SPI, or supporting modules actually loaded.
Why it mattersIt is the fastest loaded-module sanity check before going deeper.
ExamplesUse it for boot-time driver logs, supplicant failures, network service issues, and reproducing problems while watching live output.
Why it mattersFor systemd-based systems it is one of the fastest routes to the real error.
ExamplesUse it when a guide tells you to mount debugfs before inspecting ieee80211 or other kernel debug paths.
Why it mattersSome low-level debug views do not exist until the right pseudo-filesystem is mounted.
ExamplesUse it when a wireless failure is too subtle for normal logs and you need kernel event tracing while reproducing the issue.
Why it mattersIt gives much deeper visibility into wireless stack behavior than normal user-space logs.
ExamplesUse it when the link appears up but traffic is failing and you need to see whether packets are actually present on the wire.
Why it mattersIt quickly separates RF/link problems from IP, routing, and application problems.
ExamplesUse it when you need to confirm that the expected SPI or HaLow overlay is actually referenced in Pi boot config.
Why it mattersA missing or wrong overlay line can make the hardware look completely absent higher up the stack.
ExamplesUse it when verifying that Pi SPI bring-up succeeded far enough to expose spidev devices.
Why it mattersIt is an immediate sanity check before blaming higher-level driver code.
ExamplesUse it when you are not sure where you are in the filesystem before editing, deleting, or copying files.
Why it mattersPrevents mistakes caused by running commands in the wrong directory.
ExamplesUse it to inspect what exists in a directory before opening, moving, or deleting anything.
Why it mattersIt is the fastest way to see names, permissions, sizes, and timestamps.
ExamplesUse it anytime you need to move to a different folder to run commands there.
Why it mattersMany Linux commands operate relative to the current directory.
ExamplesUse it to quickly understand project layouts, log folders, or config directories.
Why it mattersIt is much easier to visualize nested folders than with repeated ls calls.
ExamplesUse it when you know part of a name, need files changed recently, or need to bulk-process matches.
Why it mattersIt is one of the most powerful ways to locate files on Linux.
ExamplesUse it when you want a very fast filename search and do not need real-time freshness.
Why it mattersIt is much faster than find for broad filename lookups.
ExamplesUse it to inspect exact timestamps, permissions, inode numbers, or file size during troubleshooting.
Why it mattersIt gives more precise details than ls.
ExamplesUse it when an extension is misleading or you are unsure what a file really is.
Why it mattersIt helps confirm whether something is text, binary, image, archive, script, or executable.
ExamplesUse it to duplicate files, stage backups, or clone directory trees.
Why it mattersIt is the standard safe way to copy data before making changes.
ExamplesUse it when reorganizing files or changing names without copying.
Why it mattersIt is usually faster than copy+delete and is the standard rename tool.
ExamplesUse it for almost all modern networking checks instead of older ifconfig/route tools.
Why it mattersIt is the current standard network management command.
ExamplesUse it to see what is bound to a port or which connections are open.
Why it mattersIt is faster and more modern than netstat.
ExamplesUse it as a first check for network path and basic DNS resolution.
Why it mattersIt quickly tells you whether a host responds at all.
ExamplesUse it when a remote host is reachable poorly or traffic seems to die somewhere in between.
Why it mattersIt helps isolate where along the route the problem appears.
ExamplesUse it when traceroute is unavailable or you want a quick path check.
Why it mattersUseful lightweight alternative.
ExamplesUse it for API calls, downloads, header checks, testing web services, and debugging redirects.
Why it mattersIt is one of the most important network troubleshooting tools.
ExamplesUse it for simple file grabs, recursive downloads, or resuming transfers.
Why it mattersIt is straightforward and script-friendly.
ExamplesUse it when troubleshooting domain resolution, MX records, nameservers, or propagation.
Why it mattersIt shows authoritative DNS answers clearly.
ExamplesUse it for quick hostname-to-IP checks or when dig is not installed.
Why it mattersIt is widely available and easy to remember.
ExamplesUse it to test whether a port is reachable or to create simple listeners.
Why it mattersExcellent for quick low-level network checks.
ExamplesUse it for long jobs, multiple shells, or remote work that must survive disconnects.
Why it mattersIt is extremely useful for serious terminal workflows.
ExamplesUse it to install, remove, search, and update software packages.
Why it mattersIt is the standard way to manage software on Debian systems.
ExamplesUse it to inspect installed .deb packages or install a local .deb file.
Why it mattersHelpful when apt is not enough or when checking package contents.
ExamplesUse it when scheduling recurring scripts or maintenance tasks.
Why it mattersCron is one of the core Linux automation tools.
ExamplesUse it when you need a delayed one-off action instead of a recurring cron job.
Why it mattersIt is simpler than creating temporary cron entries.
ExamplesUse it to monitor disk, memory, process, or service state every few seconds.
Why it mattersIt turns static commands into lightweight dashboards.
ExamplesUse it when starting a background job that should survive terminal logout.
Why it mattersUseful for one-off detached jobs when you do not need tmux/screen.
ExamplesUse it when managing jobs started from your current shell.
Why it mattersHelps you see what is suspended or running in the background.
ExamplesUse it after pressing Ctrl+Z on a command you want to keep running.
Why it mattersLets you recover a stopped task without starting over.
ExamplesUse it when you need to interact with a job again.
Why it mattersIt returns control of a shell job to the terminal.
ExamplesUse it when access is denied or you need to adjust read/write/execute bits.
Why it mattersPermissions are a common cause of Linux issues.
ExamplesUse it when files belong to the wrong user or service account.
Why it mattersWrong ownership often breaks websites, logs, and uploads.
ExamplesUse it when newly created files keep getting the wrong default permissions.
Why it mattersIt explains why new files are more or less open than expected.
ExamplesUse it when storage is low or writes start failing.
Why it mattersIt quickly tells you whether a filesystem is full.
ExamplesUse it after df shows a full disk and you need to find what is consuming space.
Why it mattersIt helps locate the big directories quickly.
ExamplesUse it when working with extra disks, USB drives, ISO files, or troubleshooting mounts.
Why it mattersMany storage issues come down to what is or is not mounted.
ExamplesUse it before removing media or remounting with new options.
Why it mattersPrevents corruption and releases the filesystem cleanly.
ExamplesUse it to understand disks and partitions before mounting or formatting.
Why it mattersIt gives a clean storage map.
ExamplesUse it when building fstab entries or identifying drives reliably.
Why it mattersUUIDs are more stable than device names like /dev/sdb1.
ExamplesUse it when examining or creating partitions on disks.
Why it mattersIt is a core low-level storage tool.
ExamplesUse it to see what is running, who owns it, and how much CPU or memory it uses.
Why it mattersIt is the standard process inspection command.
ExamplesUse it when a server feels slow or you need live CPU/memory insight.
Why it mattersIt shows the biggest resource users in real time.
ExamplesUse it when you want a friendlier version of top with easier sorting and killing.
Why it mattersIt is more readable and convenient than top for many admins.
ExamplesUse it to stop hung programs, reload daemons, or terminate jobs.
Why it mattersIt gives direct control over process signals.
ExamplesUse it when you know the process name but not the PID.
Why it mattersIt is faster than finding each PID manually.
ExamplesUse it when you need a PID for kill, renice, or inspection.
Why it mattersIt avoids fragile grep pipelines.
ExamplesUse it when you want to stop matching processes directly without manually extracting PIDs.
Why it mattersIt combines pgrep and kill into one step.
ExamplesUse it during performance checks or after a reboot.
Why it mattersIt gives a quick health snapshot in one line.
ExamplesUse it when you suspect RAM pressure or swap use.
Why it mattersIt quickly answers whether memory is a bottleneck.
ExamplesUse it when diagnosing general slowness, swap, or IO wait.
Why it mattersIt gives a broader performance picture than free alone.
ExamplesUse it in scripts, quick tests, and pipelines.
Why it mattersIt is a basic shell building block.
ExamplesUse it in scripts when you need predictable formatting.
Why it mattersMore reliable than echo for structured output.
ExamplesUse it to feed lists of files or values into another command.
Why it mattersIt is great for turning pipeline output into arguments.
ExamplesUse it when you want to see output live and save it at the same time.
Why it mattersVery useful for logging command output without losing terminal visibility.
ExamplesUse it when multiple versions may exist or you are unsure where a command comes from.
Why it mattersHelps debug PATH issues.
ExamplesUse it to tell whether something is an alias, builtin, function, or executable.
Why it mattersIt is often more informative than which.
ExamplesUse it to shorten frequent commands or make safer defaults.
Why it mattersSpeeds up repetitive terminal work.
ExamplesUse it when configuring PATH, API keys, or runtime options in the current shell.
Why it mattersMany tools read behavior from environment variables.
ExamplesUse it to inspect variables or launch a command with temporary overrides.
Why it mattersUseful for debugging shell and app environment issues.
ExamplesUse it after changing shell config files or environment setup scripts.
Why it mattersIt applies changes without opening a new shell.
ExamplesUse it when checking OS architecture, kernel version, or environment compatibility.
Why it mattersIt helps confirm what system you are actually on.
ExamplesUse it when confirming host identity or changing the hostname.
Why it mattersIt gives cleaner host details than older methods.
ExamplesUse it to start, stop, restart, enable, disable, or inspect services.
Why it mattersIt is one of the most important commands on modern Linux systems.
ExamplesUse it on systems or guides that still reference it.
Why it mattersUseful for quick service actions, though systemctl is usually preferred.
ExamplesUse it to inspect service failures, boot logs, and recent system events.
Why it mattersIt is often the first place to look when a service will not start.
ExamplesUse it for hardware, driver, boot, USB, disk, and kernel error troubleshooting.
Why it mattersKernel-level problems often show up here first.
ExamplesUse it when you are unsure which account or sudo context you are in.
Why it mattersPrevents running commands as the wrong user.
ExamplesUse it when checking group membership or permissions issues.
Why it mattersIt clearly shows UID, GID, and supplementary groups.
ExamplesUse it on shared systems to see who is active.
Why it mattersUseful for multi-user server awareness.
ExamplesUse it when auditing access or checking reboot history.
Why it mattersIt helps answer who logged in and when.
ExamplesUse it for quick reads of short config or text files.
Why it mattersIt is the fastest basic file viewer.
ExamplesUse it for logs, configs, and long command output.
Why it mattersIt is far easier than cat for large files.
ExamplesUse it to inspect headers, config starts, or CSV columns.
Why it mattersIt avoids opening an entire large file.
ExamplesUse it for log troubleshooting, watching cron output, or seeing the newest lines.
Why it mattersIt is one of the most useful commands for diagnostics.
ExamplesUse it to find errors, config values, IPs, usernames, or keywords in output and files.
Why it mattersIt narrows huge amounts of text down to what matters.
ExamplesUse it for quick in-place edits, substitutions, or extracting lines in scripts.
Why it mattersIt is faster than opening a file manually for simple text changes.
ExamplesUse it for column-based logs, CSV-like data, or report summaries.
Why it mattersIt is excellent for parsing structured text on the command line.
ExamplesUse it to order output before review, diffing, or counting.
Why it mattersSorted data is easier to compare and summarize.
ExamplesUse it after sort to count repeated values such as IPs, paths, or users.
Why it mattersIt helps summarize repeated data quickly.
ExamplesUse it when you only need a small slice of structured text.
Why it mattersIt is lightweight and simple for delimiter-based extraction.
ExamplesMany of the most useful Linux troubleshooting patterns come from combining commands. A few very common combos are command | grep pattern for narrowing output, tail -f logfile while reproducing an issue, find ... -mtime for recently changed files, and systemctl status + journalctl -u service for service failures.
When changing anything important, it is usually worth doing three things first: confirm the current location with pwd, inspect the target with ls -lah or stat, and make a backup with cp file file.bak.
For production troubleshooting, the biggest time-savers are usually: knowing how to inspect logs, understanding disk usage, checking process state, verifying permissions and ownership, and testing whether a service is actually listening on the expected port.