Bug#1071629: loginctl.1: some remarks and editorial changes for this man page
Bjarni Ingi Gislason
bjarniig at simnet.is
Wed May 22 16:11:06 BST 2024
Package: systemd
Version: 255.5-1
Severity: minor
Tags: patch
Dear Maintainer,
here are some notes and editorial fixes for the manual 'loginctl.1'.
The patch is in the attachment.
-.-
The difference between the formatted outputs can be seen with:
nroff -man <file1> > <out1>
nroff -man <file2> > <out2>
diff -u <out1> <out2>
and for groff, using
"printf '%s\n%s\n' '.kern 0' '.ss 12 0' | groff -man -Z - "
instead of "nroff -man"
Add the option "-t", if the file contains a table.
Read the output of "diff -u" with "less -R" or similar.
-.-.
If "man" (man-db) is used to check the manual for warnings,
the following must be set:
The option "-warnings=w"
The environmental variable:
export MAN_KEEP_STDERR=yes (or any non-empty value)
or
(produce only warnings):
export MANROFFOPT="-ww -z"
export MAN_KEEP_STDERR=yes (or any non-empty value)
-.-.
Output from "mandoc -T lint loginctl.1": (possibly shortened list)
mandoc: loginctl.1:2:20: WARNING: missing date, using "": TH
mandoc: loginctl.1:28:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:35:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:38:2: WARNING: skipping paragraph macro: PP after SS
mandoc: loginctl.1:46:384: STYLE: input text line longer than 80 bytes: Show terse runtime s...
mandoc: loginctl.1:55:235: STYLE: input text line longer than 80 bytes: Show properties of o...
mandoc: loginctl.1:61:123: STYLE: input text line longer than 80 bytes: if exists, and falls...
mandoc: loginctl.1:73:262: STYLE: input text line longer than 80 bytes: Activate a session\&...
mandoc: loginctl.1:80:223: STYLE: input text line longer than 80 bytes: Activates/deactivate...
mandoc: loginctl.1:94:215: STYLE: input text line longer than 80 bytes: Terminates a session...
mandoc: loginctl.1:105:134: STYLE: input text line longer than 80 bytes: to select the signal...
mandoc: loginctl.1:110:2: WARNING: skipping paragraph macro: PP after SS
mandoc: loginctl.1:118:407: STYLE: input text line longer than 80 bytes: Show terse runtime s...
mandoc: loginctl.1:127:244: STYLE: input text line longer than 80 bytes: Show properties of o...
mandoc: loginctl.1:139:400: STYLE: input text line longer than 80 bytes: Enable/disable user ...
mandoc: loginctl.1:151:260: STYLE: input text line longer than 80 bytes: Terminates all sessi...
mandoc: loginctl.1:160:147: STYLE: input text line longer than 80 bytes: to select the signal...
mandoc: loginctl.1:165:2: WARNING: skipping paragraph macro: PP after SS
mandoc: loginctl.1:173:318: STYLE: input text line longer than 80 bytes: Show terse runtime s...
mandoc: loginctl.1:182:244: STYLE: input text line longer than 80 bytes: Show properties of o...
mandoc: loginctl.1:194:108: STYLE: input text line longer than 80 bytes: Persistently attach ...
mandoc: loginctl.1:196:161: STYLE: input text line longer than 80 bytes: file system\&. To cr...
mandoc: loginctl.1:201:105: STYLE: input text line longer than 80 bytes: "seat"\&. To drop as...
mandoc: loginctl.1:215:147: STYLE: input text line longer than 80 bytes: Terminates all sessi...
mandoc: loginctl.1:220:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:230:204: STYLE: input text line longer than 80 bytes: When showing session...
mandoc: loginctl.1:231:95: STYLE: input text line longer than 80 bytes: "Sessions"\&. If spe...
mandoc: loginctl.1:236:95: STYLE: input text line longer than 80 bytes: When showing session...
mandoc: loginctl.1:244:107: STYLE: input text line longer than 80 bytes: When showing session...
mandoc: loginctl.1:260:130: STYLE: input text line longer than 80 bytes: "all", to select whe...
mandoc: loginctl.1:280:87: STYLE: input text line longer than 80 bytes: will list the known ...
mandoc: loginctl.1:282:103: STYLE: input text line longer than 80 bytes: will list known valu...
mandoc: loginctl.1:309:93: STYLE: input text line longer than 80 bytes: Execute the operatio...
mandoc: loginctl.1:310:105: STYLE: input text line longer than 80 bytes: "@", to connect to\&...
mandoc: loginctl.1:312:184: STYLE: input text line longer than 80 bytes: "/", which connects ...
mandoc: loginctl.1:318:147: STYLE: input text line longer than 80 bytes: Execute operation on...
mandoc: loginctl.1:322:143: STYLE: input text line longer than 80 bytes: is used in place of ...
mandoc: loginctl.1:327:131: STYLE: input text line longer than 80 bytes: syntax is used eithe...
mandoc: loginctl.1:352:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:355:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:384:196: STYLE: input text line longer than 80 bytes: There are two sessio...
mandoc: loginctl.1:386:2: WARNING: skipping paragraph macro: PP after SH
mandoc: loginctl.1:389:179: STYLE: input text line longer than 80 bytes: The maximum log leve...
mandoc: loginctl.1:404:90: STYLE: input text line longer than 80 bytes: A boolean\&. If true...
mandoc: loginctl.1:406:87: STYLE: input text line longer than 80 bytes: This setting is only...
mandoc: loginctl.1:408:92: STYLE: input text line longer than 80 bytes: and other tools that...
mandoc: loginctl.1:415:97: STYLE: input text line longer than 80 bytes: This setting is only...
mandoc: loginctl.1:417:100: STYLE: input text line longer than 80 bytes: and other tools that...
mandoc: loginctl.1:422:130: STYLE: input text line longer than 80 bytes: A boolean\&. If true...
mandoc: loginctl.1:424:185: STYLE: input text line longer than 80 bytes: Note that the log lo...
mandoc: loginctl.1:429:93: STYLE: input text line longer than 80 bytes: A boolean\&. If true...
mandoc: loginctl.1:431:183: STYLE: input text line longer than 80 bytes: Note that the this i...
mandoc: loginctl.1:440:85: STYLE: input text line longer than 80 bytes: (log to the attached...
mandoc: loginctl.1:515:354: STYLE: input text line longer than 80 bytes: This option instruct...
mandoc: loginctl.1:545:106: STYLE: input text line longer than 80 bytes: Takes a boolean argu...
mandoc: loginctl.1:547:117: STYLE: input text line longer than 80 bytes: is not set at all, s...
mandoc: loginctl.1:552:137: STYLE: input text line longer than 80 bytes: will be set when inv...
mandoc: loginctl.1:554:106: STYLE: input text line longer than 80 bytes: is not set at all, p...
mandoc: loginctl.1:563:114: STYLE: input text line longer than 80 bytes: or not removing it f...
mandoc: loginctl.1:578:170: STYLE: input text line longer than 80 bytes: and related utilitie...
mandoc: loginctl.1:581:146: STYLE: input text line longer than 80 bytes: to restrict the use ...
mandoc: loginctl.1:588:191: STYLE: input text line longer than 80 bytes: The value must be a ...
mandoc: loginctl.1:595:2: WARNING: skipping paragraph macro: PP after SH
-.-.
Mark a full stop (.) and the exclamation mark (!) with "\&",
if it does not mean an end of a sentence.
This is a preventive action,
the paragraph could be reshaped, e.g., after changes.
When typing, one does not always notice when the line wraps after the
period.
There are too many examples of input lines in manual pages,
that end with an abbreviation point.
This marking is robust, and independent of the position on the line.
It corresponds to "\ " in TeX, and to "@:" in Texinfo.
26:\fBloginctl\fR [OPTIONS...] {COMMAND} [NAME...]
339:Do not print the legend, i\&.e\&. column headers and the footer with hints\&.
389:The maximum log level of emitted messages (messages with a higher log level, i\&.e\&. less important ones, will be suppressed)\&. Either one of (in order of decreasing importance)
554:is not set at all, pagers which are not known to implement secure mode will not be used\&. (Currently only
561:\fBpkexec\fR(1), care must be taken to ensure that unintended interactive features are not enabled\&. "Secure" mode for the pager may be enabled automatically as describe above\&. Setting
-.-.
Separate the sentences and subordinate clauses; each begins on a new
line. See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").
The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.
Remember coding: Only one command ("sentence") on each (logical) line.
E-mail: Easier to quote exactly the relevant lines.
Generally: Easier to edit the sentence.
Patches: Less unaffected text.
Search for two adjacent words is easier, when they belong to the same line,
and the same phrase.
The amount of space between sentences in the output can then be
controlled with the ".ss" request.
N.B
The number of lines affected is too large to be in the patch.
46:Show terse runtime status information about one or more sessions, followed by the most recent log data from the journal\&. Takes one or more session identifiers as parameters\&. If no session identifiers are passed, the status of the caller\*(Aqs session is shown\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
55:Show properties of one or more sessions or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a session ID is specified, properties of the session are shown\&. Specially, if the given ID is
58:process belongs is used\&. If
61:if exists, and falls back to the current user\*(Aqs graphical session\&. By default, empty properties are suppressed\&. Use
63:to show those too\&. To select specific properties to show, use
64:\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
73:Activate a session\&. This brings a session into the foreground if another session is currently in the foreground on the respective seat\&. Takes a session identifier as argument\&. If no argument is specified, the session of the caller is put into foreground\&.
80:Activates/deactivates the screen lock on one or more sessions, if the session supports it\&. Takes one or more session identifiers as arguments\&. If no argument is specified, the session of the caller is locked/unlocked\&.
94:Terminates a session\&. This kills all processes of the session and deallocates all resources attached to the session\&. If the argument is specified as empty string the session invoking the command is terminated\&.
101:Send a signal to one or more processes of the session\&. Use
103:to select which process to kill\&. Use
105:to select the signal to send\&. If the argument is specified as empty string the signal is sent to the session invoking the command\&.
118:Show terse runtime status information about one or more logged in users, followed by the most recent log data from the journal\&. Takes one or more user names or numeric user IDs as parameters\&. If no parameters are passed, the status is shown for the user of the session of the caller\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
127:Show properties of one or more users or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a user is specified, properties of the user are shown\&. By default, empty properties are suppressed\&. Use
129:to show those too\&. To select specific properties to show, use
130:\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
139:Enable/disable user lingering for one or more users\&. If enabled for a specific user, a user manager is spawned for the user at boot and kept around after logouts\&. This allows users who are not logged in to run long\-running services\&. Takes one or more user names or numeric UIDs as argument\&. If no argument is specified, enables/disables lingering for the user of the session of the caller\&.
151:Terminates all sessions of a user\&. This kills all processes of all sessions of the user and deallocates all runtime resources attached to the user\&. If the argument is specified as empty string the sessions of the user invoking the command are terminated\&.
158:Send a signal to all processes of a user\&. Use
160:to select the signal to send\&. If the argument is specified as empty string the signal is sent to the sessions of the user invoking the command\&.
173:Show terse runtime status information about one or more seats\&. Takes one or more seat names as parameters\&. If no seat names are passed the status of the caller\*(Aqs session\*(Aqs seat is shown\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
182:Show properties of one or more seats or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a seat is specified, properties of the seat are shown\&. By default, empty properties are suppressed\&. Use
184:to show those too\&. To select specific properties to show, use
185:\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
194:Persistently attach one or more devices to a seat\&. The devices should be specified via device paths in the
196:file system\&. To create a new seat, attach at least one graphics card to a previously unused seat name\&. Seat names may consist only of a\(enz, A\(enZ, 0\(en9,
201:"seat"\&. To drop assignment of a device to a specific seat, just reassign it to a different seat, or use
210:\fBattach\fR\&. After this call, only automatically generated seats will remain, and all seat hardware is assigned to them\&.
215:Terminates all sessions on a seat\&. This kills all processes of all sessions on the seat and deallocates all runtime resources attached to them\&.
230:When showing session/user/seat properties, limit display to certain properties as specified as argument\&. If not specified, all set properties are shown\&. The argument should be a property name, such as
231:"Sessions"\&. If specified more than once, all properties with the specified names are shown\&.
257:\fBkill\-session\fR, choose which processes to kill\&. Takes one of
260:"all", to select whether to kill only the leader process of the session or all processes of the session\&. If omitted, defaults to
271:\fBkill\-user\fR, choose which signal to send to selected processes\&. Must be one of the well known signal specifiers, such as
275:\fBSIGSTOP\fR\&. If omitted, defaults to
290:\fBsession\-status\fR, controls the number of journal lines to show, counting from the most recent ones\&. Takes a positive integer argument\&. Defaults to 10\&.
300:\fBsession\-status\fR, controls the formatting of the journal entries that are shown\&. For the available choices, see
301:\fBjournalctl\fR(1)\&. Defaults to
309:Execute the operation remotely\&. Specify a hostname, or a username and hostname separated by
310:"@", to connect to\&. The hostname may optionally be suffixed by a port ssh is listening on, separated by
312:"/", which connects directly to a specific container on the specified host\&. This will use SSH to talk to the remote machine manager instance\&. Container names may be enumerated with
313:\fBmachinectl \-H \fR\fB\fIHOST\fR\fR\&. Put IPv6 addresses in brackets\&.
318:Execute operation on a local container\&. Specify a container name to connect to, optionally prefixed by a user name to connect as and a separating
320:character\&. If the special string
323:"\-\-user \-\-machine=lennart@\&.host")\&. If the
325:syntax is not used, the connection is made as root user\&. If the
339:Do not print the legend, i\&.e\&. column headers and the footer with hints\&.
384:There are two sessions, 3 and 5\&. Session 3 is a graphical session, marked with a star\&. The tree of processing including the two corresponding scope units and the user manager unit are shown\&.
389:The maximum log level of emitted messages (messages with a higher log level, i\&.e\&. less important ones, will be suppressed)\&. Either one of (in order of decreasing importance)
397:\fBdebug\fR, or an integer in the range 0\&...7\&. See
404:A boolean\&. If true, messages written to the tty will be colored according to priority\&.
413:A boolean\&. If true, console log messages will be prefixed with a timestamp\&.
422:A boolean\&. If true, messages will be prefixed with a filename and line number in the source code where the message originates\&.
424:Note that the log location is often attached as metadata to journal entries anyway\&. Including it directly in the message text can nevertheless be convenient when debugging programs\&.
429:A boolean\&. If true, messages will be prefixed with the current numerical thread ID (TID)\&.
431:Note that the this information is attached as metadata to journal entries anyway\&. Including it directly in the message text can nevertheless be convenient when debugging programs\&.
436:The destination for log messages\&. One of
456:Whether to ratelimit kmsg or not\&. Takes a boolean\&. Defaults to
457:"true"\&. If disabled, systemd will not ratelimit messages written to kmsg\&.
465:\fI$PAGER\fR\&. If neither
472:\fBmore\fR(1), until one is found\&. If no pager implementation is discovered no pager is invoked\&. Setting this environment variable to an empty string or the value
498:is pressed\&. To allow
515:This option instructs the pager to not send termcap initialization and deinitialization strings to the terminal\&. It is set by default to allow command output to remain visible in the terminal even after the pager exits\&. Nevertheless, this prevents some pager functionality from working, in particular paged output cannot be scrolled with the mouse\&.
545:Takes a boolean argument\&. When true, the "secure" mode of the pager is enabled; if false, disabled\&. If
550:\fBsd_pid_get_owner_uid\fR(3)\&. In secure mode,
552:will be set when invoking the pager, and the pager shall disable commands that open or create new files or start new subprocesses\&. When
554:is not set at all, pagers which are not known to implement secure mode will not be used\&. (Currently only
561:\fBpkexec\fR(1), care must be taken to ensure that unintended interactive features are not enabled\&. "Secure" mode for the pager may be enabled automatically as describe above\&. Setting
563:or not removing it from the inherited environment allows the user to invoke arbitrary commands\&. Note that if the
569:must be set too\&. It might be reasonable to completely disable the pager using
576:Takes a boolean argument\&. When true,
578:and related utilities will use colors in their output, otherwise the output will be monochrome\&. Additionally, the variable can take one of the following special values:
581:to restrict the use of colors to the base 16 or 256 ANSI colors, respectively\&. This can be specified to override the automatic decision based on
588:The value must be a boolean\&. Controls whether clickable links should be generated in the output for terminal emulators supporting this\&. This can be specified to override the decision that
-.-.
Test nr. 32:
Split lines longer than 80 characters into two or more lines.
Appropriate break points are the end of a sentence and a subordinate
clause; after punctuation marks.
loginctl.1: line 46 length 384
Show terse runtime status information about one or more sessions, followed by the most recent log data from the journal\&. Takes one or more session identifiers as parameters\&. If no session identifiers are passed, the status of the caller\*(Aqs session is shown\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
loginctl.1: line 55 length 235
Show properties of one or more sessions or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a session ID is specified, properties of the session are shown\&. Specially, if the given ID is
loginctl.1: line 61 length 123
if exists, and falls back to the current user\*(Aqs graphical session\&. By default, empty properties are suppressed\&. Use
loginctl.1: line 64 length 112
\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
loginctl.1: line 73 length 262
Activate a session\&. This brings a session into the foreground if another session is currently in the foreground on the respective seat\&. Takes a session identifier as argument\&. If no argument is specified, the session of the caller is put into foreground\&.
loginctl.1: line 80 length 223
Activates/deactivates the screen lock on one or more sessions, if the session supports it\&. Takes one or more session identifiers as arguments\&. If no argument is specified, the session of the caller is locked/unlocked\&.
loginctl.1: line 94 length 215
Terminates a session\&. This kills all processes of the session and deallocates all resources attached to the session\&. If the argument is specified as empty string the session invoking the command is terminated\&.
loginctl.1: line 105 length 134
to select the signal to send\&. If the argument is specified as empty string the signal is sent to the session invoking the command\&.
loginctl.1: line 118 length 407
Show terse runtime status information about one or more logged in users, followed by the most recent log data from the journal\&. Takes one or more user names or numeric user IDs as parameters\&. If no parameters are passed, the status is shown for the user of the session of the caller\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
loginctl.1: line 127 length 244
Show properties of one or more users or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a user is specified, properties of the user are shown\&. By default, empty properties are suppressed\&. Use
loginctl.1: line 130 length 112
\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
loginctl.1: line 139 length 400
Enable/disable user lingering for one or more users\&. If enabled for a specific user, a user manager is spawned for the user at boot and kept around after logouts\&. This allows users who are not logged in to run long\-running services\&. Takes one or more user names or numeric UIDs as argument\&. If no argument is specified, enables/disables lingering for the user of the session of the caller\&.
loginctl.1: line 151 length 260
Terminates all sessions of a user\&. This kills all processes of all sessions of the user and deallocates all runtime resources attached to the user\&. If the argument is specified as empty string the sessions of the user invoking the command are terminated\&.
loginctl.1: line 160 length 147
to select the signal to send\&. If the argument is specified as empty string the signal is sent to the sessions of the user invoking the command\&.
loginctl.1: line 173 length 318
Show terse runtime status information about one or more seats\&. Takes one or more seat names as parameters\&. If no seat names are passed the status of the caller\*(Aqs session\*(Aqs seat is shown\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
loginctl.1: line 182 length 244
Show properties of one or more seats or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a seat is specified, properties of the seat are shown\&. By default, empty properties are suppressed\&. Use
loginctl.1: line 185 length 112
\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
loginctl.1: line 194 length 108
Persistently attach one or more devices to a seat\&. The devices should be specified via device paths in the
loginctl.1: line 196 length 161
file system\&. To create a new seat, attach at least one graphics card to a previously unused seat name\&. Seat names may consist only of a\(enz, A\(enZ, 0\(en9,
loginctl.1: line 201 length 105
"seat"\&. To drop assignment of a device to a specific seat, just reassign it to a different seat, or use
loginctl.1: line 210 length 125
\fBattach\fR\&. After this call, only automatically generated seats will remain, and all seat hardware is assigned to them\&.
loginctl.1: line 215 length 147
Terminates all sessions on a seat\&. This kills all processes of all sessions on the seat and deallocates all runtime resources attached to them\&.
loginctl.1: line 230 length 204
When showing session/user/seat properties, limit display to certain properties as specified as argument\&. If not specified, all set properties are shown\&. The argument should be a property name, such as
loginctl.1: line 231 length 95
"Sessions"\&. If specified more than once, all properties with the specified names are shown\&.
loginctl.1: line 236 length 95
When showing session/user/seat properties, only print the value, and skip the property name and
loginctl.1: line 244 length 107
When showing session/user/seat properties, show all properties regardless of whether they are set or not\&.
loginctl.1: line 260 length 130
"all", to select whether to kill only the leader process of the session or all processes of the session\&. If omitted, defaults to
loginctl.1: line 271 length 127
\fBkill\-user\fR, choose which signal to send to selected processes\&. Must be one of the well known signal specifiers, such as
loginctl.1: line 280 length 87
will list the known values and the program will exit immediately, and the special value
loginctl.1: line 282 length 103
will list known values along with the numerical signal numbers and the program will exit immediately\&.
loginctl.1: line 290 length 161
\fBsession\-status\fR, controls the number of journal lines to show, counting from the most recent ones\&. Takes a positive integer argument\&. Defaults to 10\&.
loginctl.1: line 300 length 118
\fBsession\-status\fR, controls the formatting of the journal entries that are shown\&. For the available choices, see
loginctl.1: line 309 length 93
Execute the operation remotely\&. Specify a hostname, or a username and hostname separated by
loginctl.1: line 310 length 105
"@", to connect to\&. The hostname may optionally be suffixed by a port ssh is listening on, separated by
loginctl.1: line 312 length 184
"/", which connects directly to a specific container on the specified host\&. This will use SSH to talk to the remote machine manager instance\&. Container names may be enumerated with
loginctl.1: line 318 length 147
Execute operation on a local container\&. Specify a container name to connect to, optionally prefixed by a user name to connect as and a separating
loginctl.1: line 322 length 143
is used in place of the container name, a connection to the local system is made (which is useful to connect to a specific user\*(Aqs user bus:
loginctl.1: line 327 length 131
syntax is used either the left hand side or the right hand side may be omitted (but not both) in which case the local user name and
loginctl.1: line 384 length 196
There are two sessions, 3 and 5\&. Session 3 is a graphical session, marked with a star\&. The tree of processing including the two corresponding scope units and the user manager unit are shown\&.
loginctl.1: line 389 length 179
The maximum log level of emitted messages (messages with a higher log level, i\&.e\&. less important ones, will be suppressed)\&. Either one of (in order of decreasing importance)
loginctl.1: line 404 length 90
A boolean\&. If true, messages written to the tty will be colored according to priority\&.
loginctl.1: line 406 length 87
This setting is only useful when messages are written directly to the terminal, because
loginctl.1: line 408 length 92
and other tools that display logs will color messages based on the log level on their own\&.
loginctl.1: line 415 length 97
This setting is only useful when messages are written directly to the terminal or a file, because
loginctl.1: line 417 length 100
and other tools that display logs will attach timestamps based on the entry metadata on their own\&.
loginctl.1: line 422 length 130
A boolean\&. If true, messages will be prefixed with a filename and line number in the source code where the message originates\&.
loginctl.1: line 424 length 185
Note that the log location is often attached as metadata to journal entries anyway\&. Including it directly in the message text can nevertheless be convenient when debugging programs\&.
loginctl.1: line 429 length 93
A boolean\&. If true, messages will be prefixed with the current numerical thread ID (TID)\&.
loginctl.1: line 431 length 183
Note that the this information is attached as metadata to journal entries anyway\&. Including it directly in the message text can nevertheless be convenient when debugging programs\&.
loginctl.1: line 440 length 85
(log to the attached tty but with prefixes encoding the log level and "facility", see
loginctl.1: line 472 length 166
\fBmore\fR(1), until one is found\&. If no pager implementation is discovered no pager is invoked\&. Setting this environment variable to an empty string or the value
loginctl.1: line 515 length 354
This option instructs the pager to not send termcap initialization and deinitialization strings to the terminal\&. It is set by default to allow command output to remain visible in the terminal even after the pager exits\&. Nevertheless, this prevents some pager functionality from working, in particular paged output cannot be scrolled with the mouse\&.
loginctl.1: line 545 length 106
Takes a boolean argument\&. When true, the "secure" mode of the pager is enabled; if false, disabled\&. If
loginctl.1: line 547 length 117
is not set at all, secure mode is enabled if the effective UID is not the same as the owner of the login session, see
loginctl.1: line 552 length 137
will be set when invoking the pager, and the pager shall disable commands that open or create new files or start new subprocesses\&. When
loginctl.1: line 554 length 106
is not set at all, pagers which are not known to implement secure mode will not be used\&. (Currently only
loginctl.1: line 561 length 187
\fBpkexec\fR(1), care must be taken to ensure that unintended interactive features are not enabled\&. "Secure" mode for the pager may be enabled automatically as describe above\&. Setting
loginctl.1: line 563 length 114
or not removing it from the inherited environment allows the user to invoke arbitrary commands\&. Note that if the
loginctl.1: line 578 length 170
and related utilities will use colors in their output, otherwise the output will be monochrome\&. Additionally, the variable can take one of the following special values:
loginctl.1: line 581 length 146
to restrict the use of colors to the base 16 or 256 ANSI colors, respectively\&. This can be specified to override the automatic decision based on
loginctl.1: line 588 length 191
The value must be a boolean\&. Controls whether clickable links should be generated in the output for terminal emulators supporting this\&. This can be specified to override the decision that
Too many to have these in the patch.
-.-.
Remove unnecessary second font change in a row or (better) use a
two-fonts macro.
313:\fBmachinectl \-H \fR\fB\fIHOST\fR\fR\&. Put IPv6 addresses in brackets\&.
-.-.
Output from "test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z -rCHECKSTYLE=0":
troff: backtrace: '<stdin>':368
troff: backtrace: file '<stdin>':368
troff:<stdin>:368: warning: special character 'u251C' not defined
troff: backtrace: file '<stdin>':368
troff:<stdin>:368: warning: special character 'u2500' not defined
troff: backtrace: '<stdin>':372
troff: backtrace: file '<stdin>':372
troff:<stdin>:372: warning: special character 'u2514' not defined
-.-
'\&' is not needed if there is no space in front of the full stop (.), only
after '.', if space follows, like with abbreviations.
-- System Information:
Debian Release: trixie/sid
APT prefers testing-proposed-updates
APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.12-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages systemd depends on:
ii libacl1 2.3.2-2
ii libapparmor1 3.0.13-2
ii libaudit1 1:3.1.2-2
ii libblkid1 2.40.1-1
ii libc6 2.38-11
ii libcap2 1:2.66-5
ii libcryptsetup12 2:2.7.2-2
ii libfdisk1 2.40.1-1
ii libgcrypt20 1.10.3-3
ii libkmod2 31+20240202-2
ii liblz4-1 1.9.4-2
ii liblzma5 5.6.1+really5.4.5-1
ii libmount1 2.40.1-1
ii libpam0g 1.5.3-7
ii libseccomp2 2.5.5-1
ii libselinux1 3.5-2+b2
ii libssl3t64 3.2.1-3
ii libsystemd-shared 255.5-1
ii libsystemd0 255.5-1
ii libzstd1 1.5.5+dfsg2-2
ii mount 2.40.1-1
ii systemd-dev 255.5-1
Versions of packages systemd recommends:
ii dbus [default-dbus-system-bus] 1.14.10-4+b1
pn systemd-timesyncd | time-daemon <none>
Versions of packages systemd suggests:
ii libbpf1 1:1.4.1-1
ii libfido2-1 1.14.0-1+b2
ii libip4tc2 1.8.10-3
ii libp11-kit0 0.25.3-5
pn libpwquality1 <none>
pn libqrencode4 <none>
pn libtss2-esys-3.0.2-0 <none>
pn libtss2-mu-4.0.1-0 <none>
pn libtss2-rc0 <none>
pn libtss2-tcti-device0 <none>
pn polkitd <none>
pn systemd-boot <none>
pn systemd-container <none>
pn systemd-homed <none>
pn systemd-resolved <none>
pn systemd-userdbd <none>
Versions of packages systemd is related to:
pn dbus-user-session <none>
pn dracut <none>
ii initramfs-tools 0.142
pn libnss-systemd <none>
pn libpam-systemd <none>
ii udev 255.5-1
-- no debconf information
-------------- next part --------------
--- loginctl.1 2024-05-22 13:00:15.553748728 +0000
+++ loginctl.1.new 2024-05-22 14:08:42.227420141 +0000
@@ -25,242 +25,236 @@ loginctl \- Control the systemd login ma
.HP \w'\fBloginctl\fR\ 'u
\fBloginctl\fR [OPTIONS...] {COMMAND} [NAME...]
.SH "DESCRIPTION"
-.PP
\fBloginctl\fR
may be used to introspect and control the state of the
\fBsystemd\fR(1)
login manager
-\fBsystemd-logind.service\fR(8)\&.
+\fBsystemd-logind.service\fR(8).
.SH "COMMANDS"
-.PP
The following commands are understood:
.SS "Session Commands"
-.PP
\fBlist\-sessions\fR
.RS 4
-List current sessions\&.
+List current sessions.
.RE
.PP
-\fBsession\-status\fR [\fIID\fR\&...]
+\fBsession\-status\fR [\fIID\fR...]
.RS 4
-Show terse runtime status information about one or more sessions, followed by the most recent log data from the journal\&. Takes one or more session identifiers as parameters\&. If no session identifiers are passed, the status of the caller\*(Aqs session is shown\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
+Show terse runtime status information about one or more sessions, followed by the most recent log data from the journal. Takes one or more session identifiers as parameters. If no session identifiers are passed, the status of the caller\*(Aqs session is shown. This function is intended to generate human\-readable output. If you are looking for computer\-parsable output, use
\fBshow\-session\fR
-instead\&.
+instead.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
-\fBshow\-session\fR [\fIID\fR\&...]
+\fBshow\-session\fR [\fIID\fR...]
.RS 4
-Show properties of one or more sessions or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a session ID is specified, properties of the session are shown\&. Specially, if the given ID is
+Show properties of one or more sessions or the manager itself. If no argument is specified, properties of the manager will be shown. If a session ID is specified, properties of the session are shown. Specially, if the given ID is
"self", the session to which the
\fBloginctl\fR
-process belongs is used\&. If
+process belongs is used. If
"auto", the current session is used as with
"self"
-if exists, and falls back to the current user\*(Aqs graphical session\&. By default, empty properties are suppressed\&. Use
+if exists, and falls back to the current user\*(Aqs graphical session. By default, empty properties are suppressed. Use
\fB\-\-all\fR
-to show those too\&. To select specific properties to show, use
-\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
+to show those too. To select specific properties to show, use
+\fB\-\-property=\fR. This command is intended to be used whenever computer\-parsable output is required. Use
\fBsession\-status\fR
-if you are looking for formatted human\-readable output\&.
+if you are looking for formatted human\-readable output.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
\fBactivate\fR [\fIID\fR]
.RS 4
-Activate a session\&. This brings a session into the foreground if another session is currently in the foreground on the respective seat\&. Takes a session identifier as argument\&. If no argument is specified, the session of the caller is put into foreground\&.
+Activate a session. This brings a session into the foreground if another session is currently in the foreground on the respective seat. Takes a session identifier as argument. If no argument is specified, the session of the caller is put into foreground.
.sp
-Added in version 219\&.
+Added in version 219.
.RE
.PP
-\fBlock\-session\fR [\fIID\fR\&...], \fBunlock\-session\fR [\fIID\fR\&...]
+\fBlock\-session\fR [\fIID\fR...], \fBunlock\-session\fR [\fIID\fR...]
.RS 4
-Activates/deactivates the screen lock on one or more sessions, if the session supports it\&. Takes one or more session identifiers as arguments\&. If no argument is specified, the session of the caller is locked/unlocked\&.
+Activates/deactivates the screen lock on one or more sessions, if the session supports it. Takes one or more session identifiers as arguments. If no argument is specified, the session of the caller is locked/unlocked.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
\fBlock\-sessions\fR, \fBunlock\-sessions\fR
.RS 4
-Activates/deactivates the screen lock on all current sessions supporting it\&.
+Activates/deactivates the screen lock on all current sessions supporting it.
.sp
-Added in version 188\&.
+Added in version 188.
.RE
.PP
-\fBterminate\-session\fR \fIID\fR\&...
+\fBterminate\-session\fR \fIID\fR...
.RS 4
-Terminates a session\&. This kills all processes of the session and deallocates all resources attached to the session\&. If the argument is specified as empty string the session invoking the command is terminated\&.
+Terminates a session. This kills all processes of the session and deallocates all resources attached to the session. If the argument is specified as empty string the session invoking the command is terminated.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
-\fBkill\-session\fR \fIID\fR\&...
+\fBkill\-session\fR \fIID\fR...
.RS 4
-Send a signal to one or more processes of the session\&. Use
+Send a signal to one or more processes of the session. Use
\fB\-\-kill\-whom=\fR
-to select which process to kill\&. Use
+to select which process to kill. Use
\fB\-\-signal=\fR
-to select the signal to send\&. If the argument is specified as empty string the signal is sent to the session invoking the command\&.
+to select the signal to send. If the argument is specified as empty string the signal is sent to the session invoking the command.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.SS "User Commands"
-.PP
\fBlist\-users\fR
.RS 4
-List currently logged in users\&.
+List currently logged in users.
.RE
.PP
-\fBuser\-status\fR [\fIUSER\fR\&...]
+\fBuser\-status\fR [\fIUSER\fR...]
.RS 4
-Show terse runtime status information about one or more logged in users, followed by the most recent log data from the journal\&. Takes one or more user names or numeric user IDs as parameters\&. If no parameters are passed, the status is shown for the user of the session of the caller\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
+Show terse runtime status information about one or more logged in users, followed by the most recent log data from the journal. Takes one or more user names or numeric user IDs as parameters. If no parameters are passed, the status is shown for the user of the session of the caller. This function is intended to generate human\-readable output. If you are looking for computer\-parsable output, use
\fBshow\-user\fR
-instead\&.
+instead.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
-\fBshow\-user\fR [\fIUSER\fR\&...]
+\fBshow\-user\fR [\fIUSER\fR...]
.RS 4
-Show properties of one or more users or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a user is specified, properties of the user are shown\&. By default, empty properties are suppressed\&. Use
+Show properties of one or more users or the manager itself. If no argument is specified, properties of the manager will be shown. If a user is specified, properties of the user are shown. By default, empty properties are suppressed. Use
\fB\-\-all\fR
-to show those too\&. To select specific properties to show, use
-\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
+to show those too. To select specific properties to show, use
+\fB\-\-property=\fR. This command is intended to be used whenever computer\-parsable output is required. Use
\fBuser\-status\fR
-if you are looking for formatted human\-readable output\&.
+if you are looking for formatted human\-readable output.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
-\fBenable\-linger\fR [\fIUSER\fR\&...], \fBdisable\-linger\fR [\fIUSER\fR\&...]
+\fBenable\-linger\fR [\fIUSER\fR...], \fBdisable\-linger\fR [\fIUSER\fR...]
.RS 4
-Enable/disable user lingering for one or more users\&. If enabled for a specific user, a user manager is spawned for the user at boot and kept around after logouts\&. This allows users who are not logged in to run long\-running services\&. Takes one or more user names or numeric UIDs as argument\&. If no argument is specified, enables/disables lingering for the user of the session of the caller\&.
+Enable/disable user lingering for one or more users. If enabled for a specific user, a user manager is spawned for the user at boot and kept around after logouts. This allows users who are not logged in to run long\-running services. Takes one or more user names or numeric UIDs as argument. If no argument is specified, enables/disables lingering for the user of the session of the caller.
.sp
See also
\fIKillUserProcesses=\fR
setting in
-\fBlogind.conf\fR(5)\&.
+\fBlogind.conf\fR(5).
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
-\fBterminate\-user\fR \fIUSER\fR\&...
+\fBterminate\-user\fR \fIUSER\fR...
.RS 4
-Terminates all sessions of a user\&. This kills all processes of all sessions of the user and deallocates all runtime resources attached to the user\&. If the argument is specified as empty string the sessions of the user invoking the command are terminated\&.
+Terminates all sessions of a user. This kills all processes of all sessions of the user and deallocates all runtime resources attached to the user. If the argument is specified as empty string the sessions of the user invoking the command are terminated.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
-\fBkill\-user\fR \fIUSER\fR\&...
+\fBkill\-user\fR \fIUSER\fR...
.RS 4
-Send a signal to all processes of a user\&. Use
+Send a signal to all processes of a user. Use
\fB\-\-signal=\fR
-to select the signal to send\&. If the argument is specified as empty string the signal is sent to the sessions of the user invoking the command\&.
+to select the signal to send. If the argument is specified as empty string the signal is sent to the sessions of the user invoking the command.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.SS "Seat Commands"
-.PP
\fBlist\-seats\fR
.RS 4
-List currently available seats on the local system\&.
+List currently available seats on the local system.
.RE
.PP
-\fBseat\-status\fR [\fINAME\fR\&...]
+\fBseat\-status\fR [\fINAME\fR...]
.RS 4
-Show terse runtime status information about one or more seats\&. Takes one or more seat names as parameters\&. If no seat names are passed the status of the caller\*(Aqs session\*(Aqs seat is shown\&. This function is intended to generate human\-readable output\&. If you are looking for computer\-parsable output, use
+Show terse runtime status information about one or more seats. Takes one or more seat names as parameters. If no seat names are passed the status of the caller\*(Aqs session\*(Aqs seat is shown. This function is intended to generate human\-readable output. If you are looking for computer\-parsable output, use
\fBshow\-seat\fR
-instead\&.
+instead.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
-\fBshow\-seat\fR [\fINAME\fR\&...]
+\fBshow\-seat\fR [\fINAME\fR...]
.RS 4
-Show properties of one or more seats or the manager itself\&. If no argument is specified, properties of the manager will be shown\&. If a seat is specified, properties of the seat are shown\&. By default, empty properties are suppressed\&. Use
+Show properties of one or more seats or the manager itself. If no argument is specified, properties of the manager will be shown. If a seat is specified, properties of the seat are shown. By default, empty properties are suppressed. Use
\fB\-\-all\fR
-to show those too\&. To select specific properties to show, use
-\fB\-\-property=\fR\&. This command is intended to be used whenever computer\-parsable output is required\&. Use
+to show those too. To select specific properties to show, use
+\fB\-\-property=\fR. This command is intended to be used whenever computer\-parsable output is required. Use
\fBseat\-status\fR
-if you are looking for formatted human\-readable output\&.
+if you are looking for formatted human\-readable output.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
-\fBattach\fR \fINAME\fR \fIDEVICE\fR\&...
+\fBattach\fR \fINAME\fR \fIDEVICE\fR...
.RS 4
-Persistently attach one or more devices to a seat\&. The devices should be specified via device paths in the
+Persistently attach one or more devices to a seat. The devices should be specified via device paths in the
/sys/
-file system\&. To create a new seat, attach at least one graphics card to a previously unused seat name\&. Seat names may consist only of a\(enz, A\(enZ, 0\(en9,
+file system. To create a new seat, attach at least one graphics card to a previously unused seat name. Seat names may consist only of a\(enz, A\(enZ, 0\(en9,
"\-"
and
"_"
and must be prefixed with
-"seat"\&. To drop assignment of a device to a specific seat, just reassign it to a different seat, or use
-\fBflush\-devices\fR\&.
+"seat". To drop assignment of a device to a specific seat, just reassign it to a different seat, or use
+\fBflush\-devices\fR.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.PP
\fBflush\-devices\fR
.RS 4
Removes all device assignments previously created with
-\fBattach\fR\&. After this call, only automatically generated seats will remain, and all seat hardware is assigned to them\&.
+\fBattach\fR. After this call, only automatically generated seats will remain, and all seat hardware is assigned to them.
.RE
.PP
-\fBterminate\-seat\fR \fINAME\fR\&...
+\fBterminate\-seat\fR \fINAME\fR...
.RS 4
-Terminates all sessions on a seat\&. This kills all processes of all sessions on the seat and deallocates all runtime resources attached to them\&.
+Terminates all sessions on a seat. This kills all processes of all sessions on the seat and deallocates all runtime resources attached to them.
.sp
-Added in version 233\&.
+Added in version 233.
.RE
.SH "OPTIONS"
-.PP
The following options are understood:
.PP
\fB\-\-no\-ask\-password\fR
.RS 4
-Do not query the user for authentication for privileged operations\&.
+Do not query the user for authentication for privileged operations.
.RE
.PP
\fB\-p\fR, \fB\-\-property=\fR
.RS 4
-When showing session/user/seat properties, limit display to certain properties as specified as argument\&. If not specified, all set properties are shown\&. The argument should be a property name, such as
-"Sessions"\&. If specified more than once, all properties with the specified names are shown\&.
+When showing session/user/seat properties, limit display to certain properties as specified as argument. If not specified, all set properties are shown. The argument should be a property name, such as
+"Sessions". If specified more than once, all properties with the specified names are shown.
.RE
.PP
\fB\-\-value\fR
.RS 4
When showing session/user/seat properties, only print the value, and skip the property name and
-"="\&.
+"=".
.sp
-Added in version 230\&.
+Added in version 230.
.RE
.PP
\fB\-a\fR, \fB\-\-all\fR
.RS 4
-When showing session/user/seat properties, show all properties regardless of whether they are set or not\&.
+When showing session/user/seat properties, show all properties regardless of whether they are set or not.
.RE
.PP
\fB\-l\fR, \fB\-\-full\fR
.RS 4
-Do not ellipsize process tree entries\&.
+Do not ellipsize process tree entries.
.sp
-Added in version 198\&.
+Added in version 198.
.RE
.PP
\fB\-\-kill\-whom=\fR
.RS 4
When used with
-\fBkill\-session\fR, choose which processes to kill\&. Takes one of
+\fBkill\-session\fR, choose which processes to kill. Takes one of
"leader"
or
-"all", to select whether to kill only the leader process of the session or all processes of the session\&. If omitted, defaults to
-\fBall\fR\&.
+"all", to select whether to kill only the leader process of the session or all processes of the session. If omitted, defaults to
+\fBall\fR.
.sp
-Added in version 252\&.
+Added in version 252.
.RE
.PP
\fB\-s\fR, \fB\-\-signal=\fR
@@ -268,18 +262,18 @@ Added in version 252\&.
When used with
\fBkill\-session\fR
or
-\fBkill\-user\fR, choose which signal to send to selected processes\&. Must be one of the well known signal specifiers, such as
+\fBkill\-user\fR, choose which signal to send to selected processes. Must be one of the well known signal specifiers, such as
\fBSIGTERM\fR,
\fBSIGINT\fR
or
-\fBSIGSTOP\fR\&. If omitted, defaults to
-\fBSIGTERM\fR\&.
+\fBSIGSTOP\fR. If omitted, defaults to
+\fBSIGTERM\fR.
.sp
The special value
"help"
will list the known values and the program will exit immediately, and the special value
"list"
-will list known values along with the numerical signal numbers and the program will exit immediately\&.
+will list known values along with the numerical signal numbers and the program will exit immediately.
.RE
.PP
\fB\-n\fR, \fB\-\-lines=\fR
@@ -287,9 +281,9 @@ will list known values along with the nu
When used with
\fBuser\-status\fR
and
-\fBsession\-status\fR, controls the number of journal lines to show, counting from the most recent ones\&. Takes a positive integer argument\&. Defaults to 10\&.
+\fBsession\-status\fR, controls the number of journal lines to show, counting from the most recent ones. Takes a positive integer argument. Defaults to 10.
.sp
-Added in version 219\&.
+Added in version 219.
.RE
.PP
\fB\-o\fR, \fB\-\-output=\fR
@@ -297,62 +291,60 @@ Added in version 219\&.
When used with
\fBuser\-status\fR
and
-\fBsession\-status\fR, controls the formatting of the journal entries that are shown\&. For the available choices, see
-\fBjournalctl\fR(1)\&. Defaults to
-"short"\&.
+\fBsession\-status\fR, controls the formatting of the journal entries that are shown. For the available choices, see
+\fBjournalctl\fR(1). Defaults to
+"short".
.sp
-Added in version 219\&.
+Added in version 219.
.RE
.PP
\fB\-H\fR, \fB\-\-host=\fR
.RS 4
-Execute the operation remotely\&. Specify a hostname, or a username and hostname separated by
-"@", to connect to\&. The hostname may optionally be suffixed by a port ssh is listening on, separated by
+Execute the operation remotely. Specify a hostname, or a username and hostname separated by
+"@", to connect to. The hostname may optionally be suffixed by a port ssh is listening on, separated by
":", and then a container name, separated by
-"/", which connects directly to a specific container on the specified host\&. This will use SSH to talk to the remote machine manager instance\&. Container names may be enumerated with
-\fBmachinectl \-H \fR\fB\fIHOST\fR\fR\&. Put IPv6 addresses in brackets\&.
+"/", which connects directly to a specific container on the specified host. This will use SSH to talk to the remote machine manager instance. Container names may be enumerated with
+\fBmachinectl \-H \fIHOST\fR. Put IPv6 addresses in brackets.
.RE
.PP
\fB\-M\fR, \fB\-\-machine=\fR
.RS 4
-Execute operation on a local container\&. Specify a container name to connect to, optionally prefixed by a user name to connect as and a separating
+Execute operation on a local container. Specify a container name to connect to, optionally prefixed by a user name to connect as and a separating
"@"
-character\&. If the special string
-"\&.host"
+character. If the special string
+".host"
is used in place of the container name, a connection to the local system is made (which is useful to connect to a specific user\*(Aqs user bus:
-"\-\-user \-\-machine=lennart@\&.host")\&. If the
+"\-\-user \-\-machine=lennart at .host"). If the
"@"
-syntax is not used, the connection is made as root user\&. If the
+syntax is not used, the connection is made as root user. If the
"@"
syntax is used either the left hand side or the right hand side may be omitted (but not both) in which case the local user name and
-"\&.host"
-are implied\&.
+".host"
+are implied.
.RE
.PP
\fB\-\-no\-pager\fR
.RS 4
-Do not pipe output into a pager\&.
+Do not pipe output into a pager.
.RE
.PP
\fB\-\-no\-legend\fR
.RS 4
-Do not print the legend, i\&.e\&. column headers and the footer with hints\&.
+Do not print the legend, i.e.\& column headers and the footer with hints.
.RE
.PP
\fB\-h\fR, \fB\-\-help\fR
.RS 4
-Print a short help text and exit\&.
+Print a short help text and exit.
.RE
.PP
\fB\-\-version\fR
.RS 4
-Print a short version string and exit\&.
+Print a short version string and exit.
.RE
.SH "EXIT STATUS"
-.PP
-On success, 0 is returned, a non\-zero failure code otherwise\&.
+On success, 0 is returned, a non\-zero failure code otherwise.
.SH "EXAMPLES"
-.PP
\fBExample\ \&1.\ \&Querying user status\fR
.sp
.if n \{\
@@ -364,12 +356,12 @@ fatima (1005)
Since: Sat 2016\-04\-09 14:23:31 EDT; 54min ago
State: active
Sessions: 5 *3
- Unit: user\-1005\&.slice
- ??????user at 1005\&.service
- \&...
- ??????session\-3\&.scope
- \&...
- ??????session\-5\&.scope
+ Unit: user\-1005.slice
+ ??????user at 1005.service
+ ...
+ ??????session\-3.scope
+ ...
+ ??????session\-5.scope
??????3473 login \-\- fatima
??????3515 \-zsh
@@ -381,12 +373,12 @@ Apr 09 14:40:30 laptop login[2325]: LOGI
.RE
.\}
.PP
-There are two sessions, 3 and 5\&. Session 3 is a graphical session, marked with a star\&. The tree of processing including the two corresponding scope units and the user manager unit are shown\&.
+There are two sessions, 3 and 5. Session 3 is a graphical session, marked with a star. The tree of processing including the two corresponding scope units and the user manager unit are shown.
.SH "ENVIRONMENT"
.PP
\fI$SYSTEMD_LOG_LEVEL\fR
.RS 4
-The maximum log level of emitted messages (messages with a higher log level, i\&.e\&. less important ones, will be suppressed)\&. Either one of (in order of decreasing importance)
+The maximum log level of emitted messages (messages with a higher log level, i.e. less important ones, will be suppressed). Either one of (in order of decreasing importance)
\fBemerg\fR,
\fBalert\fR,
\fBcrit\fR,
@@ -394,46 +386,47 @@ The maximum log level of emitted message
\fBwarning\fR,
\fBnotice\fR,
\fBinfo\fR,
-\fBdebug\fR, or an integer in the range 0\&...7\&. See
+\fBdebug\fR, or an integer in the range 0...7.
+See
\fBsyslog\fR(3)
-for more information\&.
+for more information.
.RE
.PP
\fI$SYSTEMD_LOG_COLOR\fR
.RS 4
-A boolean\&. If true, messages written to the tty will be colored according to priority\&.
+A boolean. If true, messages written to the tty will be colored according to priority.
.sp
This setting is only useful when messages are written directly to the terminal, because
\fBjournalctl\fR(1)
-and other tools that display logs will color messages based on the log level on their own\&.
+and other tools that display logs will color messages based on the log level on their own.
.RE
.PP
\fI$SYSTEMD_LOG_TIME\fR
.RS 4
-A boolean\&. If true, console log messages will be prefixed with a timestamp\&.
+A boolean. If true, console log messages will be prefixed with a timestamp.
.sp
This setting is only useful when messages are written directly to the terminal or a file, because
\fBjournalctl\fR(1)
-and other tools that display logs will attach timestamps based on the entry metadata on their own\&.
+and other tools that display logs will attach timestamps based on the entry metadata on their own.
.RE
.PP
\fI$SYSTEMD_LOG_LOCATION\fR
.RS 4
-A boolean\&. If true, messages will be prefixed with a filename and line number in the source code where the message originates\&.
+A boolean. If true, messages will be prefixed with a filename and line number in the source code where the message originates.
.sp
-Note that the log location is often attached as metadata to journal entries anyway\&. Including it directly in the message text can nevertheless be convenient when debugging programs\&.
+Note that the log location is often attached as metadata to journal entries anyway. Including it directly in the message text can nevertheless be convenient when debugging programs.
.RE
.PP
\fI$SYSTEMD_LOG_TID\fR
.RS 4
-A boolean\&. If true, messages will be prefixed with the current numerical thread ID (TID)\&.
+A boolean. If true, messages will be prefixed with the current numerical thread ID (TID).
.sp
-Note that the this information is attached as metadata to journal entries anyway\&. Including it directly in the message text can nevertheless be convenient when debugging programs\&.
+Note that the this information is attached as metadata to journal entries anyway. Including it directly in the message text can nevertheless be convenient when debugging programs.
.RE
.PP
\fI$SYSTEMD_LOG_TARGET\fR
.RS 4
-The destination for log messages\&. One of
+The destination for log messages. One of
\fBconsole\fR
(log to the attached tty),
\fBconsole\-prefixed\fR
@@ -448,13 +441,13 @@ The destination for log messages\&. One
\fBauto\fR
(determine the appropriate log target automatically, the default),
\fBnull\fR
-(disable log output)\&.
+(disable log output).
.RE
.PP
\fI$SYSTEMD_LOG_RATELIMIT_KMSG\fR
.RS 4
-Whether to ratelimit kmsg or not\&. Takes a boolean\&. Defaults to
-"true"\&. If disabled, systemd will not ratelimit messages written to kmsg\&.
+Whether to ratelimit kmsg or not. Takes a boolean. Defaults to
+"true". If disabled, systemd will not ratelimit messages written to kmsg.
.RE
.PP
\fI$SYSTEMD_PAGER\fR
@@ -462,24 +455,24 @@ Whether to ratelimit kmsg or not\&. Take
Pager to use when
\fB\-\-no\-pager\fR
is not given; overrides
-\fI$PAGER\fR\&. If neither
+\fI$PAGER\fR. If neither
\fI$SYSTEMD_PAGER\fR
nor
\fI$PAGER\fR
are set, a set of well\-known pager implementations are tried in turn, including
\fBless\fR(1)
and
-\fBmore\fR(1), until one is found\&. If no pager implementation is discovered no pager is invoked\&. Setting this environment variable to an empty string or the value
+\fBmore\fR(1), until one is found. If no pager implementation is discovered no pager is invoked. Setting this environment variable to an empty string or the value
"cat"
is equivalent to passing
-\fB\-\-no\-pager\fR\&.
+\fB\-\-no\-pager\fR.
.sp
Note: if
\fI$SYSTEMD_PAGERSECURE\fR
is not set,
\fI$SYSTEMD_PAGER\fR
(as well as
-\fI$PAGER\fR) will be silently ignored\&.
+\fI$PAGER\fR) will be silently ignored.
.RE
.PP
\fI$SYSTEMD_LESS\fR
@@ -487,7 +480,7 @@ is not set,
Override the options passed to
\fBless\fR
(by default
-"FRSXMK")\&.
+"FRSXMK").
.sp
Users might want to change two options in particular:
.PP
@@ -495,11 +488,11 @@ Users might want to change two options i
.RS 4
This option instructs the pager to exit immediately when
Ctrl+C
-is pressed\&. To allow
+is pressed. To allow
\fBless\fR
to handle
Ctrl+C
-itself to switch back to the pager command prompt, unset this option\&.
+itself to switch back to the pager command prompt, unset this option.
.sp
If the value of
\fI$SYSTEMD_LESS\fR
@@ -507,23 +500,23 @@ does not include
"K", and the pager that is invoked is
\fBless\fR,
Ctrl+C
-will be ignored by the executable, and needs to be handled by the pager\&.
+will be ignored by the executable, and needs to be handled by the pager.
.RE
.PP
\fBX\fR
.RS 4
-This option instructs the pager to not send termcap initialization and deinitialization strings to the terminal\&. It is set by default to allow command output to remain visible in the terminal even after the pager exits\&. Nevertheless, this prevents some pager functionality from working, in particular paged output cannot be scrolled with the mouse\&.
+This option instructs the pager to not send termcap initialization and deinitialization strings to the terminal. It is set by default to allow command output to remain visible in the terminal even after the pager exits. Nevertheless, this prevents some pager functionality from working, in particular paged output cannot be scrolled with the mouse.
.RE
.sp
Note that setting the regular
\fI$LESS\fR
environment variable has no effect for
\fBless\fR
-invocations by systemd tools\&.
+invocations by systemd tools.
.sp
See
\fBless\fR(1)
-for more discussion\&.
+for more discussion.
.RE
.PP
\fI$SYSTEMD_LESSCHARSET\fR
@@ -531,68 +524,70 @@ for more discussion\&.
Override the charset passed to
\fBless\fR
(by default
-"utf\-8", if the invoking terminal is determined to be UTF\-8 compatible)\&.
+"utf\-8", if the invoking terminal is determined to be UTF\-8 compatible).
.sp
Note that setting the regular
\fI$LESSCHARSET\fR
environment variable has no effect for
\fBless\fR
-invocations by systemd tools\&.
+invocations by systemd tools.
.RE
.PP
\fI$SYSTEMD_PAGERSECURE\fR
.RS 4
-Takes a boolean argument\&. When true, the "secure" mode of the pager is enabled; if false, disabled\&. If
+Takes a boolean argument. When true, the "secure" mode of the pager is enabled; if false, disabled. If
\fI$SYSTEMD_PAGERSECURE\fR
is not set at all, secure mode is enabled if the effective UID is not the same as the owner of the login session, see
\fBgeteuid\fR(2)
and
-\fBsd_pid_get_owner_uid\fR(3)\&. In secure mode,
+\fBsd_pid_get_owner_uid\fR(3). In secure mode,
\fBLESSSECURE=1\fR
-will be set when invoking the pager, and the pager shall disable commands that open or create new files or start new subprocesses\&. When
+will be set when invoking the pager, and the pager shall disable commands that open or create new files or start new subprocesses. When
\fI$SYSTEMD_PAGERSECURE\fR
-is not set at all, pagers which are not known to implement secure mode will not be used\&. (Currently only
+is not set at all, pagers which are not known to implement secure mode will not be used. (Currently only
\fBless\fR(1)
-implements secure mode\&.)
+implements secure mode.)
.sp
Note: when commands are invoked with elevated privileges, for example under
\fBsudo\fR(8)
or
-\fBpkexec\fR(1), care must be taken to ensure that unintended interactive features are not enabled\&. "Secure" mode for the pager may be enabled automatically as describe above\&. Setting
+\fBpkexec\fR(1), care must be taken to ensure that unintended interactive
+features are not enabled.
+"Secure" mode for the pager may be enabled automatically as describe above.
+Setting
\fISYSTEMD_PAGERSECURE=0\fR
-or not removing it from the inherited environment allows the user to invoke arbitrary commands\&. Note that if the
+or not removing it from the inherited environment allows the user to invoke arbitrary commands. Note that if the
\fI$SYSTEMD_PAGER\fR
or
\fI$PAGER\fR
variables are to be honoured,
\fI$SYSTEMD_PAGERSECURE\fR
-must be set too\&. It might be reasonable to completely disable the pager using
+must be set too. It might be reasonable to completely disable the pager using
\fB\-\-no\-pager\fR
-instead\&.
+instead.
.RE
.PP
\fI$SYSTEMD_COLORS\fR
.RS 4
-Takes a boolean argument\&. When true,
+Takes a boolean argument. When true,
\fBsystemd\fR
-and related utilities will use colors in their output, otherwise the output will be monochrome\&. Additionally, the variable can take one of the following special values:
+and related utilities will use colors in their output, otherwise the output will be monochrome. Additionally, the variable can take one of the following special values:
"16",
"256"
-to restrict the use of colors to the base 16 or 256 ANSI colors, respectively\&. This can be specified to override the automatic decision based on
+to restrict the use of colors to the base 16 or 256 ANSI colors, respectively. This can be specified to override the automatic decision based on
\fI$TERM\fR
-and what the console is connected to\&.
+and what the console is connected to.
.RE
.PP
\fI$SYSTEMD_URLIFY\fR
.RS 4
-The value must be a boolean\&. Controls whether clickable links should be generated in the output for terminal emulators supporting this\&. This can be specified to override the decision that
+The value must be a boolean. Controls whether clickable links should be generated in the output for terminal emulators supporting this. This can be specified to override the decision that
\fBsystemd\fR
makes based on
\fI$TERM\fR
-and other conditions\&.
+and other conditions.
.RE
.SH "SEE ALSO"
-.PP
\fBsystemd\fR(1),
\fBsystemctl\fR(1),
\fBsystemd-logind.service\fR(8),
More information about the Pkg-systemd-maintainers
mailing list