[SOLVED] No logs on Ctrl-Alt-F12

[cambriz]

In Mageia 3 Ctrl-Alt-F12 doesn't show logmessages.
This worked fine in previous versions Mageia 1 and Mageia 2.
But in Mageia 3 the screen only shows a cursor in the top left corner

What can I do to fix this ?

[djennings]

In Mageia 3 Ctrl-Alt-F12 doesn't show logmessages.
This worked fine in previous versions Mageia 1 and Mageia 2.
But in Mageia 3 the screen only shows a cursor in the top left corner

If there is a change in behaviour it is probably because Mageia 3 uses journalctl instead of syslog.
If you install the rsyslog package you will get syslog back.

[doktor5000]

That is defined in /etc/inittab, by default it now only has 6 ttys:

[...]
# Run gettys in standard runlevels
1:2345:respawn:/sbin/mingetty tty1
2:2345:respawn:/sbin/mingetty tty2
3:2345:respawn:/sbin/mingetty tty3
4:2345:respawn:/sbin/mingetty tty4
5:2345:respawn:/sbin/mingetty tty5
6:2345:respawn:/sbin/mingetty tty6
[...]

For more information you may want to look at http://superuser.com/questions/266091/h ... -real-time

Was also discussed/proposed in http://archives.mageia.org/zarb-ml/mage ... 22650.html

[doktor5000]

Was also discussed/proposed in http://archives.mageia.org/zarb-ml/mage ... 22650.html

Seems to work partly, as suggested add the following to /etc/systemd/journald.conf

Code: Select all

TTYPath=/dev/tty12
ForwardToConsole=yes

and then restart journal via

Code: Select all

systemctl restart systemd-journald.service

[ghmitch]

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

[cambriz]

Thank you all for your response. Nice to see that there are several ways to achieve this.