http://bugzilla.suse.com/show_bug.cgi?id=948729 http://bugzilla.suse.com/show_bug.cgi?id=948729#c2 --- Comment #2 from Olli Tuominen <otuominen@novell.com> --- If there is already better YaST module for it then drop the old as it does not track correct logs. However I don't want to code it myself ;) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=948729 http://bugzilla.suse.com/show_bug.cgi?id=948729#c4 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ancor@suse.com) | --- Comment #4 from Ancor Gonzalez Sosa <ancor@suse.com> --- Reasons for not dropping the old module, even though we have "yast2-journal" (accessible as "Systemd Journal" in the icon next to the old "System log" one): - /var/log/messages is still used if syslog is installed. Many users decide to install it because they prefer the old text-based logs. - It's useful to track other log files like /var/log/boot.log or even any other when configured to do so. So for me is a WONTFIX, but I don't have a strong opinion about it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=948729 http://bugzilla.suse.com/show_bug.cgi?id=948729#c8 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jreidinger@suse.com --- Comment #8 from Josef Reidinger <jreidinger@suse.com> --- (In reply to Olli Tuominen from comment #7)

Ok - for me, having two different programs to view "system logs" are quite pointless however I understand point of view to enable user choose which one he prefers. UX is king nowadays! ;)

So you can choose if you close this as wontfix but my opinion is to integrate these two ones.

problem is that goal of first module is to have generic module for text based logs. The goal of new module is to have specialized journalctl module, that can use many journalctl features. So it is different tools and different goals for them. What we can maybe do is to allow showing in old one simple full unfiltered output from journalctl. Ancor do you think it make sense? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=948729 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|YaST: System Log |YaST: If syslog is not | |used, point from old | |"System Log" to newer | |"Systemd Journal" -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=948729 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|yast2-maintainers@suse.de |yast-internal@suse.de -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=948729 http://bugzilla.suse.com/show_bug.cgi?id=948729#c12 Josef Reidinger <jreidinger@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #12 from Josef Reidinger <jreidinger@suse.com> --- fix merged. Enjoy it in TW and Leap 15.1 -- You are receiving this mail because: You are on the CC list for the bug.