{ "mode": "info", "parameter": "init", "section": "", "url": "https://www.chedong.com/phpMan.php/info/init/json", "generated": "2026-08-01T21:01:45Z", "synopsis": "/lib/systemd/systemd [OPTIONS...]\ninit [OPTIONS...] {COMMAND}", "sections": { "NAME": { "content": "init - a UNIX process no 1\n", "subsections": [] }, "SYNOPSIS": { "content": "init [ 0 | 6 ]\n", "subsections": [] }, "DESCRIPTION": { "content": "runit-init is the first process the kernel starts. If runit-init is\nstarted as process no 1, it runs and replaces itself with runit(8).\n\nIf runit-init is started while the system is up, it must be either\ncalled as init 0 or init 6:\n\ninit 0 tells the Unix process no 1 to shutdown and halt the system. To\nsignal runit(8) the system halt request, runit-init removes all\npermissions of the file /run/runit.reboot (chmod 0), and sets\nthe execute by owner permission of the file /run/runit.stopit\n(chmod 100). Then a CONT signal is sent to runit(8).\n\ninit 6 tells the Unix process no 1 to shutdown and reboot the system.\nTo signal runit(8) the system reboot request, runit-init sets\nthe execute by owner permission of the files /run/runit.reboot\nand /run/runit.stopit (chmod 100). Then a CONT signal is sent to\nrunit(8).\n", "subsections": [] }, "CONCEPTS": { "content": "systemd provides a dependency system between various entities called\n\"units\" of 11 different types. Units encapsulate various objects that\nare relevant for system boot-up and maintenance. The majority of units\nare configured in unit configuration files, whose syntax and basic set\nof options is described in systemd.unit(5), however some are created\nautomatically from other configuration files, dynamically from system\nstate or programmatically at runtime. Units may be \"active\" (meaning\nstarted, bound, plugged in, ..., depending on the unit type, see\nbelow), or \"inactive\" (meaning stopped, unbound, unplugged, ...), as\nwell as in the process of being activated or deactivated, i.e. between\nthe two states (these states are called \"activating\", \"deactivating\").\nA special \"failed\" state is available as well, which is very similar to\n\"inactive\" and is entered when the service failed in some way (process\nreturned error code on exit, or crashed, an operation timed out, or\nafter too many restarts). If this state is entered, the cause will be\nlogged, for later reference. Note that the various unit types may have\na number of additional substates, which are mapped to the five\ngeneralized unit states described here.\n\nThe following unit types are available:\n\n1. Service units, which start and control daemons and the processes\nthey consist of. For details, see systemd.service(5).\n\n2. Socket units, which encapsulate local IPC or network sockets in the\nsystem, useful for socket-based activation. For details about\nsocket units, see systemd.socket(5), for details on socket-based\nactivation and other forms of activation, see daemon(7).\n\n3. Target units are useful to group units, or provide well-known\nsynchronization points during boot-up, see systemd.target(5).\n\n4. Device units expose kernel devices in systemd and may be used to\nimplement device-based activation. For details, see\nsystemd.device(5).\n\n5. Mount units control mount points in the file system, for details\nsee systemd.mount(5).\n\n6. Automount units provide automount capabilities, for on-demand\nmounting of file systems as well as parallelized boot-up. See\nsystemd.automount(5).\n\n7. Timer units are useful for triggering activation of other units\nbased on timers. You may find details in systemd.timer(5).\n\n8. Swap units are very similar to mount units and encapsulate memory\nswap partitions or files of the operating system. They are\ndescribed in systemd.swap(5).\n\n9. Path units may be used to activate other services when file system\nobjects change or are modified. See systemd.path(5).\n\n10. Slice units may be used to group units which manage system\nprocesses (such as service and scope units) in a hierarchical tree\nfor resource management purposes. See systemd.slice(5).\n\n11. Scope units are similar to service units, but manage foreign\nprocesses instead of starting them as well. See systemd.scope(5).\n\nUnits are named as their configuration files. Some units have special\nsemantics. A detailed list is available in systemd.special(7).\n\nsystemd knows various kinds of dependencies, including positive and\nnegative requirement dependencies (i.e. Requires= and Conflicts=) as\nwell as ordering dependencies (After= and Before=). NB: ordering and\nrequirement dependencies are orthogonal. If only a requirement\ndependency exists between two units (e.g. foo.service requires\nbar.service), but no ordering dependency (e.g. foo.service after\nbar.service) and both are requested to start, they will be started in\nparallel. It is a common pattern that both requirement and ordering\ndependencies are placed between two units. Also note that the majority\nof dependencies are implicitly created and maintained by systemd. In\nmost cases, it should be unnecessary to declare additional dependencies\nmanually, however it is possible to do this.\n\nApplication programs and units (via dependencies) may request state\nchanges of units. In systemd, these requests are encapsulated as 'jobs'\nand maintained in a job queue. Jobs may succeed or can fail, their\nexecution is ordered based on the ordering dependencies of the units\nthey have been scheduled for.\n\nOn boot systemd activates the target unit default.target whose job is\nto activate on-boot services and other on-boot units by pulling them in\nvia dependencies. Usually, the unit name is just an alias (symlink) for\neither graphical.target (for fully-featured boots into the UI) or\nmulti-user.target (for limited console-only boots for use in embedded\nor server environments, or similar; a subset of graphical.target).\nHowever, it is at the discretion of the administrator to configure it\nas an alias to any other target unit. See systemd.special(7) for\ndetails about these target units.\n\nsystemd only keeps a minimal set of units loaded into memory.\nSpecifically, the only units that are kept loaded into memory are those\nfor which at least one of the following conditions is true:\n\n1. It is in an active, activating, deactivating or failed state (i.e.\nin any unit state except 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\nmemory\n\n4. It has some form of resource still allocated (e.g. a service unit\nthat is inactive but for which a process is still lingering that\nignored 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\nthey are not loaded yet -- as soon as operations are requested for\nthem. Thus, in many respects, the fact whether a unit is loaded or not\nis invisible to clients. Use systemctl list-units --all to\ncomprehensively list all units currently loaded. Any unit for which\nnone of the conditions above applies is promptly unloaded. Note that\nwhen a unit is unloaded from memory its accounting data is flushed out\ntoo. However, this data is generally not lost, as a journal log record\nis generated declaring the consumed resources whenever a unit shuts\ndown.\n\nProcesses systemd spawns are placed in individual Linux control groups\nnamed after the unit which they belong to in the private systemd\nhierarchy. (see cgroups.txt[1] for more information about control\ngroups, or short \"cgroups\"). systemd uses this to effectively keep\ntrack of processes. Control group information is maintained in the\nkernel, and is accessible via the file system hierarchy (beneath\n/sys/fs/cgroup/systemd/), or in tools such as systemd-cgls(1) or ps(1)\n(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\ninit scripts are supported and simply read as an alternative (though\nlimited) configuration file format. The SysV /dev/initctl interface is\nprovided, and compatibility implementations of the various SysV client\ntools are available. In addition to that, various established Unix\nfunctionality such as /etc/fstab or the utmp database are supported.\n\nsystemd has a minimal transaction system: if a unit is requested to\nstart up or shut down it will add it and all its dependencies to a\ntemporary transaction. Then, it will verify if the transaction is\nconsistent (i.e. whether the ordering of all units is cycle-free). If\nit is not, systemd will try to fix it up, and removes non-essential\njobs from the transaction that might remove the loop. Also, systemd\ntries to suppress non-essential jobs in the transaction that would stop\na running service. Finally it is checked whether the jobs of the\ntransaction contradict jobs that have already been queued, and\noptionally the transaction is aborted then. If all worked out and the\ntransaction is consistent and minimized in its impact it is merged with\nall already outstanding jobs and added to the run queue. Effectively\nthis means that before executing a requested operation, systemd will\nverify that it makes sense, fixing it if possible, and only failing if\nit really cannot work.\n\nNote that transactions are generated independently of a unit's state at\nruntime, hence, for example, if a start job is requested on an already\nstarted unit, it will still generate a transaction and wake up any\ninactive dependencies (and cause propagation of other jobs as per the\ndefined relationships). This is because the enqueued job is at the time\nof execution compared to the target unit's state and is marked\nsuccessful and complete when both satisfy. However, this job also pulls\nin other dependencies due to the defined relationships and thus leads\nto, in our example, start jobs for any of those inactive units getting\nqueued as well.\n\nsystemd contains native implementations of various tasks that need to\nbe executed as part of the boot process. For example, it sets the\nhostname or configures the loopback network device. It also sets up and\nmounts various API file systems, such as /sys/ or /proc/.\n\nFor more information about the concepts and ideas behind systemd,\nplease refer to the Original Design Document[2].\n\nNote that some but not all interfaces provided by systemd are covered\nby the Interface Portability and Stability Promise[3].\n\nUnits may be generated dynamically at boot and system manager reload\ntime, for example based on other configuration files or parameters\npassed on the kernel command line. For details, see\nsystemd.generator(7).\n\nThe D-Bus API of systemd is described in org.freedesktop.systemd1(5)\nand org.freedesktop.LogControl1(5).\n\nSystems which invoke systemd in a container or initrd environment\nshould implement the Container Interface[4] or initrd Interface[5]\nspecifications, respectively.\n", "subsections": [] }, "DIRECTORIES": { "content": "System unit directories\nThe systemd system manager reads unit configuration from various\ndirectories. Packages that want to install unit files shall place\nthem in the directory returned by pkg-config systemd\n--variable=systemdsystemunitdir. Other directories checked are\n/usr/local/lib/systemd/system and /lib/systemd/system. User\nconfiguration always takes precedence. pkg-config systemd\n--variable=systemdsystemconfdir returns the path of the system\nconfiguration directory. Packages should alter the content of these\ndirectories only with the enable and disable commands of the\nsystemctl(1) tool. Full list of directories is provided in\nsystemd.unit(5).\n\nUser unit directories\nSimilar rules apply for the user unit directories. However, here\nthe XDG Base Directory specification[6] is followed to find units.\nApplications should place their unit files in the directory\nreturned by pkg-config systemd --variable=systemduserunitdir.\nGlobal configuration is done in the directory reported by\npkg-config systemd --variable=systemduserconfdir. The enable and\ndisable commands of the systemctl(1) tool can handle both global\n(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\ndistributions. If systemd cannot find a native unit file for a\nrequested service, it will look for a SysV init script of the same\nname (with the .service suffix removed).\n\nSysV runlevel link farm directory\nThe location of the SysV runlevel link farm directory varies\nbetween distributions. systemd will take the link farm into account\nwhen figuring out whether a service shall be enabled. Note that a\nservice unit with a native unit configuration file cannot be\nstarted by activating it in the SysV runlevel link farm.\n", "subsections": [] }, "SIGNALS": { "content": "SIGTERM\nUpon receiving this signal the systemd system manager serializes\nits state, reexecutes itself and deserializes the saved state\nagain. This is mostly equivalent to systemctl daemon-reexec.\n\nsystemd user managers will start the exit.target unit when this\nsignal is received. This is mostly equivalent to systemctl --user\nstart exit.target --job-mode=replace-irreversibly.\n\nSIGINT\nUpon receiving this signal the systemd system manager will start\nthe ctrl-alt-del.target unit. This is mostly equivalent to\nsystemctl start ctrl-alt-del.target\n--job-mode=replace-irreversibly. If this signal is received more\nthan 7 times per 2s, an immediate reboot is triggered. Note that\npressing Ctrl+Alt+Del on the console will trigger this signal.\nHence, 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\nreboot.\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\nthe kbrequest.target unit. This is mostly equivalent to systemctl\nstart kbrequest.target.\n\nThis signal is ignored by systemd user managers.\n\nSIGPWR\nWhen this signal is received the systemd manager will start the\nsigpwr.target unit. This is mostly equivalent to systemctl start\nsigpwr.target.\n\nSIGUSR1\nWhen this signal is received the systemd manager will try to\nreconnect to the D-Bus bus.\n\nSIGUSR2\nWhen this signal is received the systemd manager will log its\ncomplete state in human-readable form. The data logged is the same\nas printed by systemd-analyze dump.\n\nSIGHUP\nReloads the complete daemon configuration. This is mostly\nequivalent to systemctl daemon-reload.\n\nSIGRTMIN+0\nEnters default mode, starts the default.target unit. This is mostly\nequivalent to systemctl isolate default.target.\n\nSIGRTMIN+1\nEnters rescue mode, starts the rescue.target unit. This is mostly\nequivalent to systemctl isolate rescue.target.\n\nSIGRTMIN+2\nEnters emergency mode, starts the emergency.service unit. This is\nmostly equivalent to systemctl isolate emergency.service.\n\nSIGRTMIN+3\nHalts the machine, starts the halt.target unit. This is mostly\nequivalent to systemctl start halt.target\n--job-mode=replace-irreversibly.\n\nSIGRTMIN+4\nPowers off the machine, starts the poweroff.target unit. This is\nmostly equivalent to systemctl start poweroff.target\n--job-mode=replace-irreversibly.\n\nSIGRTMIN+5\nReboots the machine, starts the reboot.target unit. This is mostly\nequivalent to systemctl start reboot.target\n--job-mode=replace-irreversibly.\n\nSIGRTMIN+6\nReboots the machine via kexec, starts the kexec.target unit. This\nis mostly equivalent to systemctl start kexec.target\n--job-mode=replace-irreversibly.\n\nSIGRTMIN+13\nImmediately halts the machine.\n\nSIGRTMIN+14\nImmediately powers off the machine.\n\nSIGRTMIN+15\nImmediately reboots the machine.\n\nSIGRTMIN+16\nImmediately reboots the machine with kexec.\n\nSIGRTMIN+20\nEnables display of status messages on the console, as controlled\nvia systemd.showstatus=1 on the kernel command line.\n\nSIGRTMIN+21\nDisables display of status messages on the console, as controlled\nvia systemd.showstatus=0 on the kernel command line.\n\nSIGRTMIN+22\nSets the service manager's log level to \"debug\", in a fashion\nequivalent to systemd.loglevel=debug on the kernel command line.\n\nSIGRTMIN+23\nRestores the log level to its configured value. The configured\nvalue is derived from - in order of priority - the value specified\nwith systemd.log-level= on the kernel command line, or the value\nspecified with LogLevel= in the configuration file, or the built-in\ndefault of \"info\".\n\nSIGRTMIN+24\nImmediately exits the manager (only available for --user\ninstances).\n\nSIGRTMIN+26\nRestores the log target to its configured value. The configured\nvalue is derived from - in order of priority - the value specified\nwith systemd.log-target= on the kernel command line, or the value\nspecified with LogTarget= in the configuration file, or the\nbuilt-in default.\n\nSIGRTMIN+27, SIGRTMIN+28\nSets the log target to \"console\" on SIGRTMIN+27 (or \"kmsg\" on\nSIGRTMIN+28), in a fashion equivalent to systemd.logtarget=console\n(or systemd.logtarget=kmsg on SIGRTMIN+28) on the kernel command\nline.\n", "subsections": [] }, "ENVIRONMENT": { "content": "The environment block for the system manager is initially set by the\nkernel. (In particular, \"key=value\" assignments on the kernel command\nline are returned into environment variables for PID 1). For the user\nmanager, the system manager sets the environment as described in the\n\"Environment Variables in Spawned Processes\" section of\nsystemd.exec(5). The DefaultEnvironment= setting in the system manager\napplies to all services including user@.service. Additional entries may\nbe configured (as for any other service) through the Environment= and\nEnvironmentFile= settings for user@.service (see systemd.exec(5)).\nAlso, additional environment variables may be set through the\nManagerEnvironment= setting in systemd-system.conf(5) and systemd-\nuser.conf(5).\n\nSome of the variables understood by systemd:\n\n$SYSTEMDLOGLEVEL\nThe maximum log level of emitted messages (messages with a higher\nlog level, i.e. less important ones, will be suppressed). Either\none of (in order of decreasing importance) emerg, alert, crit, err,\nwarning, notice, info, debug, or an integer in the range 0...7. See\nsyslog(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\naccording 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\ntimestamp.\n\nThis can be overridden with --log-time=.\n\n$SYSTEMDLOGLOCATION\nA boolean. If true, messages will be prefixed with a filename and\nline number in the source 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\nnumerical thread ID (TID).\n\n$SYSTEMDLOGTARGET\nThe destination for log messages. One of console (log to the\nattached tty), console-prefixed (log to the attached tty but with\nprefixes encoding the log level and \"facility\", see syslog(3), kmsg\n(log to the kernel circular log buffer), journal (log to the\njournal), journal-or-kmsg (log to the journal if available, and to\nkmsg otherwise), auto (determine the appropriate log target\nautomatically, the default), null (disable log output).\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\nXDG Base Directory specification[6] to find its configuration.\n\n$SYSTEMDUNITPATH, $SYSTEMDGENERATORPATH,\n$SYSTEMDENVIRONMENTGENERATORPATH\nControls where systemd looks for unit files and generators.\n\nThese variables may contain a list of paths, separated by colons\n(\":\"). When set, if the list ends with an empty component (\"...:\"),\nthis list is prepended to the usual set of paths. Otherwise, the\nspecified list replaces the usual set of paths.\n\n$SYSTEMDPAGER\nPager to use when --no-pager is not given; overrides $PAGER. If\nneither $SYSTEMDPAGER nor $PAGER are set, a set of well-known\npager implementations are tried in turn, including less(1) and\nmore(1), until one is found. If no pager implementation is\ndiscovered no pager is invoked. Setting this environment variable\nto an empty string or the value \"cat\" is equivalent to passing\n--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\nis pressed. To allow less to handle Ctrl+C itself to switch\nback to the pager command prompt, unset this option.\n\nIf the value of $SYSTEMDLESS does not include \"K\", and the\npager that is invoked is less, Ctrl+C will be ignored by the\nexecutable, and needs to be handled by the pager.\n\nX\nThis option instructs the pager to not send termcap\ninitialization and deinitialization strings to the terminal. It\nis set by default to allow command output to remain visible in\nthe terminal even after the pager exits. Nevertheless, this\nprevents some pager functionality from working, in particular\npaged output cannot 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\ninvoking terminal is determined to be UTF-8 compatible).\n\n$SYSTEMDPAGERSECURE\nTakes a boolean argument. When true, the \"secure\" mode of the pager\nis enabled; if false, disabled. If $SYSTEMDPAGERSECURE is not set\nat all, secure mode is enabled if the effective UID is not the same\nas the owner of the login session, see geteuid(2) and\nsdpidgetowneruid(3). In secure mode, LESSSECURE=1 will be set\nwhen invoking the pager, and the pager shall disable commands that\nopen or create new files or start new subprocesses. When\n$SYSTEMDPAGERSECURE is not set at all, pagers which are not known\nto implement secure mode will not be used. (Currently only less(1)\nimplements secure mode.)\n\nNote: when commands are invoked with elevated privileges, for\nexample under sudo(8) or pkexec(1), care must be taken to ensure\nthat unintended interactive features are not enabled. \"Secure\" mode\nfor the pager may be enabled automatically as describe above.\nSetting SYSTEMDPAGERSECURE=0 or not removing it from the inherited\nenvironment allows the user to invoke arbitrary commands. Note that\nif the $SYSTEMDPAGER or $PAGER variables are to be honoured,\n$SYSTEMDPAGERSECURE must be set too. It might be reasonable to\ncompletely disable the pager using --no-pager instead.\n\n$SYSTEMDCOLORS\nTakes a boolean argument. When true, systemd and related utilities\nwill use colors in their output, otherwise the output will be\nmonochrome. Additionally, the variable can take one of the\nfollowing special values: \"16\", \"256\" to restrict the use of colors\nto the base 16 or 256 ANSI colors, respectively. This can be\nspecified to override the automatic decision based on $TERM and\nwhat the console is connected to.\n\n$SYSTEMDURLIFY\nThe value must be a boolean. Controls whether clickable links\nshould be generated in the output for terminal emulators supporting\nthis. This can be specified to override the decision that systemd\nmakes based on $TERM and other conditions.\n\n$LISTENPID, $LISTENFDS, $LISTENFDNAMES\nSet by systemd for supervised processes during socket-based\nactivation. See sdlistenfds(3) for more information.\n\n$NOTIFYSOCKET\nSet by systemd for supervised processes for status and start-up\ncompletion notification. See sdnotify(3) for more information.\n\nFor further environment variables understood by systemd and its various\ncomponents, see Known Environment Variables[7].\n", "subsections": [] }, "KERNEL COMMAND LINE": { "content": "When run as the system instance systemd parses a number of options\nlisted below. They can be specified as kernel command line\narguments[8], or through the \"SystemdOptions\" EFI variable (on EFI\nsystems). The kernel command line has higher priority. Following\nvariables are understood:\n\nsystemd.unit=, rd.systemd.unit=\nOverrides the unit to activate on boot. Defaults to default.target.\nThis may be used to temporarily boot into a different boot unit,\nfor example rescue.target or emergency.service. See\nsystemd.special(7) for details about these units. The option\nprefixed with \"rd.\" is honored only in the initial RAM disk\n(initrd), while the one that is not prefixed only in the main\nsystem.\n\nsystemd.dumpcore\nTakes a boolean argument or enables the option if specified without\nan argument. If enabled, the systemd manager (PID 1) dumps core\nwhen it crashes. Otherwise, no core dump is created. Defaults to\nenabled.\n\nsystemd.crashchvt\nTakes a positive integer, or a boolean argument. Can be also\nspecified without an argument, with the same effect as a positive\nboolean. If a positive integer (in the range 1-63) is specified,\nthe system manager (PID 1) will activate the specified virtual\nterminal when it crashes. Defaults to disabled, meaning that no\nsuch switch is attempted. If set to enabled, the virtual terminal\nthe kernel messages are written to is used instead.\n\nsystemd.crashshell\nTakes a boolean argument or enables the option if specified without\nan argument. If enabled, the system manager (PID 1) spawns a shell\nwhen it crashes, after a 10s delay. Otherwise, no shell is spawned.\nDefaults to disabled, for security reasons, as the shell is not\nprotected by password authentication.\n\nsystemd.crashreboot\nTakes a boolean argument or enables the option if specified without\nan argument. If enabled, the system manager (PID 1) will reboot the\nmachine automatically when it crashes, after a 10s delay.\nOtherwise, the system will hang indefinitely. Defaults to disabled,\nin order to avoid a reboot loop. If combined with\nsystemd.crashshell, the system is rebooted after the shell exits.\n\nsystemd.confirmspawn\nTakes a boolean argument or a path to the virtual console where the\nconfirmation messages should be emitted. Can be also specified\nwithout an argument, with the same effect as a positive boolean. If\nenabled, the system manager (PID 1) asks for confirmation when\nspawning processes using /dev/console. If a path or a console name\n(such as \"ttyS0\") is provided, the virtual console pointed to by\nthis path or described by the give name will be used instead.\nDefaults to disabled.\n\nsystemd.servicewatchdogs=\nTakes a boolean argument. If disabled, all service runtime\nwatchdogs (WatchdogSec=) and emergency actions (e.g. OnFailure= or\nStartLimitAction=) are ignored by the system manager (PID 1); see\nsystemd.service(5). Defaults to enabled, i.e. watchdogs and failure\nactions are processed normally. The hardware watchdog is not\naffected by this option.\n\nsystemd.showstatus\nTakes a boolean argument or the constants error and auto. Can be\nalso specified without an argument, with the same effect as a\npositive boolean. If enabled, the systemd manager (PID 1) shows\nterse service status updates on the console during bootup. With\nerror, only messages about failures are shown, but boot is\notherwise quiet. auto behaves like false until there is a\nsignificant delay in boot. Defaults to enabled, unless quiet is\npassed as kernel command line option, in which case it defaults to\nerror. If specified overrides the system manager configuration file\noption ShowStatus=, see systemd-system.conf(5).\n\nsystemd.statusunitformat=\nTakes name, description or combined as the value. If name, the\nsystem manager will use unit names in status messages. If combined,\nthe system manager will use unit names and description in status\nmessages. When specified, overrides the system manager\nconfiguration file option StatusUnitFormat=, see systemd-\nsystem.conf(5).\n\nsystemd.logcolor, systemd.loglevel=, systemd.loglocation,\nsystemd.logtarget=, systemd.logtime, systemd.logtid\nControls log output, with the same effect as the\n$SYSTEMDLOGCOLOR, $SYSTEMDLOGLEVEL, $SYSTEMDLOGLOCATION,\n$SYSTEMDLOGTARGET, $SYSTEMDLOGTIME, and $SYSTEMDLOGTID\nenvironment variables described above. systemd.logcolor,\nsystemd.loglocation, systemd.logtime, and systemd.logtid= can be\nspecified without an argument, with the same effect as a positive\nboolean.\n\nsystemd.defaultstandardoutput=, systemd.defaultstandarderror=\nControls default standard output and error output for services and\nsockets. That is, controls the default for StandardOutput= and\nStandardError= (see systemd.exec(5) for details). Takes one of\ninherit, null, tty, journal, journal+console, kmsg, kmsg+console.\nIf the argument is omitted systemd.default-standard-output=\ndefaults to journal and systemd.default-standard-error= to inherit.\n\nsystemd.setenv=\nTakes a string argument in the form VARIABLE=VALUE. May be used to\nset default environment variables to add to forked child processes.\nMay be used more than once to set multiple variables.\n\nsystemd.machineid=\nTakes a 32 character hex value to be used for setting the\nmachine-id. Intended mostly for network booting where the same\nmachine-id is desired for every boot.\n\nsystemd.unifiedcgrouphierarchy\nWhen specified without an argument or with a true argument, enables\nthe usage of unified cgroup hierarchy[9] (a.k.a. cgroups-v2). When\nspecified with a false argument, fall back to hybrid or full legacy\ncgroup hierarchy.\n\nIf this option is not specified, the default behaviour is\ndetermined during compilation (the -Ddefault-hierarchy= meson\noption). If the kernel does not support unified cgroup hierarchy,\nthe 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\nprevious option). When specified without an argument or with a true\nargument, disables the use of \"hybrid\" cgroup hierarchy (i.e. a\ncgroups-v2 tree used for systemd, and legacy cgroup hierarchy[10],\na.k.a. cgroups-v1, for other controllers), and forces a full\n\"legacy\" mode. When specified with a false argument, enables the\nuse of \"hybrid\" hierarchy.\n\nIf this option is not specified, the default behaviour is\ndetermined during compilation (the -Ddefault-hierarchy= meson\noption). If the kernel does not support unified cgroup hierarchy,\nthe legacy hierarchy will be used even if this option is specified.\n\nquiet\nTurn off status output at boot, much like systemd.showstatus=no\nwould. Note that this option is also read by the kernel itself and\ndisables kernel log output. Passing this option hence turns off the\nusual output from both the system manager and the kernel.\n\ndebug\nTurn on debugging output. This is equivalent to\nsystemd.loglevel=debug. Note that this option is also read by the\nkernel itself and enables kernel debug output. Passing this option\nhence turns on the debug output from both the system manager and\nthe kernel.\n\nemergency, rd.emergency, -b\nBoot into emergency mode. This is equivalent to\nsystemd.unit=emergency.target or rd.systemd.unit=emergency.target,\nrespectively, and provided for compatibility reasons and to be\neasier to type.\n\nrescue, rd.rescue, single, s, S, 1\nBoot into rescue mode. This is equivalent to\nsystemd.unit=rescue.target or rd.systemd.unit=rescue.target,\nrespectively, and provided for compatibility reasons and to be\neasier to type.\n\n2, 3, 4, 5\nBoot into the specified legacy SysV runlevel. These are equivalent\nto systemd.unit=runlevel2.target, systemd.unit=runlevel3.target,\nsystemd.unit=runlevel4.target, and systemd.unit=runlevel5.target,\nrespectively, and provided for compatibility reasons and to be\neasier to type.\n\nlocale.LANG=, locale.LANGUAGE=, locale.LCCTYPE=, locale.LCNUMERIC=,\nlocale.LCTIME=, locale.LCCOLLATE=, locale.LCMONETARY=,\nlocale.LCMESSAGES=, locale.LCPAPER=, locale.LCNAME=,\nlocale.LCADDRESS=, locale.LCTELEPHONE=, locale.LCMEASUREMENT=,\nlocale.LCIDENTIFICATION=\nSet the system locale to use. This overrides the settings in\n/etc/locale.conf. For more information, see locale.conf(5) and\nlocale(7).\n\nFor other kernel command line parameters understood by components of\nthe core OS, please refer to kernel-command-line(7).\n", "subsections": [] }, "OPTIONS": { "content": "systemd is only very rarely invoked directly, since it is started early\nand is already running by the time users may interact with it.\nNormally, tools like systemctl(1) are used to give commands to the\nmanager. Since systemd is usually not invoked directly, the options\nlisted below are mostly useful for debugging and special purposes.\n\nIntrospection and debugging options\nThose options are used for testing and introspection, and systemd may\nbe invoked with them at any time:\n", "subsections": [ { "name": "--dump-configuration-items", "content": "Dump understood unit configuration items. This outputs a terse but\ncomplete list of configuration items understood in unit definition\nfiles.\n", "long": "--dump-configuration-items" }, { "name": "--dump-bus-properties", "content": "Dump exposed bus properties. This outputs a terse but complete list\nof properties exposed on D-Bus.\n", "long": "--dump-bus-properties" }, { "name": "--test", "content": "Determine the initial start-up transaction (i.e. the list of jobs\nenqueued at start-up), dump it and exit -- without actually\nexecuting any of the determined jobs. This option is useful for\ndebugging only. Note that during regular service manager start-up\nadditional units not shown by this operation may be started,\nbecause hardware, socket, bus or other kinds of activation might\nadd additional jobs as the transaction is executed. Use --system to\nrequest the initial transaction of the system service manager (this\nis also the implied default), combine with --user to request the\ninitial transaction of the per-user service manager instead.\n", "long": "--test" }, { "name": "--system, --user", "content": "When used in conjunction with --test, selects whether to calculate\nthe initial transaction for the system instance or for a per-user\ninstance. These options have no effect when invoked without --test,\nas during regular (i.e. non---test) invocations the service manager\nwill automatically detect whether it shall operate in system or\nper-user mode, by checking whether the PID it is run as is 1 or\nnot. Note that it is not supported booting and maintaining a system\nwith the service manager running in --system mode but with a PID\nother than 1.\n", "long": "--user" }, { "name": "-h, --help", "content": "Print a short help text and exit.\n", "flag": "-h", "long": "--help" }, { "name": "--version", "content": "Print a short version string and exit.\n\nOptions that duplicate kernel command line settings\nThose options correspond directly to options listed above in \"Kernel\nCommand Line\". Both forms may be used equivalently for the system\nmanager, but it is recommended to use the forms listed above in this\ncontext, because they are properly namespaced. When an option is\nspecified both on the kernel command line and as a normal command line\nargument, the latter has higher precedence.\n\nWhen systemd is used as a user manager, the kernel command line is\nignored and only the options described below are understood.\nNevertheless, systemd is usually started in this mode through the\nuser@.service(5) service, which is shared between all users. It may be\nmore convenient to use configuration files to modify settings (see\nsystemd-user.conf(5)), or environment variables. See the \"Environment\"\nsection above for a discussion of how the environment block is set.\n\n--unit=\nSet default unit to activate on startup. If not specified, defaults\nto default.target. See systemd.unit= above.\n", "long": "--version" }, { "name": "--dump-core", "content": "Enable core dumping on crash. This switch has no effect when\nrunning as user instance. Same as systemd.dumpcore= above.\n\n--crash-vt=VT\nSwitch to a specific virtual console (VT) on crash. This switch has\nno effect when running as user instance. Same as\nsystemd.crashchvt= above (but not the different spelling!).\n", "long": "--dump-core" }, { "name": "--crash-shell", "content": "Run a shell on crash. This switch has no effect when running as\nuser instance. See systemd.crashshell= above.\n", "long": "--crash-shell" }, { "name": "--crash-reboot", "content": "Automatically reboot the system on crash. This switch has no effect\nwhen running as user instance. See systemd.crashreboot above.\n", "long": "--crash-reboot" }, { "name": "--confirm-spawn", "content": "Ask for confirmation when spawning processes. This switch has no\neffect when run as user instance. See systemd.confirmspawn above.\n", "long": "--confirm-spawn" }, { "name": "--show-status", "content": "Show terse unit status information on the console during boot-up\nand shutdown. See systemd.showstatus above.\n", "long": "--show-status" }, { "name": "--log-color", "content": "Highlight important log messages. See systemd.logcolor above.\n\n--log-level=\nSet log level. See systemd.loglevel above.\n", "long": "--log-color" }, { "name": "--log-location", "content": "Include code location in log messages. See systemd.loglocation\nabove.\n\n--log-target=\nSet log target. See systemd.logtarget above.\n\n--log-time=\nPrefix console messages with timestamp. See systemd.logtime above.\n\n--machine-id=\nOverride the machine-id set on the hard drive. See\nsystemd.machineid= above.\n", "long": "--log-location" }, { "name": "--service-watchdogs", "content": "Globally enable/disable all service watchdog timeouts and emergency\nactions. See systemd.servicewatchdogs above.\n\n--default-standard-output=, --default-standard-error=\nSets the default output or error output for all services and\nsockets, respectively. See systemd.defaultstandardoutput= and\nsystemd.defaultstandarderror= above.\n", "long": "--service-watchdogs" } ] }, "SOCKETS AND FIFOS": { "content": "/run/systemd/notify\nDaemon status notification socket. This is an AFUNIX datagram\nsocket and is used to implement the daemon notification logic as\nimplemented by sdnotify(3).\n\n/run/systemd/private\nUsed internally as communication channel between systemctl(1) and\nthe systemd process. This is an AFUNIX stream socket. This\ninterface is private to systemd and should not be used in external\nprojects.\n\n/dev/initctl\nLimited compatibility support for the SysV client interface, as\nimplemented by the systemd-initctl.service unit. This is a named\npipe in the file system. This interface is obsolete and should not\nbe used in new applications.\n", "subsections": [] }, "SEE ALSO": { "content": "runit(8), runsvdir(8), runsvchdir(8), sv(8), runsv(8), chpst(8),\nutmpset(8), svlogd(8)\n\nhttp://smarden.org/runit/\n", "subsections": [] }, "NOTES": { "content": "1. 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\ncommand line arguments to systemd itself, next to any of the\ncommand line options listed in the Options section above. If run\noutside of Linux containers, these arguments are parsed from\n/proc/cmdline instead.\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\nsystemd 249 SYSTEMD(1)\nrunit-init(8) System Manager's Manual runit-init(8)\n", "subsections": [] }, "EXIT CODES": { "content": "runit-init returns 111 on error, 0 in all other cases.\n", "subsections": [] }, "AUTHOR": { "content": "Gerrit Pape \n\nrunit-init(8)", "subsections": [] } }, "summary": "systemd, init - systemd system and service manager", "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." }, { "flag": "", "long": "--user", "arg": null, "description": "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. Options that duplicate kernel command line settings Those options correspond directly to options listed above in \"Kernel Command Line\". Both forms may be used equivalently for the system manager, but it is recommended to use the forms listed above in this context, because they are properly namespaced. When an option is specified both on the kernel command line and as a normal command line argument, the latter has higher precedence. When systemd is used as a user manager, the kernel command line is ignored and only the options described below are understood. Nevertheless, systemd is usually started in this mode through the user@.service(5) service, which is shared between all users. It may be more convenient to use configuration files to modify settings (see systemd-user.conf(5)), or environment variables. See the \"Environment\" section above for a discussion of how the environment block is set. --unit= 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. --log-level= Set log level. See systemd.loglevel above." }, { "flag": "", "long": "--log-location", "arg": null, "description": "Include code location in log messages. See systemd.loglocation above. --log-target= Set log target. See systemd.logtarget above. --log-time= Prefix console messages with timestamp. See systemd.logtime above. --machine-id= 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": "daemon", "section": "3", "url": "https://www.chedong.com/phpMan.php/man/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" } ] }