commit - 33975b0ff466e0f7b1e4924adab2b4c163f55570
commit + 7030bc240475571d6fa870360fb85664bf2e475d
blob - 1db7ff5515aafdc648dd4aca4d0ed552b48222a5
blob + 75865eed56702dd15dbb0c4b170bc63f2b07b558
--- art/015.cron_tricks.txt
+++ art/015.cron_tricks.txt
@@ -98,6 +98,32 @@ can get, but let's also check for any sessions existin
 0 12 * * * tmux ls >/dev/null 2>&1 && tmux popup echo "it's 12 o'clock"
 
 
+	X11 authorised display
+
+You can use the following script (e.g. ~/bin/xauthorised) to find
+authorised X displays via Unix sockets. The vast majority of modern
+X windows setups will use Unix sockets.
+
+#!/bin/sh
+
+ret=1
+
+for f in /tmp/.X11-unix/*; do
+	test -S $f || continue
+	d=:`basename $f | tr -d X`
+	DISPLAY=$d xprop -root >/dev/null 2>&1 && {
+		ret=0
+		echo $d
+	}
+done
+
+exit $ret
+
+You can then use it from cron like so:
+
+0 12 * * * DISPLAY=`$HOME/bin/xauthorised | head -1` /usr/X11R6/bin/xmessage "it's 12 o'clock"
+
+
 OPENBSD SPECIFIC
 
 There are many implementations of cron. Most have extensions. Here are
@@ -121,18 +147,13 @@ some OpenBSD specific:
   far as I know it's found in most modern implementations.
 
 
-	X11 programs
+	X11 logged on display
 
-You might know that this works:
+In "X11 authorised display" I gave an example of finding any X display,
+where cron can run an X11 program. OpenBSD allows you to be more
+specific, and get the display each user is logged on to via who(1).
+Here's how to use it:
 
-0 12 * * * DISPLAY=:0 /usr/X11R6/bin/xmessage "it's 12 o'clock!"
-
-(Though even that may require messing with XAUTHORITY, to which I can't
-give you any good advice.)
-
-Finding a more general approach to setting DISPLAY is ironically very
-system-specific. On OpenBSD you can use who(1):
-
 0 12 * * * DISPLAY=`who | awk -vu=$USER '$1 == u && $NF ~ /^[(]:[0-9]+[)]$/ {print substr($NF, 2, length($NF)-2); exit}'` /usr/X11R6/bin/xmessage "it's 12 o'clock"
 
 (I put parantheses into brackets here to avoid doubly-escaping