KSystemLog

System Software

Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net

0
Score 50.0%
Description:

KSystemLog is a system log viewer tool for KDE 4

This program is compatible with KDE 4 beta 3 libraries.

This program is developed for being used by beginner users, which don't know how to find information about their Linux system, and how the log files are in their computer. But it is also designed for advanced users, who want to quickly see problems occuring on their server.

KSystemLog has the following features :

* View all the main log of your system, by selecting them directly in a menu
* Tabbed view to allow displaying several logs at the same time
* Auto display new logged lines.
* Fast parsing and reading (more than 10000 lines each 5 seconds)
* Colorize log lines depending on their levels
* Detailed information for each log Lines (in a dedicated dialog)
* Quick filter
* Send a log message manually from a dialog box.
* Save, print and email log files are possible.
* It can parse the following log files of your system :
o System logs
o X.org logs
o Kernel logs
o Authentication logs
o Acpid logs
o Cups logs
o Postfix logs
o Apache logs
o Samba logs
o Daemons logs
o Cron logs
o XSession logs
o Cron logs

You can simply compile KSystemLog using the KDE 4 beta packages available in KUbuntu or other distributions.
Last changelog:

11 years ago

Major improvements :

- Compatibility with KDE 4 beta4
- Fix icon position in search bar
- Add test coverage for Kernel logs
- Support for Suse Kernel logs
- Add joker to file list in configuration
- Auto-recognizition of the opened files

For more details, go to

http://ksystemlog.forum-software.org/changelog.php

C

lastnico

14 years ago

