util-linux/misc-utils/uuidd.service.in

[Unit]
Description=Daemon for generating UUIDs
Documentation=man:uuidd(8)
Requires=uuidd.socket

[Service]
ExecStart=@usrsbin_execdir@/uuidd --socket-activation
Restart=no
User=uuidd
Group=uuidd

[Install]
Also=uuidd.socket
uuidd: add systemd unit files Add systemd unit files which use the socket activation mechanism of systemd. The uuidd deamon is started upon first request on the socket and quits after 1 minute of inactivity. Signed-off-by: Petr Uzel <petr.uzel@suse.cz> 2012-05-03 14:01:58 -05:00			`[Unit]`
			`Description=Daemon for generating UUIDs`
uuidd: Add Documentation key to uuidd.service 2018-11-12 12:39:45 -06:00			`Documentation=man:uuidd(8)`
uuidd: add systemd unit files Add systemd unit files which use the socket activation mechanism of systemd. The uuidd deamon is started upon first request on the socket and quits after 1 minute of inactivity. Signed-off-by: Petr Uzel <petr.uzel@suse.cz> 2012-05-03 14:01:58 -05:00			`Requires=uuidd.socket`

			`[Service]`
uuidd: remove timeout from systemd service file It seems that SAP does not like the timeout, for performance is better to keep the daemon permanently running. This is no problem because uuidd is used only on systems with very unusual requirements to UUID. Addresses: https://bugzilla.redhat.com/show_bug.cgi?id=1092039 Signed-off-by: Karel Zak <kzak@redhat.com> 2014-04-29 03:37:26 -05:00			`ExecStart=@usrsbin_execdir@/uuidd --socket-activation`
uuidd: add systemd unit files Add systemd unit files which use the socket activation mechanism of systemd. The uuidd deamon is started upon first request on the socket and quits after 1 minute of inactivity. Signed-off-by: Petr Uzel <petr.uzel@suse.cz> 2012-05-03 14:01:58 -05:00			`Restart=no`
			`User=uuidd`
			`Group=uuidd`
uuidd: improve systemd unit files - use $usrsbin_execdir - add [Install] section - use long options Signed-off-by: Karel Zak <kzak@redhat.com> 2012-08-15 09:06:19 -05:00
			`[Install]`
			`Also=uuidd.socket`