Run an aklog before systemd --user
Currently the aklog is called from within "systemd -user" as a user unit.
This is too late as systemd --user needs to access $HOME/.config/systemd.conf for instance at start up.
Instead run aklog within a new "user-aklog@.service" as a forced dependent unit for user@.service.
This is the same mechanism as for instance "user-runtime-dir@.service" uses to create $XDG_RUNTIME_DIR.