When he tries to install its graphic card and it does not work, or when he wants to know why its file share server (Samba) does not work, and report this to its support/friends. There are hundred and hundred reasons for a user to see system log (check the Windows one to be sure it's not a strange needing)

Report

jsakalos

14 years ago

Hi,

somehow I cannot agree that user should see the system log. This opens a big security hole as system log CAN contain some sensitive information. Even passwords if root forgets to reset log level of a program after debugging.

Further, to install a graphics card of any other piece of hardware the root privileges are required.

Please, don't take Windows as a good security example as it is NOT secure.

User should and normally is able to read only logs like ~/.xsession-errors.

I would appreciate if .desktop file created during installation already contained "Run as root" so kdesu would always start.

Jozef

Report

pdreker

14 years ago

This opens no new "security hole" in any way. Either the the user is allowed to view the logs, because the permissions on the logfiles say so, or he isn't.

On a server the normal users should not be able to view the logs, and thus root needs to tie down the permissions. No app is going to change that point.

On a desktop the normal user usually also is root. So no problem here, if that normal user is able to check the logfiles.

My point being: The file permissions define, who is able to see the logs and who isn't, not some app. If ksystemlog can read the logs as a normal user, so can "less" in a shell.

Report

C

lastnico

14 years ago

Yes, but you are talking about a multi-user Linux system with a specifical Administrator.

Today, Linux is also on simple machine, with 1 main user (which is also the root), and satellite user, like your wife, or your children.

Of course, KSystemLog is useful for this two cases : the administrator in the 1/ and the poweruser in the 2/

The fact that KSystemLog exists will not automagically change the rights of your log files, so KSystemLog is not the problem here. KSystemLog is only a way to display finely log files of your system, only if you have the rights to read them.

I have plan with neoclust to add the kdesu feature (1 line modified in .desktop file), but as you said, log files in user home are also interested, and maybe will be parsed by KSystemLog a day, so I'm not sure to always keep this kdesu, and it's not a problem.

Report

kanotixfan

14 years ago

oh yeah, this app is definitely very usefull! Thanks a lot!

Report

blaster999

14 years ago

Hi! This is a nice app, but...
When I launch it (as root, to be able to read /var/log/messages), it eats ALL my memory. First RAM, then swap, and then my computer becomes unresponsive at all (when kernel tries to find something to kill I think). It also uses 100% CPU. I don't know what's causing it, but it's not good at all. If you need further info (KDE version or kernel version or something) just ask.

Report

C

lastnico

14 years ago

ouch !!

Can you send me your system log files ?

If you can't send me, please just send a part of them, or something which always makes KSystemLog consuming too much memory.


This problem can have 2 reasons :
- Strange characters in this file (aargh, I have to manage this $*-(%? characters!)
- A bug in KSystemLog (it will be not so strange ;-)

Sorry for this problem ;-(

Report

XamDM

14 years ago

Realy nice app, would be nice to have a trayicon

keep up the good work

Xam

Report

kanotixfan

14 years ago

This app is really usefull! Thanks! We need more of these nice system tools in KDE!

Report

gigi

14 years ago

The one for 0.2.2 is still valid for 0.3

Report

cado

14 years ago

Hi,

KsystemLog 0.3 available on Debian at http://pacotesdeb.codigolivre.org.br

Requeriments:

KDE 3.4.1

Report

vdboor

14 years ago

This is a nice application. I must say I've never had such a good overview of all errors in my log files. :-)

I think it has a lot of potential. It still has room for improvement, e.g:
- detect and mark common errors
- explain standard messages
- parse common lines, like iptable/cron/auth lines
- parse distro-stuff like SuSE's SFW2-* prefixes for iptables.
- detect log files automatically
In other words: make sure log files can be read efficiently and errors can be spotted quickly (like sysadmins can in the Windows 2000 event log) :-) I wish I could help you, but I have another project running myself.

One other thing: the process column often shows stuff like cron[435] cron [14412], etc... Could you detect this "thread identifier"?

Report

C

lastnico

14 years ago

Thanks for your ideas vdboor !

- detect and mark common errors

This will be done by a plugin management (certainly with KJSEmbed), user will be able to add "detector" scripts, which will popup messages if some specials lines are discovered (ex: nvidia proprietary loading failed...)


- explain standard messages

I think this will be done in the same way than your previous request

- parse common lines, like iptable/cron/auth lines

Cron and Auth are already done, but IPtables is in the TODO list

- parse distro-stuff like SuSE's SFW2-* prefixes for iptables.

Yes, of course, I add it to my TODO-list

- detect log files automatically

Planned to the next version.

One other thing: the process column often shows stuff like cron[435] cron [14412], etc... Could you detect this "thread identifier"?

Yes I can detect it, but I'm not sure to want to add a special column for this because it seems that only Cron process use this kind of special thing.

Do not hesitate to comment my answer ;-)

Report

vdboor

14 years ago

Thanks for your feedback. I'm looking forward to the next release.

> I'm not sure to want to add a
> special column for this because

Well, why add another column for it? Could you ignore/remove the [num] part?

> it seems that only Cron process
> use this kind of special thing.

At my system, gpm, nmbd, sshd, xinetd, kdm_config, hotway seam to do the same thing. I believe the number just represents the process/thread number the event was fired from. That's why I think this information can be ignored in a "aggegrator" kind-of-thing like KSystemLog is.

Report

C

lastnico

14 years ago

OK, I didn't know that other process used this kind of thing. I will delete the process number automatically in the next version (and add an option to keep it)

Thanks for this idea!

Report

amdfanatyk

14 years ago

In file included from ksystemlog.cpp:73:
ksystemlog.h:168: error: `class KAction::ActivationReason' has not been declared
ksystemlog.h:168: error: ISO C++ forbids declaration of `reason' with no type
ksystemlog.h: In constructor `KSystemLog::KSystemLog()':
ksystemlog.h:306: warning: `KSystemLog::findDialog' will be initialized after
ksystemlog.h:285: warning: `KFind*KSystemLog::findManager'
ksystemlog.cpp:93: warning: when initialized here
ksystemlog.h:316: warning: `KSystemLog::loadingDialog' will be initialized after
ksystemlog.h:296: warning: `LogListItem*KSystemLog::previousItemFound'
ksystemlog.cpp:93: warning: when initialized here
ksystemlog.cpp: At global scope:
ksystemlog.cpp:1142: error: variable or field `slotLogAction' declared void
ksystemlog.cpp:1142: error: `int KSystemLog::slotLogAction' is not a static member of `class KSystemLog'
ksystemlog.cpp:1142: error: `ActivationReason' is not a member of `KAction'
ksystemlog.cpp:1142: error: expected primary-expression before "state"
ksystemlog.cpp:1142: error: initializer expression list treated as compound expression
ksystemlog.cpp:1142: error: expected `,' or `;' before '{' token
ksystemlog.cpp: In member function `void KSystemLog::groupByChanged(int)':
ksystemlog.cpp:1641: warning: comparison between signed and unsigned integer expressions
ksystemlog.cpp: In member function `void KSystemLog::updateGroupBy()':
ksystemlog.cpp:1711: warning: comparison between signed and unsigned integer expressions
In file included from ksystemlog.cpp:1833:
ksystemlog.moc: In member function `virtual bool KSystemLog::qt_invoke(int, QUObject*)':
ksystemlog.moc:227: error: `ActivationReason' is not a member of `KAction'
ksystemlog.moc:227: error: `ActivationReason' is not a member of `KAction'
ksystemlog.moc:227: error: expected primary-expression before ')' token
ksystemlog.moc:227: error: expected `)' before "static_QUType_ptr"
ksystemlog.cpp: At global scope:
ksystemlog.cpp:802: warning: unused parameter 'text'
ksystemlog.cpp:802: warning: unused parameter 'matchingIndex'
ksystemlog.cpp:802: warning: unused parameter 'matchingLength'
make[2]: *** [ksystemlog.o] Błąd 1
make[2]: Leaving directory `/home/amdfanatyk/Desktop/nk/ksystemlog-0.3/src'
make[1]: *** [all-recursive] Błąd 1
make[1]: Leaving directory `/home/amdfanatyk/Desktop/nk/ksystemlog-0.3'
make: *** [all] Błąd 2

Report

C

lastnico

14 years ago

I'm trying to find a solution with KDE hackers to this annoying problem (KSystemLog uses new functions from KDE 3.4, and it can't compile with older version (for the moment))

Sorry for this problem, I try to fix it ASAP...

Report

maarizwan

14 years ago

but a small preview section for the message would be good. Just like Preview in the file open dialog. Thanks a lot! Love it!

Report

C

lastnico

14 years ago

What do you mean with a preview of the messages ? Sorry, I don't understand well.

Thanks to like KSystemLog.

Report

gnemmi

14 years ago

on Conectiva Linux 10
KDE 3.3.2
QT 3.3.3

ksystemlog.h: En constructor `KSystemLog::KSystemLog()':
ksystemlog.h:306: aviso: `KSystemLog::findDialog' will be initialized after
ksystemlog.h:285: aviso: `KFind*KSystemLog::findManager'
ksystemlog.cpp:93: aviso: when initialized here
ksystemlog.h:316: aviso: `KSystemLog::loadingDialog' will be initialized after
ksystemlog.h:296: aviso: `LogListItem*KSystemLog::previousItemFound'
ksystemlog.cpp:93: aviso: when initialized here
ksystemlog.cpp: En la función miembro `void KSystemLog::highlightSearch(const
QString&, int, int)':
ksystemlog.cpp:802: aviso: unused parameter `const QString&text'
ksystemlog.cpp:802: aviso: unused parameter `int matchingIndex'
ksystemlog.cpp:802: aviso: unused parameter `int matchingLength'
ksystemlog.cpp: At global scope:
ksystemlog.cpp:1142: error: `ActivationReason' is not a member of type `KAction
'
ksystemlog.cpp:1142: error: error de decodificación before `,' token
ksystemlog.cpp: En member function `void KSystemLog::slotLogAction(...)':
ksystemlog.cpp:1161: error: `state' undeclared (first use this function)
ksystemlog.cpp:1161: error: (Each undeclared identifier is reported only once
for each function it appears in.)
ksystemlog.cpp: En member function `void KSystemLog::groupByChanged(int)':
ksystemlog.cpp:1641: aviso: comparison between signed and unsigned integer
expressions
ksystemlog.cpp: En member function `void KSystemLog::updateGroupBy()':
ksystemlog.cpp:1711: aviso: comparison between signed and unsigned integer
expressions
In file included from ksystemlog.cpp:1833:
ksystemlog.moc: En member function `virtual bool KSystemLog::qt_invoke(int,
QUObject*)':
ksystemlog.moc:227: error: `ActivationReason' is not a member of type `KAction'
ksystemlog.moc:227: error: `ActivationReason' is not a member of type `KAction'
ksystemlog.moc:227: error: error de decodificación before `)' token
ksystemlog.moc:227: error: error de decodificación before `)' token
make[2]: *** [ksystemlog.o] Error 1
make[2]: *** Se espera a que terminen otras tareas....
make[2]: Leaving directory `/home/gnemmi/paquetes/ksystemlog/BUILD/ksystemlog-0.3/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gnemmi/paquetes/ksystemlog/BUILD/ksystemlog-0.3'
make: *** [all] Error 2

see ya

Report

C

lastnico

14 years ago

Ouch, I will try to fix this tonight (it's a bit more complicated than I thought)
Thanks for reporting!

Report

C

lastnico

14 years ago

mmmh..

could you translate this log in english please, because I don't understand your language ;-)

Thanks!

Report

amdfanatyk

14 years ago

recent logs might be useless because I had compiled ksystemlog without debug but now i have that:

after logs reload:

[bash output]
QDate::setYMD: Invalid date 2005-01-00
failed to read() from server connection
KCrash: Application 'ksystemlog' crashing...
[/bash output]

crash ... bye bye ... ;(

Report

amdfanatyk

14 years ago

but why Your app isn't dockable??!!

Report

C

lastnico

14 years ago

It will be in the 0.4 version... Sorry to make you waiting ;-)

++

Report

11 years ago

Major improvements :

- Compatibility with KDE 4 beta4
- Fix icon position in search bar
- Add test coverage for Kernel logs
- Support for Suse Kernel logs
- Add joker to file list in configuration
- Auto-recognizition of the opened files

For more details, go to

http://ksystemlog.forum-software.org/changelog.php

12345678910
product-maker Count: 4 Rating: 5.0
File (click to download) Version Description PackagetypeArchitectureRelease Channel Downloads Date Filesize DL OCS-Install MD5SUM
*Needs ocs-url or ocs-store to install things
Pling
Details
license
version
0.4.1
updated Nov 07 2007
added May 04 2005
downloads 24h
0
page views 24h 4
System Tags app software