On Wednesday, April 15, 2015 10:46:23 PM Luigi Toscano wrote: > David Edmundson ha scritto: > > On Wed, Apr 15, 2015 at 10:18 PM, Albert Astals Cid <aa...@kde.org > > > > <mailto:aa...@kde.org>> wrote: > > El Dimecres, 15 d'abril de 2015, a les 15:09:03, Luigi Toscano va escriure: > > > On Wednesday 15 of April 2015 14:49:16 Ragnar Thomsen wrote: > > > > Hey all, > > > > > > > > I have started development of a log viewer for journald, which I > > > > have > > > > tentatively called Journalktl. Currently, it is pretty basic but > > > > shows > > > > date/time, unit name and log message. It allows for showing > > > > journal > > > > entries based on boot ID, searching in messages and unit names, > > > > and > > > > filtering log messages based on priority. > > > > > > > > Journalktl can be found here: > > > > git://anongit.kde.org/scratch/rthomsen/journalktl.git > > > > <http://anongit.kde.org/scratch/rthomsen/journalktl.git> > > > > > > Please give it a try, and let me know what you think :) > > > > > > Did you consider extending ksystemlog? A unified interface would be > > > nice, I > > > think, if it's possible. > > > > +1 > > > > or just replace it. > > It hasn't been touched since 2009 beyond test fixes and scripty. > > As long as the new program allows access to the text-based log files, sure. > For sure they are not going to disappear in every scenario, accessing them > is still useful.
There are all kinds of log files that don't and won't have journald replacements, so I don't there is a scenario where they disappear. journald isn't a general syslog replacement. Scott K >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<