Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Does anyone know of a good tool for breaking down the likes of, /var/log/messages. My firewall is filling up this file to the point of AAAaaaaHHHHhhhhhhhhhhh..... I know that i could probably set the firewall up to write to a different file (am lazy) I am not sure if that is a good idea anyway?. Know of any tools ????
I do not know if there is any. Maybe you could google search the web.
Or you can create your own tool anytime using e.g. bash, grep, awk, sed. If you have any specific ideas what you expect from the tool, I am ready to help to write it (though I am not a script guru at all).
My favorite workhorse is logcheck. It sifts through the logs (can do it automatically as a cron and send you a summary). The nice thing is it flags everything as bad unless you tell it specifically to ignore it in the future. So you'll see everything that's new, but after a few days of running and twaking it, it condenses MB's of logs down to the 10 lines that you need to see. I get through about 80 machines worth of syslogs this way with ease.
It''s not an analysis tool in the sense that it tells you what happened, but what it does is invaluable.