Hey Vladimir, Thanks for filling in the gaps. This installation that I'm on is a fresh Fedora 20 (Heisenbug) installation from media. Here is my `yum history info 1` (with some editing for brevity): sudo yum history info 1 Loaded plugins: langpacks, refresh-packagekit Transaction ID : 1 Begin time : Wed Jan 15 19:04:28 2014 Begin rpmdb : 0:da39a3ee5e6b4b0d3255bfef95601890afd80709 End time : 19:52:38 2014 (48 minutes) End rpmdb : 1559:ddc0bb756493d614f12d21ac3bed86c1d42a80d4 User : System <unset> Return-Code : Success Packages Altered: <snip> Install rsyslog-7.4.2-2.fc20.x86_64 @anaconda </snip> ....and if I rpm -qa | grep -i syslog - that's the only package that I see come up. I'd venture to guess the fact that I added on nearly every optional group during the install may have included that package. Even so in any large-scale deployment scenario I too prefer a centralized log server for easier review/management/shipment (to splunk or whatever your preferred log parser may be). Thanks again for filling in my gaps though! ~Steven On Fri, Jan 31, 2014 at 7:14 AM, Vladimir Mosgalin <[log in to unmask] > wrote: > Hi Steven Miano! > > On 2014.01.31 at 06:46:31 -0500, Steven Miano wrote next: > > > I'm currently on Fedora 20 (Heisenbug), and still have a > /var/log/messages. > > Actually, it means that you probably upgraded from F19 or installed > logging service manually. > On F20, one can remove rsyslog - or not install it, if doing fresh > install - and everything will be fine. > > > > > I would add that the old messages are still there - and journalctl simply > > brings another method of finding the information you're looking for. > > Yes, but it stores it in different place; it would work even if you > remove /var/log/messages > > > > > journalctl -b is equivalent to dmesg. > > Not quite. It is equivalent to dmesg+messages+.xsession-errors (or > gdm log) when run from root or .xsession-errors/gdm equivalent when run > from user. Of course, you can ask it to show you only certain categories > of messages; that's main difference to main logging from user > perspective: before, log files were split to different files by category > when message arrived and stored like that, and with journald you split > by category only when viewing these messages. > > > Either way, on server systems I just don't see how journald is going to > obsolete rsyslog, remote logging ability can be a real lifesaver at > times, that alone justifies rsyslog usage.. Until they implement it in > journald, at least. > -- <http://stevenmiano.com/> Miano, Steven M. http://stevenmiano.com