after a recent system upgrade on my RaspberryPi with Archlinuxarm with lots of update for systemd and other packages I had serious troubles with the graphical interface. Therefore I disabled lightdm.service. But some serious problems still persist:

1) systemd is not able to start logind-service (see part of syslog below)

2) logind-service finally enters failed state and can't be activated manually

3) crond functionality @reboot is broken 

4) although logind remains in failed state logins are still possible ! 

The syslog below seems to indicate that the error might occur due to interference with crond. No other hints why logind-service fails. 

----------------------------------
syslog after boot:
Aug  4 03:16:02 mars systemd[1]: Stopping NFSv4 ID-name mapping service...
Jan  1 01:00:05 mars systemd[1]: Starting Slices.
Jan  1 01:00:05 mars systemd[1]: Reached target Slices.
Jan  1 01:00:05 mars systemd[1]: Expecting device dev-mmcblk0p1.device...
Jan  1 01:00:04 mars systemd[1]: Mounted RPC Pipe File System.
Jan  1 01:00:04 mars systemd[1]: Mounted POSIX Message Queue File System.
Jan  1 01:00:04 mars systemd[1]: Mounted Debug File System.
Jan  1 01:00:04 mars systemd[1]: Mounted Temporary Directory.
Jan  1 01:00:04 mars systemd[1]: Started Collect Read-Ahead Data.
Jan  1 01:00:04 mars systemd[1]: Started Replay Read-Ahead Data.
Jan  1 01:00:04 mars systemd[1]: Started Create list of required static device nodes for the current kernel.
Jan  1 01:00:05 mars systemd[1]: Started udev Coldplug all Devices.
Jan  1 01:00:14 mars crond[142]: hape:load_user()
Jan  1 01:00:14 mars crond[142]: linenum=6
Jan  1 01:00:14 mars kernel: systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Jan  1 01:00:14 mars crond[142]: ...load_user() done