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.
Location: Vienna / Austria / Europe / Earth / Milky Way
Re: help with sudo
Originally posted by raven does anybody know how i have to configure sudo so that unprivileged user can execute one speciefied program that uses other programs which also need root permission to run?
The manual page for sudoers(5) is quite exaustive to that topic, it should be able to answer all your questions. It would be something like the following line:
ALL ALL=(root) /usr/bin/wvdial
That would allow all users to run /usr/bin/wvdial as root.
an example is wvdial: it reads/writes from/to privileged files (/etc/ppp/stuff...) accesses a device owned by root (/dev/ttyS1) and then starts a program owned by root (pppd)...
On the other hand - for wvdial it wouldn't be really needed to be run as root at all! wvdial only needs access to that device and the files. You can make those files (at least) readable to a special group, chmod g+rw /dev/ttyS1 and make wvdial sgid to that special group which you put all those files in and the user. That has quite some advantages: An exploit in wvdial wouldn't make the system a big security risk and you can
Does it die for everyone except root? Can each user can have a custom config file in their home directory, or does pppd read from a central config file (in /etc maybe)? If the error is correct, pppd is recieving conflicting instructions from somewhere, and you might have to pick through the file(s) to find the conflict.
Not being familiar with it, that's about all I can offer.