This manual page describes how to manage kresd using systemd units.
QUICKSTARTsystemctlstartkresd@1 - single instance of kresd, responding on localhost
CONCURRENTDAEMONSkresd daemon can be executed in multiple independent processes, which are managed with systemd via
systemd templates (see systemd.unit(5)). Each systemd service instance of kresd (kresd@.service)
represents a single, independent kresd process.
If you have more than one CPU core available, a single running kresd daemon will only be able to make use
of one core at a time, leaving the other cores idle. If you want kresd to take advantage of all
available cores, while sharing both cache and sockets, you should enable and start as many instances of
the kresd@.service as you have cores. Typically, each instance is just named kresd@N.service, where N is
a decimal number. For example, to enable and start 3 concurrent daemons:
systemctlenable--nowkresd@1.servicekresd@2.servicekresd@3.service
The systemd-managed kresd service set is grouped in the system-kresd.slice slice. The slice includes all
running daemons (instances of kresd@.service).