Setup monitoring for reprostim-timesync-stimuli not being ran

[yarikoptic]

Terry reminded me today that our reprostim-timesync-stimuli did not start displaying for him today.

Since we (I) never figured out full automation of either starting X for the script, or initiating X properly without a monitor attached (now IIRC we need to start X when monitor attached so we get proper resolution), and it seems we do not react to external connector being connected since we rely on xrandr output, which if not set up correctly (per above) -- would not see monitor being connected and not report back that something is good or wrong.

May be at least for monitoring and reporting if we missed recording we could rely on seeing such messages in systemctl?

reprostim@reproiner:~$ journalctl -q --grep 'EDID vendor'
Sep 29 09:05:00 reproiner /usr/libexec/gdm-x-session[1231]: (II) modeset(0): EDID vendor "AGO", prod id 1
Oct 13 09:16:45 reproiner /usr/libexec/gdm-x-session[1205]: (II) modeset(0): EDID vendor "MEI", prod id 53502
Oct 13 09:16:45 reproiner /usr/libexec/gdm-x-session[1205]: (II) modeset(0): EDID vendor "MEI", prod id 53502
Oct 13 09:16:46 reproiner /usr/libexec/gdm-x-session[1205]: (II) modeset(0): EDID vendor "MEI", prod id 53502
Oct 13 09:17:00 reproiner /usr/libexec/gdm-x-session[1205]: (II) modeset(0): EDID vendor "MEI", prod id 53502

which I think report a monitor being connected. (I guess here Terry tried multiple times today)

Also we would need

• setup sending email from that box (msmtp?)