Note that currently Type=notify will not work if used in combination with PrivateNetwork=yes.īehavior of idle is very similar to simple however, actual execution of the service binary is delayed until all jobs are dispatched. If NotifyAccess= is not set, it will be implicitly set to main. If this option is used, NotifyAccess= (see below) should be set to open access to the notification socket provided by systemd.
systemd will proceed with starting follow-up units after this notification message has been sent.
This type is the default if BusName= is specified.īehavior of notify is similar to simple however, it is expected that the daemon sends a notification message via sd_notify(3) or an equivalent call when it has finished starting up. Service units with this option configured implicitly gain dependencies on the dbus.socket unit. systemd will proceed with starting follow-up units after the D-Bus bus name has been acquired. RemainAfterExit= is particularly useful for this type of service.īehavior of dbus is similar to simple however, it is expected that the daemon acquires a name on the D-Bus bus, as configured by BusName=. systemd will proceed with starting follow-up units as soon as the parent process exits.īehavior of oneshot is similar to simple however, it is expected that the process has to exit before systemd starts follow-up units. If this setting is used, it is recommended to also use the PIDFile= option, so that systemd can identify the main process of the daemon.
This is the behavior of traditional UNIX daemons. The child continues to run as the main daemon process. The parent process is expected to exit when start-up is complete and all communication channels are set up. If set to forking, it is expected that the process configured with ExecStart= will call fork() as part of its start-up. sockets set up by systemd, via socket activation), as systemd will immediately proceed starting follow-up units. In this mode, if the process offers functionality to other processes on the system, its communication channels should be installed before the daemon is started up (e.g. If set to simple (the default value if neither Type= nor BusName= are specified), it is expected that the process configured with ExecStart= is the main process of the service. One of simple, forking, oneshot, dbus, notify or idle. The section is in man rviceĬonfigures the process start-up type for this service unit. Trying to understand more of systemd is of course very useful. Defining wrong type will simply result in failure to start service.Īs I tried t o explain in my post: I found this somewhere. This depends on how daemon is implemented.
0 kommentar(er)
