1
Session manager for the XFce desktop environment.
5
In order to use xfce4-shutdown with xfce4-session to reboot/halt the computer,
8
a) make $sbindir/xfce4-shutdown setuid to root and add the users
9
that you want to allow to reboot/halt to the file
10
$sysconfdir/xfce4/shutdown.allow
12
b) install sudo(8) and allow the users to execute /sbin/poweroff,
13
/sbin/halt and/or /sbin/reboot.
15
How to start the session manager:
16
---------------------------------
17
See the sample xinitrc file in $sysconfdir/xfce4/xinitrc.xfce4-session.
1
Session manager for the Xfce desktop environment.
3
Shutting down your computer using the session manager:
4
------------------------------------------------------
5
Since 4.1.5, the session manager supports only sudo(8)-based shutdown, other
6
method can be added by packagers if desired, just replace XfsmShutdownHelper
7
with your code. To be able to shutdown the computer, you must be listed
8
in the systems sudoers file, in particular, you must be allowed to execute
9
$libexecdir/xfsm-shutdown-helper as user root (where $libexecdir is the
10
libexec subdir in the prefix you installed xfce4-session, for example
13
For example, you installed xfce4-session into /usr/local, your hostname
14
is myhost and your user account is named myuser, then you'd have to add
15
the following line to your sudoers file (remember to use visudo to edit
18
myuser myhost=/usr/local/libexec/xfsm-shutdown-helper
22
Legacy session management:
23
--------------------------
24
As of version 4.1.7, the session manager includes native support for
25
applications that don't support the X11R6 session management protocol,
26
but support legacy (X11R5) session management. If you don't need legacy
27
session management support, you can disable it at compile time, giving
28
--disable-legacy-sm to ./configure.
30
The legacy sm code is ment as a replacement for smproxy (the X11 session
31
management proxy), which caused all kinds of trouble. That says, do NOT
32
EVER run smproxy in session that is managed by xfce4-session, or weird
33
things will happen. The included legacy session management does everything
34
that smproxy would do, and besides that, it also support multiscreen
35
display and it is less error prone compared to smproxy (atleast once
36
the various bugs I introduced are fixed :-).