Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

systemd.conf(5) [debian man page]

SYSTEMD.CONF(5) 						   systemd.conf 						   SYSTEMD.CONF(5)

NAME
systemd.conf - systemd manager configuration file SYNOPSIS
system.conf user.conf DESCRIPTION
When run as system instance systemd reads the configuration file system.conf, otherwise user.conf. These configuration files contain a few settings controlling basic manager operations. OPTIONS
All options are configured in the [Manager] section: LogLevel=, LogTarget=, LogColor=, LogLocation=, DumpCore=yes, CrashShell=no, ShowStatus=yes, SysVConsole=yes, CrashChVT=1, DefaultStandardOutput=journal, DefaultStandardError=inherit Configures various parameters of basic manager operation. These options may be overridden by the respective command line arguments. See systemd(1) for details about these command line arguments. CPUAffinity= Configures the initial CPU affinity for the init process. Takes a space-separated list of CPU indexes. MountAuto=yes, SwapAuto=yes Configures whether systemd should automatically activate all swap or mounts listed in /etc/fstab, or whether this job is left to some other system script. DefaultControllers=cpu Configures in which cgroup controller hierarchies to create per-service cgroups automatically, in addition to the name=systemd named hierarchy. Defaults to 'cpu'. Takes a space separated list of controller names. Pass an empty string to ensure that systemd does not touch any hierarchies but its own. JoinControllers=cpu,cpuacct Configures controllers that shall be mounted in a single hierarchy. By default systemd will mount all controllers which are enabled in the kernel in individual hierachies, with the exception of those listed in this setting. Takes a space separated list of comma separated controller names, in order to allow multiple joined hierarchies. Defaults to 'cpu,cpuacct'. Pass an empty string to ensure that systemd mounts all controllers in separate hierarchies. SEE ALSO
systemd(1) AUTHOR
Lennart Poettering <lennart@poettering.net> Developer systemd 10/07/2013 SYSTEMD.CONF(5)

Check Out this Related Man Page

SYSTEMD-LOGIND.CO(5)						systemd-logind.conf					      SYSTEMD-LOGIND.CO(5)

NAME
systemd-logind.conf - Login manager configuration file SYNOPSIS
systemd-logind.conf DESCRIPTION
This files configures various parameters of the systemd login manager. OPTIONS
All options are configured in the [Login] section: NAutoVTs= Takes a positive integer. How many virtual terminals to allocate by default and when switched to autospawn autovt services on (if they are otherwise unused). These services are instantiated from a template of autovt@.service with the virtual terminal TTY name, e.g. autovt@tty4.service. By default autovt@.service is linked to getty@.service, i.e. login prompts are started dynamically as the user switches to unused virtual terminals, and this parameter hence controls how many gettys are available on the virtual terminals. Defaults to 6. When set to 0, automatic spawning of autovt services is disabled. KillUserProcesses= Takes a boolean argument. Configures whether the processes of a user should be killed when she or he completely logs out (i.e. after her/his last session ended). Defaults to no. KillOnlyUsers=, KillExcludeUsers= These settings take space separated lists of user names that influence the effect of KillUserProcesses=. If not empty only processes of users listed in KillOnlyUsers will be killed when they log out entirely. Processes of users listed in KillExcludeUsers= are excluded from being killed. KillExcludeUsers= defaults to root and takes precedence over KillOnlyUsers= which defaults to the empty list. Controllers=, ResetControllers= These settings control the default control group hierarchies users logging are added to. When logging in users will get private control groups in all hierarchies listed in Controllers= and be reset to the root control group in all hierarchies listed in ResetControllers=. Controllers= defaults to the empty list, ResetControllers= defaults to cpu. Note that setting KillUserProcesses=1 will break tools like screen(1). Note that KillUserProcesses=1 is a weaker version of kill-session-processes=1 which may be configured per-service for pam_systemd(8). The latter kills processes of a session as soon as it ends, the former kills processes as soon as the last session of the user ends. SEE ALSO
systemd(1), systemd-loginctl(1), systemd.conf(5) AUTHOR
Lennart Poettering <lennart@poettering.net> Developer systemd 10/07/2013 SYSTEMD-LOGIND.CO(5)
Man Page

Featured Tech Videos