Systemd: why you should care as a Python developer
summary
Shows concrete systemd moves a Python app can use: use socket activation so systemd listens and passes file descriptors, spawn transient units instead of subprocesses, and control isolation with private /tmp and read-only or mounted paths. Demonstrates Python binding piston D to create and inspect units, sets cgroup limits (about 20% CPU, 10 MB RAM, five-task limit), starts services and batch jobs, and proves these replace shell scripts and work in live demos.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:36Service Manager
- 2:19Before Systemd
- 3:29Systemd
- 4:33What makes Systemd different
- 8:40Template
- 10:00Socket activation
- 14:20Systemd library
- 15:23Systemd demo
- 20:06Options
related talks
36mSystemd, from /dev/null to root
22mWhat's new in systemd in 2016?
04h 16mDay 2 - Room 1 Session 2
58mLogging with systemd in the Raspberry Pi Cluster
54mSystemd-Nspawn is Chroot on Steroids
30mHow To Build a Python Microservice Without Losing a Job
38mWe Need to Talk About Systemd: Boot Time Optimization for the New init daemon
30mAn Admin's Cornucopia - Python Is More Than Just A Better Bash