reading /var/log/messages
Reading the log file is a mess. Most of the messages do not make sense or are booring. Finding what is really important is a hard task - even with grep.
IASON can read the logfile for you.
cat /var/log/messages | pl2txt | more
xinetd_open("Apr-25","00:58:48","telnet","192.168.48.226").
xinetd_user("Apr-25","00:58:48","telnet","fafnir").
Somebody from the local lan logged in and used ftp.
noip_ip("gargoyle.example.com","192.0.2.18","Apr-25","01:50:46").
My service provider kicked my out. My router logged in again and got a new ip.
Thankyou "no-ip.com" for providing dynamic dns services.
xinetd_open("Apr-25","12:04:25","ssh","206.19.84.11").
xinetd_open("Apr-25","12:04:28","ssh","206.19.84.11").
xinetd_close("Apr-25","12:04:28","ssh").
Somebody not invited tried to pay me a visit. The door was locked.
named_start("Apr-25","11:20:49","BIND 9.2.3 -t /var/lib/named -u named").
named_command("Apr-25","11:20:50","127.0.0.1","953").
My nameserver has been started again and tells me what doors are open.
named_command("Apr-25","11:20:50","IP127000000001","PORT00953").
"PORT00953" is another internal coding to make life easier.
sort, grep and pl2txt can be used as filters. msg2pl itself is a filter.
|
