linuxlab.io
Tutorials▾
  • Linux & networking
    File system, processes, TCP/IP, BGP and OSPF
    →
  • Terraform & IaC
    HCL, state, plan/apply on a LocalStack sandbox
    →
  • Git & GitHub
    Object model, plumbing, branching, GitHub Actions
    →
All tutorials →
PricingAboutSign inCreate account
/
  • Введение
  • Уроки
  • How it works
  • Симулятор
  • База знаний
  • Собеседование
Lessons
Footer
linuxlab-TutorialsPricingAboutPrivacy & cookies
Copyright © 2026 LinuxLab. All rights reserved.

← из прошлого урока

You saw that every user has a UID and that sudo lets you become root. Now: what lives inside that UID, namely processes. They have their own PIDs and parents, and they can talk to each other with signals.

← к прошлому уроку

Базовый

Processes and signals: ps, kill, jobs

12 мин · урок входит в курс «Базовый»

Every command is a process-and-pid. A process has a PID (a numeric identifier), a parent (PPID), a status, an owner, and a set of open files. Managing processes means managing their lifecycle through signals: TERM (a request to terminate, which the process can handle), KILL (an immediate kill that cannot be handled), HUP, INT (Ctrl+C), and others.

Урок закрыт

Чтобы запустить sandbox и пройти этот урок целиком, нужен соответствующий курс. Внутри - ещё много практических уроков того же уровня и сквозной прогресс.

Купить курсВойти← Все уроки

дальше →

Processes exist, but how do you tell when the system is overloaded by them? Next: load average and the three numbers in uptime that people usually look at first when a machine feels "slow".

Открыть превью: Load average: what the three numbers meanв курсе «Базовый» - /pricing
Footer
linuxlab-
Copyright © 2026 LinuxLab. All rights reserved.
Tutorials
Pricing
About
Privacy & cookies