DevOps Lab Part 2: Writing a Bash Health Report Script for a Linux Server

·2 views

The author continues a beginner DevOps learning series by moving from setting up an Ubuntu EC2 server to building a practical tool on it. They created a short Bash script that prints a health report covering the current UTC time, root filesystem disk usage, memory and swap usage, and uptime with load averages. The script and accompanying README were committed to a GitHub repository, with the author noting that AI assistance was used for guidance while verifying outputs. Observed values on their instance included about 6.8 GB usable disk with roughly 34–35% usage and about 952 MiB RAM with no swap configured, though the author stresses these vary by machine. The author also clarifies that the report alone cannot judge server health, since that depends on workload and what normal looks like, and that the script does not check application availability, send alerts, or keep history.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Developer builds math-first Texas Hold'em toolkit in C# with open collaboration

A solo engineer has developed an open Texas Hold'em toolkit in C# that emphasizes mathematical design over lookup tables. The project uses bitwise card primitives and Monte Carlo equity estimation, with extensible game-state abstractions for analysis and strategy modeling. It already includes Hold'em-specific logic, command-line tools for range-versus-range estimation, and benchmark projects. Reported timings for 10,000 simulations are about 284.5 ms with two players, 448.3 ms with three, and 628.7 ms with four. The author describes the work as early-stage and is inviting contributors interested in poker math, optimization, and simulation systems.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Unsubscribing does not always stop charges, and refunds can stall

Developers discussing subscription waste on Hacker News describe a recurring problem: users cancel or request refunds but still get billed or hear nothing back. One commenter says a refund request for a forgotten subscription was ignored entirely, while another recounts a vendor that agreed to a partial refund and then went silent, prompting a chargeback. Other threads point to recurring pricing models that charge for one-time needs and per-seat plans that keep billing for unused licenses. Commenters argue that the real failure happens after a subscription is discovered, not in finding it. Several suggest the most effective fix is cancelling directly through the bank or card provider, though that approach has limits.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Agent loops need runtime controls: budgets, deadlines, cancellation, and idempotency

The article argues that production failures in AI agents usually stem from the execution loop rather than model quality, such as runs that spin for long periods, duplicated side effects, or cancellations that fail to stop workers. It recommends treating the loop as a runtime with admission control, deadlines, cooperative cancellation, and at-most-once side effects. Agent runs should have separate limits on steps, wall-clock time, tool calls, and cumulative tokens or cost, since per-step costs rise as conversation history grows. Cancellation must also reach inside tool calls through propagated deadlines and explicit timeouts on every blocking operation. Finally, retried writes should be prevented with deterministic idempotency keys stored alongside the effect, and third-party APIs without idempotency support should use an outbox-style record-and-reconcile approach.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Zoho Founder Says One AI-Equipped Worker Could Match Ten, Warns of Faster Job Losses

Sridhar Vembu, founder and chief scientist of Zoho, warned in an October 29 post on X that one skilled worker using AI could perform the work of ten. He said the risk of job losses in computer-based office work is becoming more real as AI tools improve. Vembu did not forecast that 90% of jobs will disappear, but argued that reduced labor needs could arrive faster than new job creation. He acknowledged that cheaper work could eventually lower prices and spawn new businesses, but said the timing gap could hit wages, hiring and entry-level roles first.

0 comments Read more at DEV Community