Review Glossary FR

Size

Eyes

Finish a part in any dojo to unlock the next eyes.

Know what the kernel is doing to your app.

Symptoms like exit code 137 or a full disk with free space, traced to the kernel code or the man page that explains them.

Today · day 1 · 10 min

How a process starts
Start reading →

0 of 40 chapters done

Processes: 0 of 8Memory: 0 of 8Files and disks: 0 of 8The running system: 0 of 8Containers from the kernel up: 0 of 8
One pillar per part. It fills as you finish its chapters.

The path

Processes: 0 of 8Processes

  1. How a process starts 1
  2. Signals 2
  3. PID 1 in a container 3
  4. Exit codes 4
  5. File descriptors 5
  6. Load average and the scheduler 6
  7. Watching system calls with strace 7
  8. Reading /proc 8

Memory: 0 of 8Memory

  1. Virtual memory 9
  2. The page cache 10
  3. The OOM killer 11
  4. Swap 12
  5. Memory limits in containers 13
  6. mmap 14
  7. Huge pages 15
  8. Finding a memory leak 16

Files and disks: 0 of 8Files and disks

  1. Inodes and links 17
  2. Permissions beyond rwx 18
  3. Filesystems and journaling 19
  4. fsync and durability 20
  5. A full disk with free space 21
  6. Disk I/O and iostat 22
  7. Mounts and mount options 23
  8. Disks, partitions and LVM 24

The running system: 0 of 8The running system

  1. How Linux boots 25
  2. systemd units 26
  3. Timers instead of cron 27
  4. The journal 28
  5. Users, groups and sudo 29
  6. Packages 30
  7. Kernel parameters 31
  8. Clocks and NTP 32

Containers from the kernel up: 0 of 8Containers from the kernel up

  1. Namespaces 33
  2. cgroups v2 34
  3. CPU limits and throttling 35
  4. Capabilities 36
  5. seccomp 37
  6. Image layers and overlayfs 38
  7. eBPF in practice 39
  8. A slow server in 60 seconds 40