Update README

[elogind.git] / README

diff --git a/README b/README
index e08b1ddd0a74a313e9f7ba6dfd1e20b85d09c745..06f1fc80cdc749902e629f71f72ea8a73f397800 100644 (file)
--- a/README
+++ b/README
@@ -29,7 +29,7 @@ provide a subset of the interfaces of systemd 219.
 
 To contribute to elogind, fork the current source code from github:
 
-  https://github.com/elogind/elogind
+  https://github.com/andywingo/elogind
 
 Send a pull request for the changes you like.
 
@@ -39,7 +39,7 @@ To chat about elogind:
 
 Finally, bug reports:
 
-  https://github.com/elogind/elogind/issues
+  https://github.com/andywingo/elogind/issues
 
 Why bother?
 -----------
@@ -77,32 +77,27 @@ of <systemd/sd-login.h>.
 Libelogind just implements login-related functionality.  It also
 provides the sd-bus API.
 
-Unlike systemd, whose logind arranges to manage resources for user
-sessions via RPC calls to systemd, in elogind there is no systemd so
-there is no global cgroup-based resource management.  This has a few
-implications:
+Unlike systemd, whose logind arranges to run user sessions in cgroups
+via RPC calls to systemd, in elogind there is no systemd so there are
+no cgroups.  This has a few implications:
 
   * Elogind does not create "slices" for users.  Elogind will not
     record that users are associated with slices.
 
-  * The /run/systemd/slices directory will always be empty.
+  * Systemd's logind waits for all user jobs to stop before recording
+    that a user's session has gone away.  Since we have no cgroups,
+    elogind just removes the session directly when pam_elogind.so
+    indicates the user has logged out.
 
-  * Elogind does not have the concept of a "scope", internally, as
-    it's the same as a session.  Any API that refers to scopes will
-    always return an error code.
+  * The /run/systemd/slices directory will always be empty.
 
-On the other hand, elogind does use a similar strategy to systemd in
-that it places processes in a private cgroup for organizational
-purposes, without installing any controllers (see
-http://0pointer.de/blog/projects/cgroups-vs-cgroups.html).  This
-allows elogind to map arbitrary processes to sessions, even if the
-process does the usual double-fork to be reparented to PID 1.
+  * Support for lingering is not so great.
 
 Elogind does not manage virtual terminals.
 
 Elogind does monitor power button and the lid switch, like systemd,
 but instead of doing RPC to systemd to suspend, poweroff, or restart
-the machine, elogind just does this directly.  For suspend, hybernate,
+the machine, elogind just does this directly.  For suspend, hibernate,
 and hybrid-sleep, elogind uses the same code as systemd-sleep.
 Instead of using a separate sleep.conf file to configure the sleep
 behavior, this is included in the [Sleep] section of