Very cool! I discovered the console option by accident. I changed it and F12 immediately started working without even having to restart the journal. Optionally we also have the ability now to achieve the same thing by opening a console window and executing the command (su'd to root, of course) `journalctl -f`:
- Code: Select all
[root@localhost ghmitch]# journalctl -f
-- Logs begin at Fri, 2013-06-07 20:06:40 PDT. --
Jun 07 20:46:52 localhost.localdomain sensord[1456]: fan5: 1068 RPM (min = 712 RPM, div = 8)
Jun 07 20:46:52 localhost.localdomain sensord[1456]: temp1: 35.0 C (limit = 60.0 C, hysteresis = 55.0 C)
Jun 07 20:46:52 localhost.localdomain sensord[1456]: temp3: 48.0 C (limit = 91.0 C, hysteresis = 86.0 C)
Jun 07 20:51:09 localhost.localdomain acpid[1300]: client 1413[0:0] has disconnected
Jun 07 20:51:09 localhost.localdomain acpid[1300]: client connected from 1413[0:0]
Jun 07 20:51:09 localhost.localdomain acpid[1300]: 1 client rule loaded
Jun 07 20:55:31 localhost.localdomain su[5342]: (to root) ghmitch on /dev/pts/1
Jun 07 20:55:31 localhost.localdomain su[5342]: pam_tcb(su:session): Session opened for root by ghmitch(uid=501)
journalctl -f will provide you with an ongoing flow of console messages just like F12 in a console window (Konsole, Eterm, Xterm, etc). So we now have two ways to achieve the same thing. And as noted above, rsyslog will restore "messages" and "syslog" files in /var/log.
- George