Channel
@bash_srv
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,742subscribers
-8 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002452273039 |
|---|---|
| Type | Channel |
| Username | @bash_srv |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/bash_srv |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 22:26 | 2,742 | -5 |
| 10 Aug 2026, 06:43 | 2,747 | -3 |
| 7 Aug 2026, 07:43 | 2,750 | no change |
| 7 Aug 2026, 00:46 | 2,750 | first reading |
20 posts held, back to 22 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 5 August 2026 |
|---|---|
| Posts held | 20 (22 June 2026 – 5 August 2026) |
| Views total | 6,455 |
| Reactions total | 66 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 16:11 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
114 reactions across 20 posts, in 5 distinct kinds. The most used accounts for 64.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 73 | 64.0% | |
| 🔥 | 25 | 21.9% | |
| ❤ | 13 | 11.4% | |
| 🤡 | 2 | 1.75% | |
| 🫡 | 1 | 0.877% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 114reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 22 June 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
🕵️ Ищем процессы, которые используют удалённые (удалённые, но не освобождённые) файлы Бывает, что ты удаляешь лог или большой файл, а место на диске не освобождается? Это потому, что файл всё ещё открыт каким-то процессом! Вот скрипт, который найдёт таких «виновников»: #!/bin/bash echo "🔍 Ищем процессы, держащие открытые удалённые файлы..." lsof | grep '(deleted)' | awk '{print $2}' | sort -u | while read -r pid;…
👍4❤1🔥1
🧠 Bash совет дня - Отслеживаем подозрительные sudo-команды в реальном времени 🕵️ Хочешь знать, кто и что запускает через sudo прямо сейчас? Настроим простой мониторинг: #!/bin/bash logfile="/var/log/auth.log" tail -F "$logfile" | grep --line-buffered "sudo" | while read line; do echo "[ALERT] 🔐 $(date): $line" done 📌 Что делает: - Следит за /var/log/auth.log в реальном времени. - Отфильтровывает строки, свя…
👍6
$ sudo apt install holiday Reading package lists... Done Building dependency tree... Done Устанавливается пакет: "День системного администратора" ✔ Серверы работают ✔ Мониторинг молчит ✔ Бэкапы актуальны ✔ Кофе горячий ✔ Пользователи не паникуют Congratulations! Happy SysAdmin Day! 🎉
❤8
🚀 Bash-совет дня: Быстрое сканирование открытых портов с помощью bash и /dev/tcp Зачем ставить nmap, если можно быстро просканировать порты встроенными средствами bash? Вот простой однострочный скрипт: for port in {20..1024}; do (echo > /dev/tcp/127.0.0.1/$port) >/dev/null 2>&1 && echo "Порт $port открыт" done 📌 Что делает скрипт: * Использует встроенную возможность Bash подключаться к TCP-портам через псевдо…
👍4❤3🔥2
🚀 Подборка полезных IT каналов в Max Системное администрирование, DevOps 📌 https://max.ru/i_odmin Все для системного администратора https://max.ru/bash_srv Bash Советы https://max.ru/sysadminof Книги для админов, полезные материалы https://max.ru/i_odmin_book Библиотека Системного Администратора https://max.ru/i_devops DevOps: Пишем о Docker, Kubernetes и др. https://max.ru/tipsysdmin Типичный Сисадмин https://max…
🫡1
🧠 Bash-совет дня: Проверка скорости интернет-соединения прямо из терминала Если тебе нужно быстро проверить скорость интернета на сервере (например, VPS), не устанавливая громоздкие GUI-программы — вот решение: #!/bin/bash # Проверяем наличие speedtest-cli if ! command -v speedtest &> /dev/null; then echo "⏳ Устанавливаем speedtest-cli..." apt update && apt install -y speedtest-cli # Для Debian/Ubuntu …
👍6
🎯 Проверка доступности списка хостов с цветным 🎨 выводом Иногда нужно быстро проверить, какие сервера "живые", а какие — нет. Ниже написал удобный Bash-скрипт с цветным выводом в терминале 🖥️. #!/bin/bash # Список хостов hosts=("192.168.0.1" "google.com" "yandex.ru" "192.168.0.100") # Цвета GREEN="\e[32m" RED="\e[31m" NC="\e[0m" # No Color for host in "${hosts[@]}"; do if ping -c 1 -W 1 "$host" &> /dev/null…
👍6🔥1
🧠 Bash: Проверка доступности нескольких хостов одним скриптом Следишь за парком серверов? Этот скрипт покажет, какие машины "живы", а какие — нет 🖥️❌ #!/bin/bash # Список IP или хостнеймов HOSTS=("192.168.0.1" "google.com" "server.local") for HOST in "${HOSTS[@]}"; do if ping -c 1 -W 1 "$HOST" &> /dev/null; then echo "[✅] $HOST доступен" else echo "[❌] $HOST недоступен" fi done 📌 Что делает: * pi…
👍7🔥1
🔥Проверка статуса нескольких сервисов systemd за один раз Когда нужно быстро проверить, работают ли нужные сервисы - этот однострочник спасёт: for svc in nginx mysql sshd; do systemctl is-active --quiet $svc && echo "$svc ✅" || echo "$svc ❌"; done 📌 Замените nginx mysql sshd на нужные вам сервисы. Скрипт выведет статус каждого: * ✅ — сервис активен * ❌ — сервис не работает 🚀 Удобно засунуть в alias или в монит…
👍2🔥2
💡 Bash-совет дня: Мониторинг открытых портов с выводом в Telegram Автоматизируй контроль за безопасностью своего сервера! Этот простой bash-скрипт проверяет изменения в открытых портах и шлёт уведомление в Telegram, если появились новые или исчезли старые порты. #!/bin/bash # Настройки TG_TOKEN="your_bot_token" TG_CHAT_ID="your_chat_id" PORTS_FILE="/var/tmp/open_ports_last.txt" # Получаем текущие открытые порты …
👍3🔥1
🔐 Как найти файлы с открытыми правами (777) - быстро и просто! Иногда на сервере появляются файлы и каталоги с правами 777, что представляет угрозу безопасности. Найдём их одной командой: find / -type f -perm 0777 2>/dev/null 📁 А если нужно проверить директории: find / -type d -perm 0777 2>/dev/null 🔍 Пояснение: / - путь, где искать (можно заменить на /var, /home и т.д.) -type f / -type d — искать только …
👍5🔥2
🔁 Циклический мониторинг статуса сервиса с логированием Иногда нужно следить за работой сервиса в режиме реального времени и при сбое — сразу зафиксировать проблему. Вот простой скрипт, который будет каждые 30 секунд проверять статус сервиса и писать лог при ошибке: #!/bin/bash SERVICE="nginx" LOGFILE="/var/log/${SERVICE}_monitor.log" INTERVAL=30 while true; do if ! systemctl is-active --quiet "$SERVICE"; th…
👍4
Showing the 12 most recent of 20 posts we hold for @bash_srv. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 871,924 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Bash Советы” (@bash_srv), 2,742 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/bash_srv.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.