From Gentoo Wiki
Jump to:navigation Jump to:search

elogind is the systemd project's logind, extracted to a standalone package. It's designed for users who prefer a non-systemd init system, but still want to use popular software such as KDE/Wayland or GNOME that otherwise hard-depends on systemd.



The following kernel options are recommended:

General setup  --->
    [*] Control Group support  --->
File systems  --->
    [*] Inotify support for userspace

In the unlikely (and not recommended) event that standard kernel features are enabled for manual configuration, elogind also requires eventpoll, signalfd() and timerfd() support. Most users can ignore this.

USE flags

USE flags for sys-auth/elogind The systemd project's logind, extracted to a standalone package

acl Add support for Access Control Lists
audit Enable support for Linux audit subsystem using sys-process/audit
debug Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
doc Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
pam Add support for PAM (Pluggable Authentication Modules)DANGEROUS to arbitrarily flip
policykit Enable PolicyKit (polkit) authentication support
selinux !!internal use only!! Security Enhanced Linux support, this must be set by the selinux profile or breakage will occur

There is a global elogind USE flag for enabling elogind support in other packages. It's also recommended to disable support for other session trackers to avoid conflicts:

FILE /etc/portage/make.conf
USE="elogind -systemd"
Running more than one session tracker at the same time may lead to unforeseen problems with some applications.


After updating the USE flags update the system so the changes take effect:

root #emerge --ask --changed-use --deep @world



elogind may be optionally configured to start at boot time:

root #rc-update add elogind boot

Alternatively, elogind will be launched automatically when the first service calls it via dbus, or if built with USE="pam", when the first user logs into the system. However if there are problems getting poweroff/reboot/suspend etc. working from desktop environment, putting elogind into boot runlevel will make sure it is started properly before any user is logged in and so should fix the problem.

startx integration

To have an elogind session created when using startx to start the X server (instead of a display manager), add the following to the user's ~/.xinitrc file:

FILE ~/.xinitrc
exec dbus-launch --exit-with-session <WINDOW_MANAGER>

WINDOW_MANAGER in the above example needs to be replaced by a window manager or a single application.

Hook scripts to be run when suspending/hibernating and/or when resuming/thawing

With elogind the situation is much handier. Any suspend/resume and hibernate/thaw hook scripts need to be in the directory /lib64/elogind/system-sleep/ and use the variables $1 (pre or post) and $2 (suspend, hibernate, or hybrid-sleep). For example, in the case of elogind a hook script could have the following format:

case $1/$2 in
    # Put here any commands expected to be run when suspending or hibernating.
    # Put here any commands expected to be run when resuming from suspension or thawing from hibernation.
Do not forget to make the hook scripts executable.



The command loginctl may be used to control and introspect the login manager. For example, to shut down or reboot the system:

user $loginctl poweroff
user $loginctl reboot

For example, to suspend, hibernate or hybrid-suspend the system:

user $loginctl suspend
user $loginctl hibernate
user $loginctl hybrid-sleep


Conflict when using hidepid in proc

When procfs is mounted with hidepid=2 and gid=wheel, there will be conflicts with elogind. In order to change this, the gid needs to be changed to gid=polkitd.

See also this forum post https://forums.gentoo.org/viewtopic-t-1099870.html

External resources