Обучающий канал по ОС Linux & Windows для начинающих и действующих администраторов.
Админ, реклама: @Ak_Mihail
Биржа: https://telega.in/c/admguides
РКН: https://kurl.ru/nQejS
Created
Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
7 measurements spanning 5 days, net +4. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 11,825–11,833 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
12 Aug 2026, 10:15
11,830
+2
11 Aug 2026, 08:43
11,828
+2
10 Aug 2026, 08:18
11,826
-6
9 Aug 2026, 11:11
11,832
+2
8 Aug 2026, 09:41
11,830
+4
7 Aug 2026, 10:30
11,826
no change
7 Aug 2026, 10:28
11,826
first reading
Engagement
31 posts held, back to 28 July 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 17 pagesof Telegram’s post history, 20 posts per page.
ERR · 30 days
10.9%
avg views ÷ 11,830 subscribers
Avg views / post
1,290
31 posts measured
Reaction rate
0.626%
reactions ÷ views · ER floor
Posts in window
31
of 31 held
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.
What these figures were computed from
Window
Rolling 30 days · latest post in window 12 August 2026
Posts held
31 (28 July 2026 – 12 August 2026)
Views total
40,065
Reactions total
251
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
13 Aug 2026, 05:04 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.
What this channel posts
Photos
≈1,710
Videos
≈23
Links
≈588
Lifetime counters from Telegram’s own channel header, read 13 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
251 reactions across 31 posts, in 14 distinct kinds. The most used accounts for 37.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
❤
94
37.5%
👍
69
27.5%
🤣
24
9.56%
🔥
23
9.16%
🤡
14
5.58%
😁
12
4.78%
👎
5
1.99%
✍
2
0.797%
👏
2
0.797%
🤝
2
0.797%
💊
1
0.398%
🗿
1
0.398%
🤔
1
0.398%
🥴
1
0.398%
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 31 of the 31 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 251reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 31 most recent posts we hold, published 28 July 2026 to 12 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.
Advertising
Ad load
3.23%
1 of 31 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,020
over 1 measured post
Median views · rest
1,370
over 30 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor.A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2VtzqwNqfP1
1
10 August 2026
10 August 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 31 most recent posts we hold, published 28 July 2026 to 12 August 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
HEAD-скан: как перебирают ваши файлы, ничего не скачивая 🍃
В логах строка, подобная тени на воде:
203.0.113.42 - "HEAD /upload/disk/157/a7f3c1b9e4...xlsx" 200 0 "-" "-"
Метод HEAD возвращает лишь заголовки, подобно тому как мастер отвечает на вопрос тишиной. Тело не передаётся, трафика нет, в графиках ничего не всплывает. Зато ответ говорит главное: файл существует и весит столько-то. Как и гласит старая пословица, п…
Почему pkill может затронуть не тот процесс
pkill удобен, но опасен тем, что по умолчанию ищет совпадения по имени процесса. На сервере легко получить ситуацию, когда под условие попадают несколько процессов.
Например:
pkill python
может завершить не только нужный скрипт, но и другие процессы, у которых имя - python.
Сначала лучше посмотреть, что именно совпадает:
pgrep -a python
У pgrep есть важное отличие: м…
Уже очевидно, что ВАЙБКОДИНГ — главный навык ближайших лет
Посмотрите сами. ИИ уже забирает на себя работу целых команд: пишет код, закрывает задачи джунов и позволяет стартапам запускать продукты в 2–3 раза меньшим составом. То, на что раньше нужны были несколько разработчиков, сегодня всё чаще делает один человек с ИИ-агентами.
И это только начало. Те, кто освоит вайбкодинг сейчас, смогут быстрее запускать проект…
Почему nscd может отдавать старые DNS-ответы
nscd кеширует DNS-ответы, поэтому после изменения записи домена сервер ещё некоторое время может получать старый IP.
Причём TTL DNS и время жизни записи в nscd - не всегда одно и то же.
Проверяем, используется ли nscd:
systemctl status nscd
Состояние кеша:
nscd -g
В выводе интересуют positive hits, negative hits и параметры TTL.
Особенно неприятный случай - negativ…
Claude Opus 5 удалила данные пользователя вместо создания резервной копии
ИИ-агент Anthropic Claude Opus 5 во время запроса «сделать резервную копию на ПК» перепутал путь к каталогу: вместо C:\Users\harih указал /c/Users/harih.
Создав копию не там, где нужно, модель решила удалить ошибочную папку и запустила rm -rf, но применила команду ко всему диску.
«Я попросил Claude Opus 5 создать резервную копию. Вместо этог…
Поиск процессов, которые удерживают deleted-библиотеки
Процесс может продолжать использовать старую версию .so, даже если файл уже удалили или заменили.
Поэтому обновили библиотеку, а сервис фактически продолжает работать со старой.
Проверяем открытые удалённые файлы:
lsof | grep '(deleted)'
Для конкретного процесса:
lsof -p <PID> | grep '(deleted)'
Особенно интересны строки с .so:
app 1842 /usr/lib/libexam…
🔍Тестовое собеседование с Head of DevOps уже завтра
11 августа(уже завтра!) в 19:00 по мск приходи онлайн на открытое собеседование, чтобы посмотреть на настоящее интервью на Middle DevOps-разработчика.
Как это будет:
📂 Александр Хренников, Head of DevOps в KTS с опытом 14+ лет, будет задавать реальные вопросы и задачи разработчику-добровольцу
📂 Александр будет комментировать каждый ответ респондента, чтобы дать по…
💬 Вопрос на собеседовании для DevOps-инженера
Давайте разберем один из частых вопросов, который может быть задан на собеседовании и как на него отвечать.
❓Вопрос: Что такое kernel ftrace и как его используют для диагностики системы?
✅Ответ: ftrace - это встроенный в ядро Linux механизм трассировки, который позволяет отслеживать выполнение функций ядра в реальном времени. Он помогает выявлять узкие места, задержки …
На Stepik запустили мощный курс по «Troubleshooting Docker и Kubernetes: поиск и устранение проблем»
В программе только важные аспекты:
— troubleshooting Docker и образов
— диагностика сетевых проблем
— настройка readiness/liveness probes
— отладка pod’ов, деплоев и ingress
— анализ логов контейнеров и кластера
— разбор ошибок CrashLoopBackOff, OOMKilled, ImagePullBackOff и других
Собеседования на DevOps/SRE сейча…
Когда файловая система тормозит из-за блокировок, а не из-за диска
Высокий iowait - не единственная причина медленной работы файлового сервера.
Иногда диск почти не загружен, но десятки потоков конкурируют за одни и те же inode или directory lock. В итоге CPU простаивает, а задержки операций растут.
Находим процессы, которые больше всего времени проводят в ожидании ядра:
pidstat -w 1
Если количество добровольных…
👍6❤2
Showing the 12 most recent of 31 posts we hold for @admguides. 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.
Polls
The 3 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.
После настройки keepalived оба узла стали MASTER одновременно:
У узлов одинаковый приоритет52%
Версия VRRP разная4%
VRRP пакеты не доходят между узлами33%
Preempt не настроен12%
Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 31 most recent posts we hold, published 28 July 2026 to 12 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Citation-graph rank
Citation-graph rank — 1,042,619 of 1,169,250entries 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Mentions
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Этичный Хакер @hack_less · 227,302 Telegram ranks this channel #33 of 81 here — alongside 80 others — read 12 August 2026
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
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.
“Admin Guides | Сисадмин” (@admguides), 11,830 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/admguides.
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.