I have had a problem with it -- or, rather, a problem which it made more difficult. From a comment a few months ago in a systemd thread (https://news.ycombinato

I have had a problem with it -- or, rather, a problem which it made more difficult. From a comment a few months ago in a systemd thread (https://news.ycombinator.com/item?id=5124589 https://news.ycombinator.com/item?id=5124589): > "Getting smbd/nmbd to work again was a real adventure. Like other users reported, it would just silently fail when starting it from systemd. No error message when issuing the start command, and only a vague "failed" in status. I ended up having to track down Lennart's blog post on "systemd for administrators" to figure out how in blazes to extract anything useful from that cussed binary log system he invented. My first half-dozen or so attempts to get anything useful out of the log journal got exactly zero results; I finally got lucky on another approach..." I'm really not fond of the idea of having to search logs for information. Being able to page through them is actually super nice. Being able to tail -f them while kicking a process over and over again to see why it's mad at me is also really nice. I think I've heard that some people have come up with tools that will translate the binary log data back to text again, which helps, but that seems a little silly. I'm running Debian (on everything that's not running BSD) now in part because they've been deft so far about handling the transition to systemd. I'm sure Debian will switch to it eventually, but I also trust them to make sure the major issues are all dealt with before they do.