From Fedora Project Wiki
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
= systemd = | = systemd = | ||
'''systemd''' is the new system and service manager for Fedora 15. It provides: <!-- explain better --> | '''systemd''' is the new system and service manager for Fedora 15. It provides: <!-- explain better --> | ||
* aggressive parallelization capabilities using socket | * '''aggressive parallelization capabilities using socket''': to speed up the entire boot and start more processes in parallel, systemd creates the listening sockets before actually starting the daemon, and then just passes the socket to it. All sockets for all daemons are created in one step in the init system, and then in a second step run all daemons at once. If a service needs another, and it is not fully started up, what will happen is that the connection is queued in the providing service and the client will potentially block on that single request. But only that one client will block and only on that one request. Also, dependencies between services no longer have to be configured to allow proper parallelized start-up: starting all sockets at once and a service needing another, it surely can connect to its socket. | ||
* D-Bus activation for starting services | * D-Bus activation for starting services | ||
* offers on-demand starting of daemons | * offers on-demand starting of daemons | ||
Revision as of 17:23, 31 January 2011
Beat is open
This beat is now ready to have Fedora 25 content added by the beat writer
This beat is now ready to have Fedora 25 content added by the beat writer
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page. Feel free to improve it. TY
It is still under construction and content may change. Do not rely on the information on this page. Feel free to improve it. TY
systemd
systemd is the new system and service manager for Fedora 15. It provides:
- aggressive parallelization capabilities using socket: to speed up the entire boot and start more processes in parallel, systemd creates the listening sockets before actually starting the daemon, and then just passes the socket to it. All sockets for all daemons are created in one step in the init system, and then in a second step run all daemons at once. If a service needs another, and it is not fully started up, what will happen is that the connection is queued in the providing service and the client will potentially block on that single request. But only that one client will block and only on that one request. Also, dependencies between services no longer have to be configured to allow proper parallelized start-up: starting all sockets at once and a service needing another, it surely can connect to its socket.
- D-Bus activation for starting services
- offers on-demand starting of daemons
- keeps track of processes using Linux cgroups
- supports snapshotting and restoring of the system state
- maintains mount and automount points
- implements an elaborate transactional dependency-based service control logic.
It can work as a drop-in replacement for sysvinit.
It is implemented around the notion of units. Units have a name and a type, whose configuration is in a file with the same name. There are several kinds of units: service, socket, device, others.