{ "content": [ { "type": "text", "text": "# systemd(1) (man)\n\n## TLDR\n\n- To display process startup time::\n `systemd-analyze`\n- To display process startup time at service level::\n `systemd-analyze blame`\n- To list running units::\n `systemctl list-units`\n- To load a unit at startup::\n `systemctl enable foo.service`\n- To start or Stop a unit::\n `systemctl <start | stop> foo.service`\n- To unit file locations::\n `/etc/systemd/system`\n\n*Source: cheat.sh*\n\n---\n\n**Summary:** systemd, init - systemd system and service manager\n\n**Synopsis:** /lib/systemd/systemd [OPTIONS...]\ninit [OPTIONS...] {COMMAND}\n\n## Flags\n\n| Flag | Long | Arg | Description |\n|------|------|-----|-------------|\n| — | --dump-configuration-items | — | Dump understood unit configuration items. This outputs a terse but complete list of configuration items understood in un |\n| — | --dump-bus-properties | — | Dump exposed bus properties. This outputs a terse but complete list of properties exposed on D-Bus. |\n| — | --test | — | Determine the initial start-up transaction (i.e. the list of jobs enqueued at start-up), dump it and exit — without actu |\n| -h | --help | — | Print a short help text and exit. |\n| — | --version | — | Print a short version string and exit. |\n| — | — | — | Set default unit to activate on startup. If not specified, defaults to default.target. See systemd.unit= above. |\n| — | --dump-core | — | Enable core dumping on crash. This switch has no effect when running as user instance. Same as systemd.dumpcore= above. |\n| — | --crash-shell | — | Run a shell on crash. This switch has no effect when running as user instance. See systemd.crashshell= above. |\n| — | --crash-reboot | — | Automatically reboot the system on crash. This switch has no effect when running as user instance. See systemd.crashrebo |\n| — | --confirm-spawn | — | Ask for confirmation when spawning processes. This switch has no effect when run as user instance. See systemd.confirmsp |\n| — | --show-status | — | Show terse unit status information on the console during boot-up and shutdown. See systemd.showstatus above. |\n| — | --log-color | — | Highlight important log messages. See systemd.logcolor above. |\n| — | — | — | Set log level. See systemd.loglevel above. |\n| — | --log-location | — | Include code location in log messages. See systemd.loglocation above. |\n| — | — | — | Set log target. See systemd.logtarget above. |\n| — | — | — | Prefix console messages with timestamp. See systemd.logtime above. |\n| — | — | — | Override the machine-id set on the hard drive. See systemd.machineid= above. |\n| — | --service-watchdogs | — | Globally enable/disable all service watchdog timeouts and emergency actions. See systemd.servicewatchdogs above. --defau |\n\n## See Also\n\n- systemd-system.conf(5)\n- locale.conf(5)\n- systemctl(1)\n- journalctl(1)\n- systemd-notify(1)\n- daemon(7)\n- sd-daemon(3)\n- org.freedesktop.systemd1(5)\n- systemd.unit(5)\n- systemd.special(7)\n- pkg-config(1)\n- kernel-command-line(7)\n- bootup(7)\n- systemd.directives(7)\n\n## Section Outline\n\n- **NAME** (2 lines)\n- **SYNOPSIS** (4 lines)\n- **DESCRIPTION** (18 lines)\n- **CONCEPTS** (155 lines)\n- **DIRECTORIES** (30 lines)\n- **SIGNALS** (40 lines) — 17 subsections\n - SIGRTMIN+0 (3 lines)\n - SIGRTMIN+1 (3 lines)\n - SIGRTMIN+2 (3 lines)\n - SIGRTMIN+3 (3 lines)\n - SIGRTMIN+4 (3 lines)\n - SIGRTMIN+5 (3 lines)\n - SIGRTMIN+6 (3 lines)\n - SIGRTMIN+13 (2 lines)\n - SIGRTMIN+14 (2 lines)\n - SIGRTMIN+15 (2 lines)\n - SIGRTMIN+16 (2 lines)\n - SIGRTMIN+20 (3 lines)\n - SIGRTMIN+21 (3 lines)\n - SIGRTMIN+22 (3 lines)\n - SIGRTMIN+23 (5 lines)\n - SIGRTMIN+24 (2 lines)\n - SIGRTMIN+26 (10 lines)\n- **ENVIRONMENT** (133 lines)\n- **KERNEL COMMAND LINE** (147 lines)\n- **OPTIONS** (5 lines) — 20 subsections\n - Introspection and debugging options (3 lines)\n - --dump-configuration-items (3 lines)\n - --dump-bus-properties (3 lines)\n - --test (18 lines)\n - -h --help (2 lines)\n - --version (2 lines)\n - Options that duplicate kernel command line settings (13 lines)\n - --unit= (3 lines)\n - --dump-core (8 lines)\n - --crash-shell (3 lines)\n - --crash-reboot (3 lines)\n - --confirm-spawn (3 lines)\n - --show-status (3 lines)\n - --log-color (2 lines)\n - --log-level= (2 lines)\n - --log-location (2 lines)\n - --log-target= (2 lines)\n - --log-time= (2 lines)\n - --machine-id= (2 lines)\n - --service-watchdogs (7 lines)\n- **SOCKETS AND FIFOS** (14 lines)\n- **SEE ALSO** (5 lines)\n- **NOTES** (38 lines)\n\n## Full Content\n\n### NAME\n\nsystemd, init - systemd system and service manager\n\n### SYNOPSIS\n\n/lib/systemd/systemd [OPTIONS...]\n\ninit [OPTIONS...] {COMMAND}\n\n### DESCRIPTION\n\nsystemd is a system and service manager for Linux operating systems. When run as first\nprocess on boot (as PID 1), it acts as init system that brings up and maintains userspace\nservices. Separate instances are started for logged-in users to start their services.\n\nsystemd is usually not invoked directly by the user, but is installed as the /sbin/init\nsymlink and started during early boot. The user manager instances are started automatically\nthrough the user@.service(5) service.\n\nFor compatibility with SysV, if the binary is called as init and is not the first process on\nthe machine (PID is not 1), it will execute telinit and pass all command line arguments\nunmodified. That means init and telinit are mostly equivalent when invoked from normal login\nsessions. See telinit(8) for more information.\n\nWhen run as a system instance, systemd interprets the configuration file system.conf and the\nfiles in system.conf.d directories; when run as a user instance, systemd interprets the\nconfiguration file user.conf and the files in user.conf.d directories. See systemd-\nsystem.conf(5) for more information.\n\n### CONCEPTS\n\nsystemd provides a dependency system between various entities called \"units\" of 11 different\ntypes. Units encapsulate various objects that are relevant for system boot-up and\nmaintenance. The majority of units are configured in unit configuration files, whose syntax\nand basic set of options is described in systemd.unit(5), however some are created\nautomatically from other configuration files, dynamically from system state or\nprogrammatically at runtime. Units may be \"active\" (meaning started, bound, plugged in, ...,\ndepending on the unit type, see below), or \"inactive\" (meaning stopped, unbound, unplugged,\n...), as well as in the process of being activated or deactivated, i.e. between the two\nstates (these states are called \"activating\", \"deactivating\"). A special \"failed\" state is\navailable as well, which is very similar to \"inactive\" and is entered when the service failed\nin some way (process returned error code on exit, or crashed, an operation timed out, or\nafter too many restarts). If this state is entered, the cause will be logged, for later\nreference. Note that the various unit types may have a number of additional substates, which\nare mapped to the five generalized unit states described here.\n\nThe following unit types are available:\n\n1. Service units, which start and control daemons and the processes they consist of. For\ndetails, see systemd.service(5).\n\n2. Socket units, which encapsulate local IPC or network sockets in the system, useful for\nsocket-based activation. For details about socket units, see systemd.socket(5), for\ndetails on socket-based activation and other forms of activation, see daemon(7).\n\n3. Target units are useful to group units, or provide well-known synchronization points\nduring boot-up, see systemd.target(5).\n\n4. Device units expose kernel devices in systemd and may be used to implement device-based\nactivation. For details, see systemd.device(5).\n\n5. Mount units control mount points in the file system, for details see systemd.mount(5).\n\n6. Automount units provide automount capabilities, for on-demand mounting of file systems as\nwell as parallelized boot-up. See systemd.automount(5).\n\n7. Timer units are useful for triggering activation of other units based on timers. You may\nfind details in systemd.timer(5).\n\n8. Swap units are very similar to mount units and encapsulate memory swap partitions or\nfiles of the operating system. They are described in systemd.swap(5).\n\n9. Path units may be used to activate other services when file system objects change or are\nmodified. See systemd.path(5).\n\n10. Slice units may be used to group units which manage system processes (such as service and\nscope units) in a hierarchical tree for resource management purposes. See\nsystemd.slice(5).\n\n11. Scope units are similar to service units, but manage foreign processes instead of\nstarting them as well. See systemd.scope(5).\n\nUnits are named as their configuration files. Some units have special semantics. A detailed\nlist is available in systemd.special(7).\n\nsystemd knows various kinds of dependencies, including positive and negative requirement\ndependencies (i.e. Requires= and Conflicts=) as well as ordering dependencies (After= and\nBefore=). NB: ordering and requirement dependencies are orthogonal. If only a requirement\ndependency exists between two units (e.g. foo.service requires bar.service), but no ordering\ndependency (e.g. foo.service after bar.service) and both are requested to start, they will\nbe started in parallel. It is a common pattern that both requirement and ordering\ndependencies are placed between two units. Also note that the majority of dependencies are\nimplicitly created and maintained by systemd. In most cases, it should be unnecessary to\ndeclare additional dependencies manually, however it is possible to do this.\n\nApplication programs and units (via dependencies) may request state changes of units. In\nsystemd, these requests are encapsulated as 'jobs' and maintained in a job queue. Jobs may\nsucceed or can fail, their execution is ordered based on the ordering dependencies of the\nunits they have been scheduled for.\n\nOn boot systemd activates the target unit default.target whose job is to activate on-boot\nservices and other on-boot units by pulling them in via dependencies. Usually, the unit name\nis just an alias (symlink) for either graphical.target (for fully-featured boots into the UI)\nor multi-user.target (for limited console-only boots for use in embedded or server\nenvironments, or similar; a subset of graphical.target). However, it is at the discretion of\nthe administrator to configure it as an alias to any other target unit. See\nsystemd.special(7) for details about these target units.\n\nsystemd only keeps a minimal set of units loaded into memory. Specifically, the only units\nthat are kept loaded into memory are those for which at least one of the following conditions\nis true:\n\n1. It is in an active, activating, deactivating or failed state (i.e. in any unit state\nexcept for \"inactive\")\n\n2. It has a job queued for it\n\n3. It is a dependency of at least one other unit that is loaded into memory\n\n4. It has some form of resource still allocated (e.g. a service unit that is inactive but\nfor which a process is still lingering that ignored the request to be terminated)\n\n5. It has been pinned into memory programmatically by a D-Bus call\n\nsystemd will automatically and implicitly load units from disk — if they are not loaded yet —\nas soon as operations are requested for them. Thus, in many respects, the fact whether a unit\nis loaded or not is invisible to clients. Use systemctl list-units --all to comprehensively\nlist all units currently loaded. Any unit for which none of the conditions above applies is\npromptly unloaded. Note that when a unit is unloaded from memory its accounting data is\nflushed out too. However, this data is generally not lost, as a journal log record is\ngenerated declaring the consumed resources whenever a unit shuts down.\n\nProcesses systemd spawns are placed in individual Linux control groups named after the unit\nwhich they belong to in the private systemd hierarchy. (see cgroups.txt[1] for more\ninformation about control groups, or short \"cgroups\"). systemd uses this to effectively keep\ntrack of processes. Control group information is maintained in the kernel, and is accessible\nvia the file system hierarchy (beneath /sys/fs/cgroup/systemd/), or in tools such as systemd-\ncgls(1) or ps(1) (ps xawf -eo pid,user,cgroup,args is particularly useful to list all\nprocesses and the systemd units they belong to.).\n\nsystemd is compatible with the SysV init system to a large degree: SysV init scripts are\nsupported and simply read as an alternative (though limited) configuration file format. The\nSysV /dev/initctl interface is provided, and compatibility implementations of the various\nSysV client tools are available. In addition to that, various established Unix functionality\nsuch as /etc/fstab or the utmp database are supported.\n\nsystemd has a minimal transaction system: if a unit is requested to start up or shut down it\nwill add it and all its dependencies to a temporary transaction. Then, it will verify if the\ntransaction is consistent (i.e. whether the ordering of all units is cycle-free). If it is\nnot, systemd will try to fix it up, and removes non-essential jobs from the transaction that\nmight remove the loop. Also, systemd tries to suppress non-essential jobs in the transaction\nthat would stop a running service. Finally it is checked whether the jobs of the transaction\ncontradict jobs that have already been queued, and optionally the transaction is aborted\nthen. If all worked out and the transaction is consistent and minimized in its impact it is\nmerged with all already outstanding jobs and added to the run queue. Effectively this means\nthat before executing a requested operation, systemd will verify that it makes sense, fixing\nit if possible, and only failing if it really cannot work.\n\nNote that transactions are generated independently of a unit's state at runtime, hence, for\nexample, if a start job is requested on an already started unit, it will still generate a\ntransaction and wake up any inactive dependencies (and cause propagation of other jobs as per\nthe defined relationships). This is because the enqueued job is at the time of execution\ncompared to the target unit's state and is marked successful and complete when both satisfy.\nHowever, this job also pulls in other dependencies due to the defined relationships and thus\nleads to, in our example, start jobs for any of those inactive units getting queued as well.\n\nsystemd contains native implementations of various tasks that need to be executed as part of\nthe boot process. For example, it sets the hostname or configures the loopback network\ndevice. It also sets up and mounts various API file systems, such as /sys/ or /proc/.\n\nFor more information about the concepts and ideas behind systemd, please refer to the\nOriginal Design Document[2].\n\nNote that some but not all interfaces provided by systemd are covered by the Interface\nPortability and Stability Promise[3].\n\nUnits may be generated dynamically at boot and system manager reload time, for example based\non other configuration files or parameters passed on the kernel command line. For details,\nsee systemd.generator(7).\n\nThe D-Bus API of systemd is described in org.freedesktop.systemd1(5) and\norg.freedesktop.LogControl1(5).\n\nSystems which invoke systemd in a container or initrd environment should implement the\nContainer Interface[4] or initrd Interface[5] specifications, respectively.\n\n### DIRECTORIES\n\nSystem unit directories\nThe systemd system manager reads unit configuration from various directories. Packages\nthat want to install unit files shall place them in the directory returned by pkg-config\nsystemd --variable=systemdsystemunitdir. Other directories checked are\n/usr/local/lib/systemd/system and /lib/systemd/system. User configuration always takes\nprecedence. pkg-config systemd --variable=systemdsystemconfdir returns the path of the\nsystem configuration directory. Packages should alter the content of these directories\nonly with the enable and disable commands of the systemctl(1) tool. Full list of\ndirectories is provided in systemd.unit(5).\n\nUser unit directories\nSimilar rules apply for the user unit directories. However, here the XDG Base Directory\nspecification[6] is followed to find units. Applications should place their unit files in\nthe directory returned by pkg-config systemd --variable=systemduserunitdir. Global\nconfiguration is done in the directory reported by pkg-config systemd\n--variable=systemduserconfdir. The enable and disable commands of the systemctl(1) tool\ncan handle both global (i.e. for all users) and private (for one user) enabling/disabling\nof units. Full list of directories is provided in systemd.unit(5).\n\nSysV init scripts directory\nThe location of the SysV init script directory varies between distributions. If systemd\ncannot find a native unit file for a requested service, it will look for a SysV init\nscript of the same name (with the .service suffix removed).\n\nSysV runlevel link farm directory\nThe location of the SysV runlevel link farm directory varies between distributions.\nsystemd will take the link farm into account when figuring out whether a service shall be\nenabled. Note that a service unit with a native unit configuration file cannot be started\nby activating it in the SysV runlevel link farm.\n\n### SIGNALS\n\nSIGTERM\nUpon receiving this signal the systemd system manager serializes its state, reexecutes\nitself and deserializes the saved state again. This is mostly equivalent to systemctl\ndaemon-reexec.\n\nsystemd user managers will start the exit.target unit when this signal is received. This\nis mostly equivalent to systemctl --user start exit.target\n--job-mode=replace-irreversibly.\n\nSIGINT\nUpon receiving this signal the systemd system manager will start the ctrl-alt-del.target\nunit. This is mostly equivalent to systemctl start ctrl-alt-del.target\n--job-mode=replace-irreversibly. If this signal is received more than 7 times per 2s, an\nimmediate reboot is triggered. Note that pressing Ctrl+Alt+Del on the console will\ntrigger this signal. Hence, if a reboot is hanging, pressing Ctrl+Alt+Del more than 7\ntimes in 2 seconds is a relatively safe way to trigger an immediate reboot.\n\nsystemd user managers treat this signal the same way as SIGTERM.\n\nSIGWINCH\nWhen this signal is received the systemd system manager will start the kbrequest.target\nunit. This is mostly equivalent to systemctl start kbrequest.target.\n\nThis signal is ignored by systemd user managers.\n\nSIGPWR\nWhen this signal is received the systemd manager will start the sigpwr.target unit. This\nis mostly equivalent to systemctl start sigpwr.target.\n\nSIGUSR1\nWhen this signal is received the systemd manager will try to reconnect to the D-Bus bus.\n\nSIGUSR2\nWhen this signal is received the systemd manager will log its complete state in\nhuman-readable form. The data logged is the same as printed by systemd-analyze dump.\n\nSIGHUP\nReloads the complete daemon configuration. This is mostly equivalent to systemctl\ndaemon-reload.\n\n#### SIGRTMIN+0\n\nEnters default mode, starts the default.target unit. This is mostly equivalent to\nsystemctl isolate default.target.\n\n#### SIGRTMIN+1\n\nEnters rescue mode, starts the rescue.target unit. This is mostly equivalent to systemctl\nisolate rescue.target.\n\n#### SIGRTMIN+2\n\nEnters emergency mode, starts the emergency.service unit. This is mostly equivalent to\nsystemctl isolate emergency.service.\n\n#### SIGRTMIN+3\n\nHalts the machine, starts the halt.target unit. This is mostly equivalent to systemctl\nstart halt.target --job-mode=replace-irreversibly.\n\n#### SIGRTMIN+4\n\nPowers off the machine, starts the poweroff.target unit. This is mostly equivalent to\nsystemctl start poweroff.target --job-mode=replace-irreversibly.\n\n#### SIGRTMIN+5\n\nReboots the machine, starts the reboot.target unit. This is mostly equivalent to\nsystemctl start reboot.target --job-mode=replace-irreversibly.\n\n#### SIGRTMIN+6\n\nReboots the machine via kexec, starts the kexec.target unit. This is mostly equivalent to\nsystemctl start kexec.target --job-mode=replace-irreversibly.\n\n#### SIGRTMIN+13\n\nImmediately halts the machine.\n\n#### SIGRTMIN+14\n\nImmediately powers off the machine.\n\n#### SIGRTMIN+15\n\nImmediately reboots the machine.\n\n#### SIGRTMIN+16\n\nImmediately reboots the machine with kexec.\n\n#### SIGRTMIN+20\n\nEnables display of status messages on the console, as controlled via\nsystemd.showstatus=1 on the kernel command line.\n\n#### SIGRTMIN+21\n\nDisables display of status messages on the console, as controlled via\nsystemd.showstatus=0 on the kernel command line.\n\n#### SIGRTMIN+22\n\nSets the service manager's log level to \"debug\", in a fashion equivalent to\nsystemd.loglevel=debug on the kernel command line.\n\n#### SIGRTMIN+23\n\nRestores the log level to its configured value. The configured value is derived from – in\norder of priority – the value specified with systemd.log-level= on the kernel command\nline, or the value specified with LogLevel= in the configuration file, or the built-in\ndefault of \"info\".\n\n#### SIGRTMIN+24\n\nImmediately exits the manager (only available for --user instances).\n\n#### SIGRTMIN+26\n\nRestores the log target to its configured value. The configured value is derived from –\nin order of priority – the value specified with systemd.log-target= on the kernel command\nline, or the value specified with LogTarget= in the configuration file, or the built-in\ndefault.\n\nSIGRTMIN+27, SIGRTMIN+28\nSets the log target to \"console\" on SIGRTMIN+27 (or \"kmsg\" on SIGRTMIN+28), in a fashion\nequivalent to systemd.logtarget=console (or systemd.logtarget=kmsg on SIGRTMIN+28) on\nthe kernel command line.\n\n### ENVIRONMENT\n\nThe environment block for the system manager is initially set by the kernel. (In particular,\n\"key=value\" assignments on the kernel command line are returned into environment variables\nfor PID 1). For the user manager, the system manager sets the environment as described in the\n\"Environment Variables in Spawned Processes\" section of systemd.exec(5). The\nDefaultEnvironment= setting in the system manager applies to all services including\nuser@.service. Additional entries may be configured (as for any other service) through the\nEnvironment= and EnvironmentFile= settings for user@.service (see systemd.exec(5)). Also,\nadditional environment variables may be set through the ManagerEnvironment= setting in\nsystemd-system.conf(5) and systemd-user.conf(5).\n\nSome of the variables understood by systemd:\n\n$SYSTEMDLOGLEVEL\nThe maximum log level of emitted messages (messages with a higher log level, i.e. less\nimportant ones, will be suppressed). Either one of (in order of decreasing importance)\nemerg, alert, crit, err, warning, notice, info, debug, or an integer in the range 0...7.\nSee syslog(3) for more information.\n\nThis can be overridden with --log-level=.\n\n$SYSTEMDLOGCOLOR\nA boolean. If true, messages written to the tty will be colored according to priority.\n\nThis can be overridden with --log-color=.\n\n$SYSTEMDLOGTIME\nA boolean. If true, console log messages will be prefixed with a timestamp.\n\nThis can be overridden with --log-time=.\n\n$SYSTEMDLOGLOCATION\nA boolean. If true, messages will be prefixed with a filename and line number in the\nsource code where the message originates.\n\nThis can be overridden with --log-location=.\n\n$SYSTEMDLOGTID\nA boolean. If true, messages will be prefixed with the current numerical thread ID (TID).\n\n$SYSTEMDLOGTARGET\nThe destination for log messages. One of console (log to the attached tty),\nconsole-prefixed (log to the attached tty but with prefixes encoding the log level and\n\"facility\", see syslog(3), kmsg (log to the kernel circular log buffer), journal (log to\nthe journal), journal-or-kmsg (log to the journal if available, and to kmsg otherwise),\nauto (determine the appropriate log target automatically, the default), null (disable log\noutput).\n\nThis can be overridden with --log-target=.\n\n$XDGCONFIGHOME, $XDGCONFIGDIRS, $XDGDATAHOME, $XDGDATADIRS\nThe systemd user manager uses these variables in accordance to the XDG Base Directory\nspecification[6] to find its configuration.\n\n$SYSTEMDUNITPATH, $SYSTEMDGENERATORPATH, $SYSTEMDENVIRONMENTGENERATORPATH\nControls where systemd looks for unit files and generators.\n\nThese variables may contain a list of paths, separated by colons (\":\"). When set, if the\nlist ends with an empty component (\"...:\"), this list is prepended to the usual set of\npaths. Otherwise, the specified list replaces the usual set of paths.\n\n$SYSTEMDPAGER\nPager to use when --no-pager is not given; overrides $PAGER. If neither $SYSTEMDPAGER\nnor $PAGER are set, a set of well-known pager implementations are tried in turn,\nincluding less(1) and more(1), until one is found. If no pager implementation is\ndiscovered no pager is invoked. Setting this environment variable to an empty string or\nthe value \"cat\" is equivalent to passing --no-pager.\n\n$SYSTEMDLESS\nOverride the options passed to less (by default \"FRSXMK\").\n\nUsers might want to change two options in particular:\n\nK\nThis option instructs the pager to exit immediately when Ctrl+C is pressed. To allow\nless to handle Ctrl+C itself to switch back to the pager command prompt, unset this\noption.\n\nIf the value of $SYSTEMDLESS does not include \"K\", and the pager that is invoked is\nless, Ctrl+C will be ignored by the executable, and needs to be handled by the pager.\n\nX\nThis option instructs the pager to not send termcap initialization and\ndeinitialization strings to the terminal. It is set by default to allow command\noutput to remain visible in the terminal even after the pager exits. Nevertheless,\nthis prevents some pager functionality from working, in particular paged output\ncannot be scrolled with the mouse.\n\nSee less(1) for more discussion.\n\n$SYSTEMDLESSCHARSET\nOverride the charset passed to less (by default \"utf-8\", if the invoking terminal is\ndetermined to be UTF-8 compatible).\n\n$SYSTEMDPAGERSECURE\nTakes a boolean argument. When true, the \"secure\" mode of the pager is enabled; if false,\ndisabled. If $SYSTEMDPAGERSECURE is not set at all, secure mode is enabled if the\neffective UID is not the same as the owner of the login session, see geteuid(2) and\nsdpidgetowneruid(3). In secure mode, LESSSECURE=1 will be set when invoking the\npager, and the pager shall disable commands that open or create new files or start new\nsubprocesses. When $SYSTEMDPAGERSECURE is not set at all, pagers which are not known to\nimplement secure mode will not be used. (Currently only less(1) implements secure mode.)\n\nNote: when commands are invoked with elevated privileges, for example under sudo(8) or\npkexec(1), care must be taken to ensure that unintended interactive features are not\nenabled. \"Secure\" mode for the pager may be enabled automatically as describe above.\nSetting SYSTEMDPAGERSECURE=0 or not removing it from the inherited environment allows\nthe user to invoke arbitrary commands. Note that if the $SYSTEMDPAGER or $PAGER\nvariables are to be honoured, $SYSTEMDPAGERSECURE must be set too. It might be\nreasonable to completely disable the pager using --no-pager instead.\n\n$SYSTEMDCOLORS\nTakes a boolean argument. When true, systemd and related utilities will use colors in\ntheir output, otherwise the output will be monochrome. Additionally, the variable can\ntake one of the following special values: \"16\", \"256\" to restrict the use of colors to\nthe base 16 or 256 ANSI colors, respectively. This can be specified to override the\nautomatic decision based on $TERM and what the console is connected to.\n\n$SYSTEMDURLIFY\nThe value must be a boolean. Controls whether clickable links should be generated in the\noutput for terminal emulators supporting this. This can be specified to override the\ndecision that systemd makes based on $TERM and other conditions.\n\n$LISTENPID, $LISTENFDS, $LISTENFDNAMES\nSet by systemd for supervised processes during socket-based activation. See\nsdlistenfds(3) for more information.\n\n$NOTIFYSOCKET\nSet by systemd for supervised processes for status and start-up completion notification.\nSee sdnotify(3) for more information.\n\nFor further environment variables understood by systemd and its various components, see Known\nEnvironment Variables[7].\n\n### KERNEL COMMAND LINE\n\nWhen run as the system instance systemd parses a number of options listed below. They can be\nspecified as kernel command line arguments[8], or through the \"SystemdOptions\" EFI variable\n(on EFI systems). The kernel command line has higher priority. Following variables are\nunderstood:\n\nsystemd.unit=, rd.systemd.unit=\nOverrides the unit to activate on boot. Defaults to default.target. This may be used to\ntemporarily boot into a different boot unit, for example rescue.target or\nemergency.service. See systemd.special(7) for details about these units. The option\nprefixed with \"rd.\" is honored only in the initial RAM disk (initrd), while the one that\nis not prefixed only in the main system.\n\nsystemd.dumpcore\nTakes a boolean argument or enables the option if specified without an argument. If\nenabled, the systemd manager (PID 1) dumps core when it crashes. Otherwise, no core dump\nis created. Defaults to enabled.\n\nsystemd.crashchvt\nTakes a positive integer, or a boolean argument. Can be also specified without an\nargument, with the same effect as a positive boolean. If a positive integer (in the range\n1–63) is specified, the system manager (PID 1) will activate the specified virtual\nterminal when it crashes. Defaults to disabled, meaning that no such switch is attempted.\nIf set to enabled, the virtual terminal the kernel messages are written to is used\ninstead.\n\nsystemd.crashshell\nTakes a boolean argument or enables the option if specified without an argument. If\nenabled, the system manager (PID 1) spawns a shell when it crashes, after a 10s delay.\nOtherwise, no shell is spawned. Defaults to disabled, for security reasons, as the shell\nis not protected by password authentication.\n\nsystemd.crashreboot\nTakes a boolean argument or enables the option if specified without an argument. If\nenabled, the system manager (PID 1) will reboot the machine automatically when it\ncrashes, after a 10s delay. Otherwise, the system will hang indefinitely. Defaults to\ndisabled, in order to avoid a reboot loop. If combined with systemd.crashshell, the\nsystem is rebooted after the shell exits.\n\nsystemd.confirmspawn\nTakes a boolean argument or a path to the virtual console where the confirmation messages\nshould be emitted. Can be also specified without an argument, with the same effect as a\npositive boolean. If enabled, the system manager (PID 1) asks for confirmation when\nspawning processes using /dev/console. If a path or a console name (such as \"ttyS0\") is\nprovided, the virtual console pointed to by this path or described by the give name will\nbe used instead. Defaults to disabled.\n\nsystemd.servicewatchdogs=\nTakes a boolean argument. If disabled, all service runtime watchdogs (WatchdogSec=) and\nemergency actions (e.g. OnFailure= or StartLimitAction=) are ignored by the system\nmanager (PID 1); see systemd.service(5). Defaults to enabled, i.e. watchdogs and failure\nactions are processed normally. The hardware watchdog is not affected by this option.\n\nsystemd.showstatus\nTakes a boolean argument or the constants error and auto. Can be also specified without\nan argument, with the same effect as a positive boolean. If enabled, the systemd manager\n(PID 1) shows terse service status updates on the console during bootup. With error, only\nmessages about failures are shown, but boot is otherwise quiet. auto behaves like false\nuntil there is a significant delay in boot. Defaults to enabled, unless quiet is passed\nas kernel command line option, in which case it defaults to error. If specified overrides\nthe system manager configuration file option ShowStatus=, see systemd-system.conf(5).\n\nsystemd.statusunitformat=\nTakes name, description or combined as the value. If name, the system manager will use\nunit names in status messages. If combined, the system manager will use unit names and\ndescription in status messages. When specified, overrides the system manager\nconfiguration file option StatusUnitFormat=, see systemd-system.conf(5).\n\nsystemd.logcolor, systemd.loglevel=, systemd.loglocation, systemd.logtarget=,\nsystemd.logtime, systemd.logtid\nControls log output, with the same effect as the $SYSTEMDLOGCOLOR, $SYSTEMDLOGLEVEL,\n$SYSTEMDLOGLOCATION, $SYSTEMDLOGTARGET, $SYSTEMDLOGTIME, and $SYSTEMDLOGTID\nenvironment variables described above. systemd.logcolor, systemd.loglocation,\nsystemd.logtime, and systemd.logtid= can be specified without an argument, with the\nsame effect as a positive boolean.\n\nsystemd.defaultstandardoutput=, systemd.defaultstandarderror=\nControls default standard output and error output for services and sockets. That is,\ncontrols the default for StandardOutput= and StandardError= (see systemd.exec(5) for\ndetails). Takes one of inherit, null, tty, journal, journal+console, kmsg, kmsg+console.\nIf the argument is omitted systemd.default-standard-output= defaults to journal and\nsystemd.default-standard-error= to inherit.\n\nsystemd.setenv=\nTakes a string argument in the form VARIABLE=VALUE. May be used to set default\nenvironment variables to add to forked child processes. May be used more than once to set\nmultiple variables.\n\nsystemd.machineid=\nTakes a 32 character hex value to be used for setting the machine-id. Intended mostly for\nnetwork booting where the same machine-id is desired for every boot.\n\nsystemd.unifiedcgrouphierarchy\nWhen specified without an argument or with a true argument, enables the usage of unified\ncgroup hierarchy[9] (a.k.a. cgroups-v2). When specified with a false argument, fall back\nto hybrid or full legacy cgroup hierarchy.\n\nIf this option is not specified, the default behaviour is determined during compilation\n(the -Ddefault-hierarchy= meson option). If the kernel does not support unified cgroup\nhierarchy, the legacy hierarchy will be used even if this option is specified.\n\nsystemd.legacysystemdcgroupcontroller\nTakes effect if the full unified cgroup hierarchy is not used (see previous option). When\nspecified without an argument or with a true argument, disables the use of \"hybrid\"\ncgroup hierarchy (i.e. a cgroups-v2 tree used for systemd, and legacy cgroup\nhierarchy[10], a.k.a. cgroups-v1, for other controllers), and forces a full \"legacy\"\nmode. When specified with a false argument, enables the use of \"hybrid\" hierarchy.\n\nIf this option is not specified, the default behaviour is determined during compilation\n(the -Ddefault-hierarchy= meson option). If the kernel does not support unified cgroup\nhierarchy, the legacy hierarchy will be used even if this option is specified.\n\nquiet\nTurn off status output at boot, much like systemd.showstatus=no would. Note that this\noption is also read by the kernel itself and disables kernel log output. Passing this\noption hence turns off the usual output from both the system manager and the kernel.\n\ndebug\nTurn on debugging output. This is equivalent to systemd.loglevel=debug. Note that this\noption is also read by the kernel itself and enables kernel debug output. Passing this\noption hence turns on the debug output from both the system manager and the kernel.\n\nemergency, rd.emergency, -b\nBoot into emergency mode. This is equivalent to systemd.unit=emergency.target or\nrd.systemd.unit=emergency.target, respectively, and provided for compatibility reasons\nand to be easier to type.\n\nrescue, rd.rescue, single, s, S, 1\nBoot into rescue mode. This is equivalent to systemd.unit=rescue.target or\nrd.systemd.unit=rescue.target, respectively, and provided for compatibility reasons and\nto be easier to type.\n\n2, 3, 4, 5\nBoot into the specified legacy SysV runlevel. These are equivalent to\nsystemd.unit=runlevel2.target, systemd.unit=runlevel3.target,\nsystemd.unit=runlevel4.target, and systemd.unit=runlevel5.target, respectively, and\nprovided for compatibility reasons and to be easier to type.\n\nlocale.LANG=, locale.LANGUAGE=, locale.LCCTYPE=, locale.LCNUMERIC=, locale.LCTIME=,\nlocale.LCCOLLATE=, locale.LCMONETARY=, locale.LCMESSAGES=, locale.LCPAPER=,\nlocale.LCNAME=, locale.LCADDRESS=, locale.LCTELEPHONE=, locale.LCMEASUREMENT=,\nlocale.LCIDENTIFICATION=\nSet the system locale to use. This overrides the settings in /etc/locale.conf. For more\ninformation, see locale.conf(5) and locale(7).\n\nFor other kernel command line parameters understood by components of the core OS, please\nrefer to kernel-command-line(7).\n\n### OPTIONS\n\nsystemd is only very rarely invoked directly, since it is started early and is already\nrunning by the time users may interact with it. Normally, tools like systemctl(1) are used to\ngive commands to the manager. Since systemd is usually not invoked directly, the options\nlisted below are mostly useful for debugging and special purposes.\n\n#### Introspection and debugging options\n\nThose options are used for testing and introspection, and systemd may be invoked with them at\nany time:\n\n#### --dump-configuration-items\n\nDump understood unit configuration items. This outputs a terse but complete list of\nconfiguration items understood in unit definition files.\n\n#### --dump-bus-properties\n\nDump exposed bus properties. This outputs a terse but complete list of properties exposed\non D-Bus.\n\n#### --test\n\nDetermine the initial start-up transaction (i.e. the list of jobs enqueued at start-up),\ndump it and exit — without actually executing any of the determined jobs. This option is\nuseful for debugging only. Note that during regular service manager start-up additional\nunits not shown by this operation may be started, because hardware, socket, bus or other\nkinds of activation might add additional jobs as the transaction is executed. Use\n--system to request the initial transaction of the system service manager (this is also\nthe implied default), combine with --user to request the initial transaction of the\nper-user service manager instead.\n\n--system, --user\nWhen used in conjunction with --test, selects whether to calculate the initial\ntransaction for the system instance or for a per-user instance. These options have no\neffect when invoked without --test, as during regular (i.e. non---test) invocations the\nservice manager will automatically detect whether it shall operate in system or per-user\nmode, by checking whether the PID it is run as is 1 or not. Note that it is not supported\nbooting and maintaining a system with the service manager running in --system mode but\nwith a PID other than 1.\n\n#### -h --help\n\nPrint a short help text and exit.\n\n#### --version\n\nPrint a short version string and exit.\n\n#### Options that duplicate kernel command line settings\n\nThose options correspond directly to options listed above in \"Kernel Command Line\". Both\nforms may be used equivalently for the system manager, but it is recommended to use the forms\nlisted above in this context, because they are properly namespaced. When an option is\nspecified both on the kernel command line and as a normal command line argument, the latter\nhas higher precedence.\n\nWhen systemd is used as a user manager, the kernel command line is ignored and only the\noptions described below are understood. Nevertheless, systemd is usually started in this mode\nthrough the user@.service(5) service, which is shared between all users. It may be more\nconvenient to use configuration files to modify settings (see systemd-user.conf(5)), or\nenvironment variables. See the \"Environment\" section above for a discussion of how the\nenvironment block is set.\n\n#### --unit=\n\nSet default unit to activate on startup. If not specified, defaults to default.target.\nSee systemd.unit= above.\n\n#### --dump-core\n\nEnable core dumping on crash. This switch has no effect when running as user instance.\nSame as systemd.dumpcore= above.\n\n--crash-vt=VT\nSwitch to a specific virtual console (VT) on crash. This switch has no effect when\nrunning as user instance. Same as systemd.crashchvt= above (but not the different\nspelling!).\n\n#### --crash-shell\n\nRun a shell on crash. This switch has no effect when running as user instance. See\nsystemd.crashshell= above.\n\n#### --crash-reboot\n\nAutomatically reboot the system on crash. This switch has no effect when running as user\ninstance. See systemd.crashreboot above.\n\n#### --confirm-spawn\n\nAsk for confirmation when spawning processes. This switch has no effect when run as user\ninstance. See systemd.confirmspawn above.\n\n#### --show-status\n\nShow terse unit status information on the console during boot-up and shutdown. See\nsystemd.showstatus above.\n\n#### --log-color\n\nHighlight important log messages. See systemd.logcolor above.\n\n#### --log-level=\n\nSet log level. See systemd.loglevel above.\n\n#### --log-location\n\nInclude code location in log messages. See systemd.loglocation above.\n\n#### --log-target=\n\nSet log target. See systemd.logtarget above.\n\n#### --log-time=\n\nPrefix console messages with timestamp. See systemd.logtime above.\n\n#### --machine-id=\n\nOverride the machine-id set on the hard drive. See systemd.machineid= above.\n\n#### --service-watchdogs\n\nGlobally enable/disable all service watchdog timeouts and emergency actions. See\nsystemd.servicewatchdogs above.\n\n--default-standard-output=, --default-standard-error=\nSets the default output or error output for all services and sockets, respectively. See\nsystemd.defaultstandardoutput= and systemd.defaultstandarderror= above.\n\n### SOCKETS AND FIFOS\n\n/run/systemd/notify\nDaemon status notification socket. This is an AFUNIX datagram socket and is used to\nimplement the daemon notification logic as implemented by sdnotify(3).\n\n/run/systemd/private\nUsed internally as communication channel between systemctl(1) and the systemd process.\nThis is an AFUNIX stream socket. This interface is private to systemd and should not be\nused in external projects.\n\n/dev/initctl\nLimited compatibility support for the SysV client interface, as implemented by the\nsystemd-initctl.service unit. This is a named pipe in the file system. This interface is\nobsolete and should not be used in new applications.\n\n### SEE ALSO\n\nThe systemd Homepage[11], systemd-system.conf(5), locale.conf(5), systemctl(1),\njournalctl(1), systemd-notify(1), daemon(7), sd-daemon(3), org.freedesktop.systemd1(5),\nsystemd.unit(5), systemd.special(7), pkg-config(1), kernel-command-line(7), bootup(7),\nsystemd.directives(7)\n\n### NOTES\n\n1. cgroups.txt\nhttps://www.kernel.org/doc/Documentation/cgroup-v1/cgroups.txt\n\n2. Original Design Document\nhttp://0pointer.de/blog/projects/systemd.html\n\n3. Interface Portability and Stability Promise\nhttps://systemd.io/PORTABILITYANDSTABILITY/\n\n4. Container Interface\nhttps://systemd.io/CONTAINERINTERFACE\n\n5. initrd Interface\nhttps://systemd.io/INITRDINTERFACE/\n\n6. XDG Base Directory specification\nhttp://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html\n\n7. Known Environment Variables\nhttps://systemd.io/ENVIRONMENT\n\n8. If run inside a Linux container these arguments may be passed as command line arguments\nto systemd itself, next to any of the command line options listed in the Options section\nabove. If run outside of Linux containers, these arguments are parsed from /proc/cmdline\ninstead.\n\n9. unified cgroup hierarchy\nhttps://www.kernel.org/doc/html/latest/admin-guide/cgroup-v2.html\n\n10. legacy cgroup hierarchy\nhttps://www.kernel.org/doc/Documentation/cgroup-v1/\n\n11. systemd Homepage\nhttps://www.freedesktop.org/wiki/Software/systemd/\n\n\n\nsystemd 249 SYSTEMD(1)\n\n" } ], "structuredContent": { "command": "systemd", "section": "1", "mode": "man", "summary": "systemd, init - systemd system and service manager", "synopsis": "/lib/systemd/systemd [OPTIONS...]\ninit [OPTIONS...] {COMMAND}", "tldr_summary": "", "tldr_examples": [ { "description": "To display process startup time:", "command": "systemd-analyze" }, { "description": "To display process startup time at service level:", "command": "systemd-analyze blame" }, { "description": "To list running units:", "command": "systemctl list-units" }, { "description": "To load a unit at startup:", "command": "systemctl enable foo.service" }, { "description": "To start or Stop a unit:", "command": "systemctl <start | stop> foo.service" }, { "description": "To unit file locations:", "command": "/etc/systemd/system" } ], "tldr_source": "cheatsh", "flags": [ { "flag": "", "long": "--dump-configuration-items", "arg": null, "description": "Dump understood unit configuration items. This outputs a terse but complete list of configuration items understood in unit definition files." }, { "flag": "", "long": "--dump-bus-properties", "arg": null, "description": "Dump exposed bus properties. This outputs a terse but complete list of properties exposed on D-Bus." }, { "flag": "", "long": "--test", "arg": null, "description": "Determine the initial start-up transaction (i.e. the list of jobs enqueued at start-up), dump it and exit — without actually executing any of the determined jobs. This option is useful for debugging only. Note that during regular service manager start-up additional units not shown by this operation may be started, because hardware, socket, bus or other kinds of activation might add additional jobs as the transaction is executed. Use --system to request the initial transaction of the system service manager (this is also the implied default), combine with --user to request the initial transaction of the per-user service manager instead. --system, --user When used in conjunction with --test, selects whether to calculate the initial transaction for the system instance or for a per-user instance. These options have no effect when invoked without --test, as during regular (i.e. non---test) invocations the service manager will automatically detect whether it shall operate in system or per-user mode, by checking whether the PID it is run as is 1 or not. Note that it is not supported booting and maintaining a system with the service manager running in --system mode but with a PID other than 1." }, { "flag": "-h", "long": "--help", "arg": null, "description": "Print a short help text and exit." }, { "flag": "", "long": "--version", "arg": null, "description": "Print a short version string and exit." }, { "flag": "", "long": null, "arg": null, "description": "Set default unit to activate on startup. If not specified, defaults to default.target. See systemd.unit= above." }, { "flag": "", "long": "--dump-core", "arg": null, "description": "Enable core dumping on crash. This switch has no effect when running as user instance. Same as systemd.dumpcore= above. --crash-vt=VT Switch to a specific virtual console (VT) on crash. This switch has no effect when running as user instance. Same as systemd.crashchvt= above (but not the different spelling!)." }, { "flag": "", "long": "--crash-shell", "arg": null, "description": "Run a shell on crash. This switch has no effect when running as user instance. See systemd.crashshell= above." }, { "flag": "", "long": "--crash-reboot", "arg": null, "description": "Automatically reboot the system on crash. This switch has no effect when running as user instance. See systemd.crashreboot above." }, { "flag": "", "long": "--confirm-spawn", "arg": null, "description": "Ask for confirmation when spawning processes. This switch has no effect when run as user instance. See systemd.confirmspawn above." }, { "flag": "", "long": "--show-status", "arg": null, "description": "Show terse unit status information on the console during boot-up and shutdown. See systemd.showstatus above." }, { "flag": "", "long": "--log-color", "arg": null, "description": "Highlight important log messages. See systemd.logcolor above." }, { "flag": "", "long": null, "arg": null, "description": "Set log level. See systemd.loglevel above." }, { "flag": "", "long": "--log-location", "arg": null, "description": "Include code location in log messages. See systemd.loglocation above." }, { "flag": "", "long": null, "arg": null, "description": "Set log target. See systemd.logtarget above." }, { "flag": "", "long": null, "arg": null, "description": "Prefix console messages with timestamp. See systemd.logtime above." }, { "flag": "", "long": null, "arg": null, "description": "Override the machine-id set on the hard drive. See systemd.machineid= above." }, { "flag": "", "long": "--service-watchdogs", "arg": null, "description": "Globally enable/disable all service watchdog timeouts and emergency actions. See systemd.servicewatchdogs above. --default-standard-output=, --default-standard-error= Sets the default output or error output for all services and sockets, respectively. See systemd.defaultstandardoutput= and systemd.defaultstandarderror= above." } ], "examples": [], "see_also": [ { "name": "systemd-system.conf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/systemd-system.conf/5/json" }, { "name": "locale.conf", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/locale.conf/5/json" }, { "name": "systemctl", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/systemctl/1/json" }, { "name": "journalctl", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/journalctl/1/json" }, { "name": "systemd-notify", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/systemd-notify/1/json" }, { "name": "daemon", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/daemon/7/json" }, { "name": "sd-daemon", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/sd-daemon/3/json" }, { "name": "org.freedesktop.systemd1", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/org.freedesktop.systemd1/5/json" }, { "name": "systemd.unit", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/systemd.unit/5/json" }, { "name": "systemd.special", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/systemd.special/7/json" }, { "name": "pkg-config", "section": "1", "url": "https://www.chedong.com/phpMan.php/man/pkg-config/1/json" }, { "name": "kernel-command-line", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/kernel-command-line/7/json" }, { "name": "bootup", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/bootup/7/json" }, { "name": "systemd.directives", "section": "7", "url": "https://www.chedong.com/phpMan.php/man/systemd.directives/7/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 4, "subsections": [] }, { "name": "DESCRIPTION", "lines": 18, "subsections": [] }, { "name": "CONCEPTS", "lines": 155, "subsections": [] }, { "name": "DIRECTORIES", "lines": 30, "subsections": [] }, { "name": "SIGNALS", "lines": 40, "subsections": [ { "name": "SIGRTMIN+0", "lines": 3 }, { "name": "SIGRTMIN+1", "lines": 3 }, { "name": "SIGRTMIN+2", "lines": 3 }, { "name": "SIGRTMIN+3", "lines": 3 }, { "name": "SIGRTMIN+4", "lines": 3 }, { "name": "SIGRTMIN+5", "lines": 3 }, { "name": "SIGRTMIN+6", "lines": 3 }, { "name": "SIGRTMIN+13", "lines": 2 }, { "name": "SIGRTMIN+14", "lines": 2 }, { "name": "SIGRTMIN+15", "lines": 2 }, { "name": "SIGRTMIN+16", "lines": 2 }, { "name": "SIGRTMIN+20", "lines": 3 }, { "name": "SIGRTMIN+21", "lines": 3 }, { "name": "SIGRTMIN+22", "lines": 3 }, { "name": "SIGRTMIN+23", "lines": 5 }, { "name": "SIGRTMIN+24", "lines": 2 }, { "name": "SIGRTMIN+26", "lines": 10 } ] }, { "name": "ENVIRONMENT", "lines": 133, "subsections": [] }, { "name": "KERNEL COMMAND LINE", "lines": 147, "subsections": [] }, { "name": "OPTIONS", "lines": 5, "subsections": [ { "name": "Introspection and debugging options", "lines": 3 }, { "name": "--dump-configuration-items", "lines": 3, "long": "--dump-configuration-items" }, { "name": "--dump-bus-properties", "lines": 3, "long": "--dump-bus-properties" }, { "name": "--test", "lines": 18, "long": "--test" }, { "name": "-h --help", "lines": 2, "flag": "-h", "long": "--help" }, { "name": "--version", "lines": 2, "long": "--version" }, { "name": "Options that duplicate kernel command line settings", "lines": 13 }, { "name": "--unit=", "lines": 3 }, { "name": "--dump-core", "lines": 8, "long": "--dump-core" }, { "name": "--crash-shell", "lines": 3, "long": "--crash-shell" }, { "name": "--crash-reboot", "lines": 3, "long": "--crash-reboot" }, { "name": "--confirm-spawn", "lines": 3, "long": "--confirm-spawn" }, { "name": "--show-status", "lines": 3, "long": "--show-status" }, { "name": "--log-color", "lines": 2, "long": "--log-color" }, { "name": "--log-level=", "lines": 2 }, { "name": "--log-location", "lines": 2, "long": "--log-location" }, { "name": "--log-target=", "lines": 2 }, { "name": "--log-time=", "lines": 2 }, { "name": "--machine-id=", "lines": 2 }, { "name": "--service-watchdogs", "lines": 7, "long": "--service-watchdogs" } ] }, { "name": "SOCKETS AND FIFOS", "lines": 14, "subsections": [] }, { "name": "SEE ALSO", "lines": 5, "subsections": [] }, { "name": "NOTES", "lines": 38, "subsections": [] } ] } }