Page 8 - Linux

Anyone who only uses sed line by line with s/old/new/ quickly hits a wall with config blocks, XML fragments and multiline log entries. Hold space and pattern space give sed the ability to look at several lines at once and replace them as one connected block, without ever reaching for Perl or Python.

nohup ignores the SIGHUP signal, disown removes a job from the shell's job table after the fact, and setsid starts a brand-new session with no controlling terminal at all. Knowing the difference means picking the right, most robust tool for every background service in a deployment script.

Bare metal, virtual machines and containers form a spectrum of isolation, overhead and deployment speed, not a simple either-or decision. This article explains when full hardware control is necessary, when hypervisor isolation makes sense for multi-tenancy, and when containers are the faster choice, along with the hybrid approach that most production hosting setups actually run to balance cost, security and operational effort.

Anyone who only checks DNS records one at a time by hand misses propagation problems and silent changes. Automating DNS lookups with dig and host processes domain lists in seconds, compares resolvers, and catches configuration mistakes before customers report them.

aws s3 sync transfers only changed files between a local directory and an S3 bucket, making it the standard tool for deployment and backup scripts in Bash. Used correctly it saves time and bandwidth. Used carelessly, the --delete flag can wipe out entire bucket contents in seconds. This article shows the patterns that make the difference.

Not every task requires a machine that keeps running around the clock. With rtcwake, Linux puts a machine into a targeted power saving state and wakes it back up via an RTC alarm at exactly the desired moment, to perform a task and then switch back into idle mode afterward. This article explains how rtcwake works, the required prerequisites in BIOS and kernel, and automation for backup windows, energy savings, and test infrastructure.

Cron has been the standard for scheduled tasks on Linux for decades, but it hits clear limits around dependencies, logging, and error handling. systemd timers offer a far more observable alternative with OnCalendar syntax, journalctl integration, and automatic retry, and can be introduced step by step through a concrete migration.

On most current Linux distributions, DNS resolution today runs through systemd-resolved by default instead of directly through kernel or glibc anchored name resolution. For admins juggling internal VPN networks, Docker containers and the public internet, understanding this stub resolver is no longer optional, it is a prerequisite for DNS resolution to work reliably at all in mixed network environments.

Every time a container is started with a published port, Docker silently rewrites the host's iptables rule set. This automation is convenient, but it regularly causes hard-to-trace conflicts once custom firewall rules or tools like firewalld enter the picture.

A reindex, a backup, or a large cron job competes directly with PHP-FPM workers for the same CPU time and the same disk access without deliberate priorities. nice and ionice allow deliberately deprioritizing background jobs, so they only get resources when the web server does not currently need them.