Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
I am looking for an open source syslog server which accumulate the each and every log of Windows, Solaris, Linux and network devices. Currently I am using Syslog-ng which is not fulfiling my requirement in Windows clients, as I need the logs of every action which user performed after logon.
That is not really what syslog is for. Syslog records the messages sent by systems when triggered by events. It records events for diagnostics, not every action. Overall using a syslog server is wise, but trying to log every action is probably not wise: for one thing you will fill up disks very rapidly.
Not saying you cannot do that, just that you probably should not and that syslog may not be the right tool for that job.
See the problem here is that MS (in their infinite wisdom) chooses to NOT use anyone else's standard solutions until the market forces the issue. (Remember how long it took them to decide it was OK for Windows to do native TCP/IP? I do.) Up to Win2k at least (I stopped checking after that) no windows product nativly spoke syslog. You have to run something that can YANK the log entries out, or add software to windows to make it play well in polite society.
Please forgive me, I added some useful information but neglected to address the original question.
Every major Linux, *BSD, and Unix distribution comes with and uses syslogd. While there are other 'syslog' server tools out there you cannot really get anything better than the GNU syslogd server itself.
You will need to research how to configure it to respond to all of the servers on your network without opening it up to external or unauthorized servers, but that is not difficult.
Note that syslogd does NOT go out and GET log entries, the syslog native to the remote servers must be configured to SEND messages to the syslog server, and it must be configured to ACCEPT those messages.
Once you have set one or two up it all makes sense and seems almost intuitive: it is not and takes some study the first time or two.
Last edited by wpeckham; 12-13-2010 at 11:37 AM.
Reason: spelling corrections