[arch-general] Services with DefaultDependencies=no

Eli Schwartz eschwartz at archlinux.org
Mon Aug 27 16:51:13 UTC 2018

On 8/27/18 8:45 AM, Leonid Isaev via arch-general wrote:
> Hi,
> 	While going over .service files on my system, I noticed that quite a
> few of them, not belonging to systemd package, contain DefaultDependencies=no
> (DD=no). This is understandable (perhaps) for programs like systemd-journald,
> but what about normal daemons, like rpcbind, haveged and rpc-nfsd? I thought
> that setting DD=no is kind of a hack needed only for special services (e.g.
> called from fstab via x-systemd.requires=). Or am I missing something?

DefaultDependencies=false means it won't get "ensure that the service is
started only after basic system initialization is completed and is
properly terminated on system shutdown." (from the systemd.unit(5) man

Seems like a reasonable thing to want to avoid for programs that are
meant to be started as part of initializing the system.

e.g. you might want RPC daemons running as soon as possible. You most
likely do want haveged running as soon as possible.

Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20180827/e34c5d64/attachment-0001.asc>

More information about the arch-general mailing list