Чтобы узнать, какой процесс открыл тот или иной ресурс, например, файл или сетевой порт, можно воспользоваться командой fuser. Например: fuser -va 23/tcp Получим идентификатор процесса, открывшего ТСР порт 23 fuser -va /chroot/etc/resolv.conf Во втором случае получим идентификатор процесса, открывшего файл /chroot/ etc/resolv.conf. Что делать далее - решать вам, например, можно убить этот процесс командой kill.

Channel
Linux для чайника
@os_linux_ru
On this record: Topic · Growth · Engagement · Advertising · Posts · Posts recorded as deleted · Telegram's recommendations · Cite this entry
19,498subscribers
-196 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001301455979 |
|---|---|
| Type | Channel |
| Username | @os_linux_ru |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 21 November 2026 |
| Measurements held | 59 |
| Confirmed unchanged | 1 time, most recently 21 November 2026 |
| On Telegram | t.me/os_linux_ru |
Topic
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 94% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 21 Nov 2026, 08:46 | 19,498 | -14 |
| 17 Nov 2026, 19:45 | 19,512 | -2 |
| 14 Nov 2026, 12:51 | 19,514 | -12 |
| 11 Nov 2026, 16:08 | 19,526 | -10 |
| 9 Nov 2026, 19:08 | 19,536 | -1 |
| 8 Nov 2026, 09:57 | 19,537 | -1 |
| 6 Nov 2026, 00:40 | 19,538 | -4 |
| 5 Nov 2026, 00:04 | 19,542 | +1 |
| 3 Nov 2026, 21:06 | 19,541 | -2 |
| 2 Nov 2026, 23:36 | 19,543 | -7 |
| 1 Nov 2026, 22:05 | 19,550 | -2 |
| 31 Oct 2026, 20:21 | 19,552 | -2 |
| 30 Oct 2026, 20:56 | 19,554 | -3 |
| 30 Oct 2026, 00:27 | 19,557 | +4 |
| 29 Oct 2026, 02:37 | 19,553 | -5 |
| 28 Oct 2026, 02:08 | 19,558 | -1 |
| 27 Oct 2026, 04:26 | 19,559 | -3 |
| 26 Oct 2026, 06:25 | 19,562 | -1 |
| 25 Oct 2026, 07:55 | 19,563 | -8 |
| 23 Oct 2026, 08:46 | 19,571 | first reading |
Engagement
63 posts held, back to 1 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 96 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 14.0%
- avg views ÷ 19,498 subscribers
- Avg views / post
- 2,720
- 19 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 19
- of 63 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.
| Window | Rolling 30 days · latest post in window 20 November 2026 |
|---|---|
| Posts held | 63 (1 July 2026 – 20 November 2026) |
| Views total | 51,700 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 21 Nov 2026, 06:58 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.
Advertising
- Ad load
- 1.59%
- 1 of 63 posts carry an ad marker
- Regulatory tokens
- 1
- posts carrying an erid · 1 distinct token
- Median views · ads
- 3,540
- over 1 measured post
- Median views · rest
- 3,980
- over 62 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.
| erid | Posts | First seen | Last seen |
|---|---|---|---|
| 2VtzqvtXvLa | 1 | 27 July 2026 | 27 July 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 63 most recent posts we hold, published 1 July 2026 to 20 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 19 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
30 приёмов Linux, которые экономят время Если Linux пока кажется сложным, а терминал — местом, где страшно нажать Enter, этот материал для тебя. Если ты уже работаешь и каждый день проводишь в терминале - тоже. Мы собрали 30 приёмов Linux, которые экономят время. Простыми словами: как быстрее делать рутину, как не паниковать, когда что-то сломалось, и как не наступить на грабли, на которые уже наступали другие. Ест…
Несколько примеров настроек ядра Linux: /proc/sys/kernel/panic: Этот параметр определяет время задержки перед автоматической перезагрузкой системы после возникновения фатальной ошибки (паники) ядра. Значение в секундах. Например, чтобы установить время задержки в 10 секунд, выполните команду: echo 10 > /proc/sys/kernel/panic /proc/sys/kernel/sysrq: Этот параметр определяет, разрешены ли команды SysRq (System Reques…
Подсчитаем количество файлов в директории Напишем команду, которая подсчитает количество всех файлов в директории /path/to/directory. Пример: find /path/to/directory -type f | wc -l Команда find ищет все файлы (-type f) в указанной директории и ее поддиректориях, а wc -l подсчитывает количество строк, что соответствует количеству найденных файлов.
💻 Как менять параметры модуля ядра без пересборки? 24 ноября в 20:00 на открытом уроке разберём, как управлять параметрами модуля ядра Linux через sysfs без лишних действий. На примере простого модуля на C посмотрим, как параметр из кода появляется в /sys/module/<имя_модуля>/parameters/, как его читать и изменять из командной строки. Разберём: — module_param() и права доступа; — параметры при загрузке модуля и изм…
Поиск и замена текста в файлах Скрипт ищет и заменяет текст "foo" на "bar" во всех текстовых файлах в текущем каталоге. #!/bin/bash for file in *.txt; do sed -i 's/foo/bar/g' "$file" done for file in *.txt; do — перебирает все текстовые файлы в текущем каталоге. sed -i 's/foo/bar/g' "$file" — использует sed для замены "foo" на "bar" во всех найденных файлах.
cgroups для ограничения ресурсов процессов в Linux Control Groups (cgroups) — функциональность ядра Linux, которая позволяет ограничивать и управлять ресурсами (такими как процессорное время, память, дисковое I/O и т.д.) для групп процессов. Установка и настройка cgroups: Проверка наличия cgroups: Убедитесь, что ваш дистрибутив Linux поддерживает cgroups: ls /sys/fs/cgroup/ Если каталог существует и содержит подк…
Управление буфером обмена из командной строки Буфер обмена — непостоянное хранилище на вашем компьютере данных, которые пользователь хочет скопировать с одного пути на другой. Xclip — отличный инструмент, который используется в качестве буфера обмена. Устанавливаем Xclip в Ubuntu: sudo apt install xclip Примеры использования: Предположим, вы хотите скопировать имя любого веб-сайта в буфер обмена, а затем, позже, …
Открытые драйверы Open Source Drivers — драйверы, разработанные сообществом или производителями с открытым исходным кодом, которые интегрируются в ядро Linux и поддерживаются сообществом разработчиков. Они часто являются лучшим выбором для пользователей Linux благодаря их стабильности, прозрачности и оптимальной интеграции с системой. Устройства, которые лучше всего работают с Open Source драйверами: - Графические …
Проверка поддержки устройства в ядре Linux Когда подключаем новое устройство к Linux, важно убедиться, что оно будет корректно работать с системой. Одним из шагов в этом процессе является проверка, поддерживает ли устройство ядро Linux. Для того чтобы узнать, поддерживает ли устройство ядро, используем команду lspci -nnk, которая покажет информацию о подключенных устройствах и драйверах: lspci -nnk | grep -A3 -i <т…
Раздел удалён, логический диск пропал, структура LVM повреждена. С чего начать восстановление и как не усугубить ситуацию первыми действиями? В такой момент важно понимать, какие метаданные пострадали и как устроено хранение данных. 19 ноября в 20:00 на открытом уроке курса «Инфраструктура высоконагруженных систем» разберёте восстановление MBR, GPT и LVM после критических сбоев. Рассмотрите, как операционная систем…
Управляем Bluetooth-устройствами в Linux с помощью bluetoothctl bluetoothctl — стандартная консольная утилита для управления Bluetooth в Linux. Она входит в пакет bluez и установлена в большинстве дистрибутивов по умолчанию. Запуск Открываем терминал и запускаем утилиту: bluetoothctl После этого мы попадаем в интерактивный режим — приглашение изменится на [bluetooth]#. Все дальнейшие команды вводятся уже без префик…
Showing the 12 most recent of 63 posts we hold for @os_linux_ru. 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.
Posts recorded as deleted after publishing
We recorded 3 posts on @os_linux_ru as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.
A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.
- First seen missing
- 14 August 2026
- Most recent seen missing
- 19 November 2026
- Median time before seen missing
- 2 days
- Seen missing in the last 30 days
- 1
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
@linux_sup · 7,353#1
@bashdays · 23,600#2
@sysadmin_library · 25,649#3
@devops_sc · 14,810#4
@linux_education · 11,025#5
@Social_engineering · 124,611#6
@admguides · 12,062#7
@it_boooks · 47,332#8
@it_secur · 63,745#9
@sysodmins_league · 13,368#10
@srv_admin · 32,691#11
@bash_help · 8,770#12
@linuxkalii · 55,861#13
@linuxacademiya · 28,652#14
@networkadm · 12,343#15
@school_network · 26,360#16
@linux_gram · 13,961#17
@i_odmin · 26,703#18
@ITKB_channel · 8,041#19
@krxnotes · 2,205#20
@bzd_channel · 36,183#21
@linuxcamp_tg · 13,413#22
@i_odmin_book · 18,782#23
@itbook_library · 15,886#24
@haccking · 63,009#25
@pylinux0 · 11,048#26
@usr_bin_linux · 5,003#27
@the_algorithms · 8,226#28
@developer_shelf · 26,696#29
@sysadminof · 14,253#30
@sysodmins · 41,235#31
@gitgate · 6,792#32
@IT_obrazovach · 6,754#33
@i_DevOps · 8,859#34
@dev_ops_info · 2,185#35
@interface31 · 9,085#36
@knijnoe_xranilishe · 19,476#37
@code_library · 17,542#38
@IT_Portal · 118,729#39
@databases_secrets · 29,979#40
@codeby_sec · 37,082#41
@winitpro_ru · 9,370#42
@bezopasno_soft · 29,589#43
@Selectel · 62,334#44
@DevOPSitsec · 23,873#45
@devopsslib · 10,322#46
@devopseri · 2,670#47
@linuxdevs · 3,807#48
@code_m0de · 10,740#49
@juniorlinux · 3,058#50
@devops_memops · 6,601#51
@seniorpy · 39,004#52
@open_source_friend · 52,755#53
@S_E_Reborn · 22,447#54
@black_triangle_tg · 63,982#55
@the_winda · 5,987#56
@S_E_Book · 23,080#57
@github · 155,143#58
@habr_com · 134,920#59
@CScience1 · 7,670#60
@plafonyoutube · 9,064#61
@elliot_cybersec · 38,828#62
@SecLabNews · 86,790#63
@opennet_ru · 16,468#64
@mediatrends · 602,084#65
@devopsina · 23,556#66
@osint_pythons · 36,436#67
@dataleak · 117,440#68
@monitorim_it · 8,596#69
@codecamp · 177,161#70
@itmemes · 121,781#71
@xakep_ru · 40,378#72
@worlditech · 7,257#73
@bugfeature · 547,298#74
@prog_lib_eng · 2,662#75
@tg_infosec · 26,815#76
@iscode · 5,725#77
@proglibrary · 77,413#78
@python2day · 63,245#79
@rebrain_devops · 28,690#80
@book_academ · 21,316#81
@tproger · 77,974#82
@SysadminNotes · 12,232#83
@exploitex · 2,016,103#84
@physics_lib · 146,667#85
@yaplakal · 419,637#86
@EnglishScript · 44,214#87
Read from Telegram’s recommendation API, most recently 1 October 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
@sysadmin_library · 25,649
Telegram ranks this channel #9 of 85 here — alongside 84 others — read 13 September 2026
@linuxacademiya · 28,652
Telegram ranks this channel #18 of 84 here — alongside 83 others — read 9 September 2026
@bashdays · 23,600
Telegram ranks this channel #21 of 94 here — alongside 93 others — read 18 September 2026
@databases_secrets · 29,979
Telegram ranks this channel #26 of 82 here — alongside 81 others — read 7 September 2026
@school_network · 26,360
Telegram ranks this channel #31 of 85 here — alongside 84 others — read 12 September 2026
@i_odmin_book · 18,782
Telegram ranks this channel #32 of 83 here — alongside 82 others — read 5 October 2026
@termuxplz0x41 · 32,414
Telegram ranks this channel #36 of 54 here — alongside 53 others — read 4 September 2026
@bzd_channel · 36,183
Telegram ranks this channel #38 of 57 here — alongside 56 others — read 1 September 2026
@i_odmin · 26,703
Telegram ranks this channel #41 of 89 here — alongside 88 others — read 12 September 2026
@linuxkalii · 55,861
Telegram ranks this channel #41 of 89 here — alongside 88 others — read 23 August 2026
@knijnoe_xranilishe · 19,476
Telegram ranks this channel #42 of 73 here — alongside 72 others — read 30 September 2026
@device24 · 21,241
Telegram ranks this channel #42 of 52 here — alongside 51 others — read 23 September 2026
@Selectel · 62,334
Telegram ranks this channel #42 of 96 here — alongside 95 others — read 21 August 2026
@developer_shelf · 26,696
Telegram ranks this channel #43 of 63 here — alongside 62 others — read 11 September 2026
@procode404 · 39,987
Telegram ranks this channel #48 of 83 here — alongside 82 others — read 30 August 2026
@pcTeapot · 39,293
Telegram ranks this channel #49 of 53 here — alongside 52 others — read 30 August 2026
@srv_admin · 32,691
Telegram ranks this channel #53 of 96 here — alongside 95 others — read 5 September 2026
@pythonist24 · 55,035
Telegram ranks this channel #55 of 88 here — alongside 87 others — read 23 August 2026
@EnglishScript · 44,214
Telegram ranks this channel #69 of 82 here — alongside 81 others — read 27 August 2026
@cmd_it · 24,019
Telegram ranks this channel #72 of 82 here — alongside 81 others — read 16 September 2026
@python_secrets · 40,230
Telegram ranks this channel #73 of 82 here — alongside 81 others — read 30 August 2026
@osint_pythons · 36,436
Telegram ranks this channel #81 of 84 here — alongside 83 others — read 1 September 2026
This channel appears in 22 seed channels' Telegram-generated recommendation lists 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 21 November 2026 — this entry's latest reading, not the date you are reading this.
“Linux для чайника” (@os_linux_ru), 19,498 subscribers as measured 21 November 2026. Telegram Register, tgregister.com/channel/os_linux_ru.
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.