<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>sysadmin on toorun.dev</title><link>https://toorun.dev/tags/sysadmin/</link><description>Recent content in sysadmin on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Wed, 26 Aug 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/sysadmin/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Retrieve Hardware Specifications on Linux and Embedded Systems: CPU, RAM, Storage, Peripherals, and System Info</title><link>https://toorun.dev/posts/retrieve-hardware-specs-linux-embedded-systems/</link><pubDate>Wed, 26 Aug 2026 08:00:00 +0000</pubDate><guid>https://toorun.dev/posts/retrieve-hardware-specs-linux-embedded-systems/</guid><description>How to Retrieve Hardware Specifications on Linux and Embedded Systems When debugging, deploying, or documenting an embedded system or Linux machine, you need to know what hardware you are working with: CPU type and speed, available memory, storage capacity, connected peripherals, and kernel configuration.
This guide provides practical commands and file locations to retrieve all critical hardware information on Linux-based systems, from servers to embedded devices.
1. CPU Information Basic CPU Info # Detailed CPU information lscpu # Raw CPU data cat /proc/cpuinfo # CPU architecture uname -m What you get: CPU model, cores, threads, architecture (ARM, x86_64, RISC-V), frequency, cache sizes, flags (NEON, AVX, FPU).</description></item><item><title>SNMP in Linux: Practical Setup, Secure Defaults, and Useful Commands</title><link>https://toorun.dev/posts/snmp-in-linux-practical-setup-monitoring-commands/</link><pubDate>Fri, 24 Jul 2026 11:30:00 +0000</pubDate><guid>https://toorun.dev/posts/snmp-in-linux-practical-setup-monitoring-commands/</guid><description>SNMP in Linux (Short Practical Guide) SNMP is a lightweight protocol to monitor devices and servers. You can read metrics like CPU, memory, interfaces, disk usage, and uptime from one central tool.
1) When SNMP is useful Use SNMP when you need:
Basic infrastructure monitoring across mixed vendors. Simple polling from NMS tools (Zabbix, LibreNMS, PRTG, etc.). Device visibility where agent options are limited. 2) SNMP versions (quick choice) SNMPv1: old, avoid.</description></item><item><title>Linux NTP: Practical Settings and Usage</title><link>https://toorun.dev/posts/linux-ntp-time-sync-settings-chrony-timesyncd-ntpd/</link><pubDate>Fri, 24 Jul 2026 10:00:00 +0000</pubDate><guid>https://toorun.dev/posts/linux-ntp-time-sync-settings-chrony-timesyncd-ntpd/</guid><description>Linux NTP (Short Practical Guide) Accurate time is required for TLS, logs, monitoring, cron jobs, and distributed systems. In Linux, use one time-sync service only.
1) Check current time sync status timedatectl status Look for:
System clock synchronized: yes NTP service: active 2) Recommended choice: chrony chrony is usually the best default for servers and unstable networks.
Install and enable:
# Debian/Ubuntu sudo apt update &amp;amp;&amp;amp; sudo apt install -y chrony sudo systemctl enable --now chrony # RHEL/CentOS/Fedora sudo dnf install -y chrony sudo systemctl enable --now chronyd Basic config file:</description></item><item><title>Windows Batch Auto-Run: At Login, Without Login, and On Logout</title><link>https://toorun.dev/posts/windows-batch-auto-run-login-logout-task-scheduler/</link><pubDate>Thu, 23 Jul 2026 10:30:00 +0000</pubDate><guid>https://toorun.dev/posts/windows-batch-auto-run-login-logout-task-scheduler/</guid><description>Windows Batch Auto-Run (Short Practical Guide) Use different methods depending on when the script must run.
1) Auto-run after user login (Startup folder) Create C:\Scripts\hello-login.bat:
@echo off echo Login script ran at %date% %time% &amp;gt;&amp;gt; C:\Scripts\login.log Open Startup folder:
Win + R -&amp;gt; shell:startup Put a shortcut to hello-login.bat there.
Best for per-user, interactive tasks.
2) Auto-run after user login (Registry Run key) reg add &amp;#34;HKCU\Software\Microsoft\Windows\CurrentVersion\Run&amp;#34; ^ /v HelloLogin ^ /t REG_SZ ^ /d &amp;#34;C:\Scripts\hello-login.</description></item><item><title>Linux Process Prioritization: nice, renice, and Practical Tuning</title><link>https://toorun.dev/posts/linux-process-prioritization-nice-renice-chrt-ionice/</link><pubDate>Mon, 20 Jul 2026 09:00:00 +0000</pubDate><guid>https://toorun.dev/posts/linux-process-prioritization-nice-renice-chrt-ionice/</guid><description>Linux Process Prioritization (Short Practical Guide) When a system is busy, process priority helps decide what gets CPU and I/O time first.
1) CPU priority with nice nice sets a process niceness from -20 (highest priority) to 19 (lowest priority).
Start a low-priority background job:
nice -n 10 tar -czf backup.tar.gz /data Start a higher-priority job (usually requires root for negative values):
sudo nice -n -5 ./latency_sensitive_app Check NI (niceness) and PRI:</description></item></channel></rss>