Directives for the selected non-service unit type. Enter directives only, without the section header; the correct section will be written, such as [Timer], [Socket], [Path], [Mount], [Automount], [Swap], or [Slice].

Mount and automount units have dedicated fields for their common settings. Use this field only for uncommon directives that are not shown elsewhere in the form.

For a timer, examples include OnCalendar=daily, Persistent=true, and Unit=myjob.service. If Unit= is omitted, systemd activates the service with the same base name, such as myjob.service for myjob.timer.

For a socket, examples include ListenStream=8080, ListenStream=/run/myapp.sock, Accept=false, and Service=myapp.service. For user units, filesystem socket paths should be below a location the selected user can write, such as /run/user/UID. If Service= is omitted, systemd uses the service with the same base name.

For a path unit, examples include PathChanged=/srv/myapp, PathExists=/var/run/myapp.ready, and Unit=myjob.service. For user units, watched paths should normally be below the selected user's home directory or runtime directory.

Target units do not need a type-specific settings body in this form. Dependencies such as Wants=, Requires=, Before=, and After= are set in the common advanced options.

For a swap unit, examples include What=/swapfile and Priority=10. For a slice unit, use the dedicated fields for CPU weight, memory maximum, task maximum, and I/O weight; this field can be used for additional resource controls such as CPUQuota=50% or MemoryHigh=256M. For user units, slice resource controls apply only within the selected user's systemd manager.