Added geoclue as a unit file and set it to autostart by default.
Redshift on archlinux has problems working correctly if there is no
(gnome?) desktop environment and the geoclue agent has thus not been
started yet. This simply runs it on startup as a user service and
redshift subsequently picks it up to get its location from.
I have stopped using keybase a while ago, (due to switching over to
keyoxide, and generally being a bit weary after reading about some of
the more shady dealings of keybase, culminating at some point with its
zoom take-over) this also removes some of its associated systemd
invocations.
Detect X autostart a bit better with a separate service. The service
relies on a shell script which searches for a socket which X creates on
startup and only finishes when it finds the socket succesfully.
This makes services which need X to start successfully a bit more
robust, and while it can still break if X takes too long, it should be
more stable now.
Finally, services can restart more quickly when ended since they don't
require the 2+ `RestartSec` option to be present anymore to successfully
start.
Flashfocus did not start up correctly since it was not required for the
`default.target` which is the only (?) valid target when systemd
operates in user-mode.
Instead of overwriting just part of the flashfocus service file, and
subsequently having it enabled for default.target and a non-existent
graphical.target user environment, we overwrite the whole file and set
it to `default.target`.
Additionally, the service should be restarted when it fails and slow
down on its restart attempts (I kept 5 seconds for this one, since it is
not as time critical as others -- no one cares if windows only flash
5 seconds after starting the machine.)
Added (wishful) After components to many service units, in case I figure
out one day how to make a useful target for the systemd user mode.
Autostarts an2linuxserver, dunst, kbfs, keybase, and the keybase://
redirector.
Will (presumably) complain if one of the programs is missing. Either
this should not be enabled by default or the startup service should
contain a sanity check for the program before attempting to launch
itself.
Both greenclip and redshift did not automatically start on system start,
since they needed X to be running but their restart was almost
instantaneously. So, they restarted their alloted 5 times before X was
ready and gave up.
Restart time has been set to 5 and 10 seconds, so their startup takes a
little longer but should, in most cases, succeed.
Used wrong 'after' designation which would wait forever since it needed
to start after the runlevel which it was designated to run at.
Committed default.target.wants symlink to service file to automatically
enable its autostart on new machines.
This wil only really work for my directory set-up, so perhaps either the
service module should be disabled by default for the installation, be
asked during installation, or simply be manually enabled to autostart
during initial set-up (maybe mention in readme for the module).
