systemd support for various packages
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 38 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 38 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 00/38] systemd support for various packages
Quoted 7 lines · Alex Suykov
This set adds systemd support to packages that install sysv initscripts but not systemd services. The idea is that the choice between
BR2_INIT_SYSVandBR2_INIT_SYSTEMDshould affect the process list in the resulting system as little as possible.All services start foreground processes (Type=simple), and follow current initscripts otherwise whenever possible.
Type=simple is not necessarily the best way to do this. Handling errors is done differently by systemd with Type=simple vs Type=forking.
A recent blog post by Lucas Nussbaum has more details:
http://www.lucas-nussbaum.net/blog/?p=877
With Type=simple, systemd considers the service started right after executing it. It will not flag errors on startup if the process exits soon after due to a config error, etc. With Type=forking, systemd will only consider the service started after the parent exits. As many daemons will check config files and command line args before forking, these errors will be detected and propagated to systemd.