shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-28 02:50:16 +03:00
Code

man: update links to "Inhibitor Locks"

Browse Source
This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2024-05-28 13:04:09 +02:00
parent b346d72c79
commit 5507480cf4
4 changed files with 8 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
man/org.freedesktop.login1.xml
View File

@ -715,7 +715,7 @@ node /org/freedesktop/login1 {
whether the inhibit shall be consider mandatory or whether it should just delay the operation to a
certain maximum time. The method returns a file descriptor. The lock is released the moment this file
descriptor and all its duplicates are closed. For more information on the inhibition logic see
<ulink url="https://www.freedesktop.org/wiki/Software/systemd/inhibit">Inhibitor Locks</ulink>.
<ulink url="https://systemd.io/INHIBITOR_LOCKS">Inhibitor Locks</ulink>.
</para>
</refsect2>
@ -739,7 +739,7 @@ node /org/freedesktop/login1 {
that should be done shortly before shutdown/sleep, in conjunction with delay inhibitor locks. After
completion of this work they should release their inhibition locks in order to not delay the operation
any further. For more information see
<ulink url="https://www.freedesktop.org/wiki/Software/systemd/inhibit">Inhibitor Locks</ulink>. The
<ulink url="https://systemd.io/INHIBITOR_LOCKS">Inhibitor Locks</ulink>. The
<function>PrepareForShutdownWithMetadata()</function> signal additionally sends a list of key/value
pair metadata fields. Currently it sends a <varname>type</varname> string which defines the type of
shutdown. The type can be one of <literal>power-off</literal>, <literal>reboot</literal>,

5
man/systemd-inhibit.xml
View File

@ -44,9 +44,8 @@
an optical disc is being recorded, or similar operations that
should not be interrupted.</para>
<para>For more information see the <ulink
url="https://www.freedesktop.org/wiki/Software/systemd/inhibit">Inhibitor
Lock Developer Documentation</ulink>.</para>
<para>For more information see
<ulink url="https://systemd.io/INHIBITOR_LOCKS">Inhibitor Locks</ulink>.</para>
</refsect1>
<refsect1>

5
man/systemd-logind.service.xml
View File

@ -84,9 +84,8 @@
<citerefentry><refentrytitle>org.freedesktop.LogControl1</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for information about the D-Bus APIs <filename>systemd-logind</filename> provides.</para>
<para>For more information on the inhibition logic see the <ulink
url="https://www.freedesktop.org/wiki/Software/systemd/inhibit">Inhibitor
Lock Developer Documentation</ulink>.</para>
<para>For more information see
<ulink url="https://systemd.io/INHIBITOR_LOCKS">Inhibitor Locks</ulink>.</para>
<para>If you are interested in writing a display manager that makes use of logind, please have look at
<ulink url="https://www.freedesktop.org/wiki/Software/systemd/writing-display-managers">Writing Display

6
man/systemd-suspend.service.xml
View File

@ -73,10 +73,8 @@
<para>Note that scripts or binaries dropped in
<filename>/usr/lib/systemd/system-sleep/</filename> are intended
for local use only and should be considered hacks. If applications
want to react to system suspend/hibernation and resume,
they should rather use the <ulink
url="https://www.freedesktop.org/wiki/Software/systemd/inhibit">Inhibitor
interface</ulink>.</para>
want to react to system suspend/hibernation and resume, they should rather use the
<ulink url="https://systemd.io/INHIBITOR_LOCKS">Inhibitor Locks</ulink>.</para>
<para>Note that <filename>systemd-suspend.service</filename>,
<filename>systemd-hibernate.service</filename>, <filename>systemd-hybrid-sleep.service</filename>, and