From e45c6b76dad062e1e2c492524f2c05e27913b382 Mon Sep 17 00:00:00 2001 From: Jacob Nevins Date: Thu, 19 May 2022 10:52:56 +0100 Subject: [PATCH] Restore advice about making pterm set[ug]id. cmake doesn't have convincing facilities for doing this in its install step, so the new advice is to do it manually (we've provided no equivalent to the autotools --enable-setuid or --enable-setgid options, nor UTMP_USER/GROUP). --- README | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/README b/README index 85b645d1..c996c3a8 100644 --- a/README +++ b/README @@ -12,6 +12,16 @@ Then, to install in the simplest way on Linux or Mac: cmake --build . --target install +On Unix, pterm would like to be setuid or setgid, as appropriate, to +permit it to write records of user logins to /var/run/utmp and +/var/log/wtmp. (Of course it will not use this privilege for +anything else, and in particular it will drop all privileges before +starting up complex subsystems like GTK.) The cmake install step +doesn't attempt to add these privileges, so if you want user login +recording to work, you should manually ch{own,grp} and chmod the +pterm binary yourself after installation. If you don't do this, +pterm will still work, but not update the user login databases. + Documentation (in various formats including Windows Help and Unix `man' pages) is built from the Halibut (`.but') files in the `doc' subdirectory using `doc/Makefile'. If you aren't using one of our