World-renowned Unix master Chris Siebenmann has written an article entitled 'I wish systemd would get over its thing about syslog'. It addresses the strained relationship between the systemd init system and the traditional syslog approach to logging used on many Linux systems.
Chris writes:
Anyone who works with systemd soon comes to realize that systemd just doesn't like syslog very much. In fact systemd is so unhappy with syslog that it invented its own logging mechanism (in the form of journald). This is not news. What people who don't have to look deeply into the situation often don't realize is that systemd's dislike is sufficiently deep that systemd just doesn't interact very well with syslog.
This is a must-read article for anyone who needs to use systemd and syslog together.
(Score: 2) by danomac on Monday April 20 2015, @10:40PM
I also noticed that shutdowns take a lot longer - about 3 minutes compared to openrc's 20 seconds. systemd seems to get hung up shutting down apcupsd (even though apcupsd indicates it shut down successfully in journalctl) systemd doesn't seem to notice.
When I was using openrc the IMSM raid array would corrupt at every reboot.
My laptop has no issues with systemd. Just my main desktop.