SlackwareThis Forum is for the discussion of Slackware Linux.
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'm using it happily since some time on our debian hosts for remote secure logging via gnutls, it has a lot of features plus it's backward compatible with sysklogd (it's an alternative to the one installed in standard slackware).
Just tested it here and everything went fine; the system didn't even notice the change, and better, an updated system log tool. I liked it a lot.
However, one thing was annoying me: every single message from the kernel were being printed to console stdout and the system here boots into init 3. To fix this, I just added a backward compatibility with klogd -c 3 behaviour: on rsyslog.conf, just added
And everything is back to normal. :-)
Last edited by rfernandez; 10-15-2010 at 11:55 PM.
Reason: bad grammar
The coolest thing, I think, about rsyslogd is it's simplicity, compatibility and daily updated support. For example: My /var/log/syslog gets constantly unreadable because of iptables log messages, so, I just added some lines in the rsyslog.conf that are clearly explained at the rsyslog webpage and voilą, I have rsyslog to separate iptables messages into another file and keeps syslog lean and clean. :-)
glad you like it: here Rainer explains how it's born and why it exists.
it's, relatively speaking, a little bit heavier (still having a nearly undetectable load, multi-cpu aware too) and it needs more space (we're talking of 2 megabytes of docs and another megabyte with the rest, uncompressed) than sysklogd but its nice features (easy filtering and redirecting, logging to database, remotely through secure connections and so on) can be useful in a lot of scenarios.