http://ftp.x.org/contrib/applications/xscreensaver-3.09.tar.gz

[xscreensaver] / config.h.in

diff --git a/config.h.in b/config.h.in
index 367aa85a97d7ff39f9d3fa632a3d8ec037ef2084..5707bd8c0ac99bb22f4763852a94dbc0b9bbae27 100644 (file)
--- a/config.h.in
+++ b/config.h.in
@@ -96,6 +96,12 @@
  */
 #undef HAVE_DPMS_EXTENSION
 
+/*  Define this if you have a Linux-like /proc/interrupts file which can be
+ *  examined to determine when keyboard activity has occurred.
+ */
+#undef HAVE_PROC_INTERRUPTS
+
+
 
 /* *************************************************************************
                           CONFIGURING GRAPHICS TOOLKITS
@@ -145,6 +151,10 @@
  */
 #undef HAVE_XSHM_EXTENSION
 
+/*  Define this if you have the X Double Buffer Extension.
+ */
+#undef HAVE_DOUBLE_BUFFER_EXTENSION
+
 /*  Some screenhacks like to run an external program to generate random pieces
     of text; set this to the one you like ("yow" and "fortune" are the most
     likely prospects.)  Note that this is just the default; X resources can
@@ -179,11 +189,13 @@
 #undef HAVE_PAM
 
 /*  If PAM is being used, this is the name of the PAM service that xscreensaver
- *  will authenticate as.  It would be sensible to set this to "xscreensaver".
- *  However, since some systems already have a PAM service named "xlock" 
- *  defined, we might as well use that.
+ *  will authenticate as.  The default is "xscreensaver", which means that the
+ *  PAM library will look for an "xscreensaver" line in /etc/pam.conf, or (on
+ *  recent Linux systems) will look for a file called /etc/pam.d/xscreensaver.
+ *  Some systems might already have a PAM installation that is configured for
+ *  xlock, so setting this to "xlock" would also work in that case.
  */
-#define PAM_SERVICE_NAME "xlock"
+#define PAM_SERVICE_NAME "xscreensaver"
 
 /*  Define this if your system uses `shadow' passwords, that is, the passwords
  *  live in /etc/shadow instead of /etc/passwd, and one reads them with