Page 18 - Linux

Client-side Git hooks are convenient, but every developer can bypass them with --no-verify, delete them, or simply never install them. Server-side hooks, by contrast, run on the central Git server, where nobody has direct access, making them the only real enforcement point for force-push protection, file size limits and branch naming conventions across the team.

Docker containers usually run fine in testing, but in continuous operation log rotation, the right storage driver, clean systemd integration and clear resource limits decide whether a single container brings down the whole server or keeps running quietly in the background. This article shows how administrators configure the Docker daemon for production, keep containers starting reliably and continuously monitor their health status.

Solid PCI-DSS hardening requires concrete Linux configuration, not just process documentation. Understanding which requirements of the standard apply directly to the server allows implementing firewall segmentation, access control, logging and file integrity in a way that holds up to a Qualified Security Assessor.

Anyone who cannot start a service because a port is already in use, or needs to know which process is really behind a connection, cannot avoid ss. This article explains why ss replaced the old netstat, how to correctly read connection states like ESTABLISHED and TIME_WAIT, and how to reliably diagnose port conflicts before starting a service.

Teams looking for a Docker Desktop alternative because of licensing rules or resource usage almost always end up comparing Colima and Podman. Both replace the commercial Docker Desktop daemon with leaner, open solutions, but they differ significantly in architecture, compatibility and everyday usability for development teams.

inotify is a kernel interface that notifies Bash scripts the instant a file or directory changes, instead of checking again and again in a loop. With the command line tool inotifywait from the inotify-tools package, you can build deployment triggers, config reloads and log watchers that react to real events rather than a fixed time interval.

NTP reliably synchronizes system clocks to within a few milliseconds, but certain applications need far more: sub-microsecond accuracy across the local network. This guide explains how PTP under IEEE 1588 works with hardware timestamping, how linuxptp with ptp4l and phc2sys is set up on Linux, and when the extra effort compared to NTP actually pays off.

Killing production processes with kill -9 risks corrupted PHP-FPM requests, orphaned locks, and inconsistent data. This article explains how Unix signals really work, why SIGTERM and SIGKILL are fundamentally different, how to trap signals cleanly in your own scripts, and how kill, pkill, killall, and systemd work together for controlled process management.

A CIS Benchmark provides the most concrete checklist available for hardening a Linux server traceably and meeting compliance requirements. Anyone who understands the controls, prioritizes them and automates them with CIS-CAT and Ansible replaces manual one off checks with repeatable, auditable processes.

Mount points decide how and where data ends up on a Linux server, and the choice of filesystem determines performance, safety, and recoverability when things go wrong. This article explains the mechanics behind mount, the correct fstab syntax, and shows with concrete examples when ext4, XFS, or Btrfs is genuinely the right choice on a production server.