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.
I have checked the privileges for it in the /etc/sudoers files, everything seems to be fine. The scenario is i do not have privileges to edit the httpd conf file. But when i run sudo screen, i login to the screen as root and then i can able to edit the http conf file. How do i block the root access.
You are doing it the wrong way. sudo is a program that can be used to give a user root access to specific applications. You define those applications in the sudoers file. if you don't want to be able to run screen as root don't add screen to your program list in that file. With sudo you have to be very careful and test every application that you add to the list if there are ways to break out from it as root. For example, you shouldn't allow to use Vim or Emacs as root with sudo, since both are able to start shells, which would be started as root in that case.
So the solution for your problem is not to block single applications, but to not allow them in the first place.