Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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.
The first item is the type of message (see 'ausearch -m'), originating from (the PAM stack for) a service or login. uid=0 means the process runs with root account rights, the "auid=4294967295" means the process isn't known to the audit service (possibly started before the audit service was started) and the message means the OpenSSH daemon didn't allow the "test" account to ssh in. IMNSHO one shouldn't have accounts named "test" anyway (use an unique, not-so-easy-to-guess name instead) and guard access rights for testing accounts just like one would for any other account. Check /var/log/secure or equivalent first if this is correct: you should see failed logins there.