diff options
Diffstat (limited to 'man/org.freedesktop.login1.xml')
-rw-r--r-- | man/org.freedesktop.login1.xml | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/man/org.freedesktop.login1.xml b/man/org.freedesktop.login1.xml index 0d686d65a1..e5521e155a 100644 --- a/man/org.freedesktop.login1.xml +++ b/man/org.freedesktop.login1.xml @@ -499,19 +499,20 @@ node /org/freedesktop/login1 { directory of a user is kept around and he may continue to run processes while he is logged out. If disabled, the runtime directory goes away as soon as they log out. <function>SetUserLinger()</function> expects three arguments: the UID, a boolean whether to enable/disable and a boolean controlling the - PolicyKit authorization interactivity (see below). Note that the user linger state is persistently + <ulink url="https://www.freedesktop.org/software/polkit/docs/latest/">polkit</ulink> + authorization interactivity (see below). Note that the user linger state is persistently stored on disk.</para> <para><function>AttachDevice()</function> may be used to assign a specific device to a specific seat. The device is identified by its /sys path and must be eligible for seat assignments. <function>AttachDevice()</function> takes three - arguments: the seat id, the sysfs path, and a boolean for controlling PolicyKit interactivity (see + arguments: the seat id, the sysfs path, and a boolean for controlling polkit interactivity (see below). Device assignments are persistently stored on disk. To create a new seat, simply specify a previously unused seat id. For more information about the seat assignment logic see <ulink url="https://www.freedesktop.org/wiki/Software/systemd/multiseat">Multi-Seat for Linux</ulink>. </para> <para><function>FlushDevices()</function> removes all explicit seat assignments for devices, resetting - all assignments to the automatic defaults. The only argument it takes is the PolicyKit interactivity + all assignments to the automatic defaults. The only argument it takes is the polkit interactivity boolean (see below).</para> <para><function>PowerOff()</function>, <function>Reboot()</function>, <function>Halt()</function>, @@ -521,9 +522,9 @@ node /org/freedesktop/login1 { the machine is powered down). <function>HybridSleep()</function> results in the system entering a hybrid-sleep mode, i.e. the system is both hibernated and suspended. <function>SuspendThenHibernate()</function> results in the system being suspended, then later woken - using an RTC timer and hibernated. The only argument is the PolicyKit interactivity boolean + using an RTC timer and hibernated. The only argument is the polkit interactivity boolean <varname>interactive</varname> (see below). The main purpose of these calls is that they enforce - PolicyKit policy and hence allow powering off/rebooting/suspending/hibernating even by unprivileged + polkit policy and hence allow powering off/rebooting/suspending/hibernating even by unprivileged users. They also enforce inhibition locks. UIs should expose these calls as the primary mechanism to poweroff/reboot/suspend/hibernate the machine.</para> @@ -678,7 +679,7 @@ node /org/freedesktop/login1 { <refsect2> <title>Security</title> - <para>A number of operations are protected via the PolicyKit privilege + <para>A number of operations are protected via the polkit privilege system. <function>SetUserLinger()</function> requires the <interfacename>org.freedesktop.login1.set-user-linger</interfacename> privilege. <function>AttachDevice()</function> requires @@ -731,7 +732,7 @@ node /org/freedesktop/login1 { <interfacename>org.freedesktop.login1.inhibit-handle-lid-switch</interfacename> depending on the lock type and mode taken.</para> - <para>The <varname>interactive</varname> boolean parameters can be used to control whether PolicyKit + <para>The <varname>interactive</varname> boolean parameters can be used to control whether polkit should interactively ask the user for authentication credentials if required.</para> </refsect2> </refsect1> |