Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
12-29-2008, 01:00 PM
|
#1
|
LQ Newbie
Registered: Jan 2007
Location: Johor, Malaysia
Distribution: Slackware 9.2,12.2,13.0, Debian woody,sarge,etch,Centos5.3
Posts: 22
Rep:
|
Does sudo need a restart to work ?
I'm coming from a Debian background and I used to issue
Code:
/etc/init.d/sudo restart
whenever I made any changes to the sudoer file. But in Slackware, how do I do that ? I just add a user into the sudoer file but I guess I need a restart of the sudo daemon cause I got a 'command not found' after I tried running some root command. (I put 'ALL' privilege for that user) I have spent a lengthy time looking through LQ but could hardly find any guidance, and also after googling for the whole night
And BTW, in Slackware, if I'm not be able to find anything in /etc/rc.d/ that could let me to restart some service or server, where else do I find them or do I need to create one or they will be created during the installation ?
Many thanks for any helping hand, as I'm trying to learn Slackware now.
|
|
|
12-29-2008, 01:28 PM
|
#2
|
Senior Member
Registered: Dec 2008
Posts: 1,190
|
Quote:
Originally Posted by sloganyart
I'm coming from a Debian background and I used to issue
Code:
/etc/init.d/sudo restart
whenever I made any changes to the sudoer file. But in Slackware, how do I do that ? I just add a user into the sudoer file but I guess I need a restart of the sudo daemon cause I got a 'command not found' after I tried running some root command. (I put 'ALL' privilege for that user) I have spent a lengthy time looking through LQ but could hardly find any guidance, and also after googling for the whole night
And BTW, in Slackware, if I'm not be able to find anything in /etc/rc.d/ that could let me to restart some service or server, where else do I find them or do I need to create one or they will be created during the installation ?
Many thanks for any helping hand, as I'm trying to learn Slackware now.
|
There is no "sudo daemon". The in debian does the same as You could look into the script by yourself.
Last edited by guanx; 12-29-2008 at 01:30 PM.
|
|
|
12-29-2008, 01:40 PM
|
#3
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,255
Rep:
|
I'm not a sudo user but AFAIK there are no scripts to start/stop sudo in Slackware, thus I guess you'll have to make one yourself if you need it.
My understanding is that sudo is not so much used by most Slackers. May be they prefer to add relevant users in "powerful" groups like e.g. "wheel", as I do.
About the /etc/rc.d directory, it's basically populated at install time, but some scripts are added depending on which packages you install. This is the case e.g. for networks-scripts, MySQL and Apache.
Side note: if you want to learn Slackware, looking at the stuff in /etc and especially in /etc/rc.d helps a lot. The scripts there are generally well documented.
Tip : to know wich package include a given script, or any other file coming from the "official" distribution, you can use the packages and files browser.
Last edited by Didier Spaier; 12-29-2008 at 01:41 PM.
Reason: typos
|
|
|
12-29-2008, 02:52 PM
|
#4
|
Moderator
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=15, FreeBSD_12{.0|.1}
Posts: 6,306
|
It is the PATH, not the daemon (sounds spiritual)
Quote:
Originally Posted by sloganyart
I just add a user into the sudoer file but I guess I need a restart of the sudo daemon cause I got a 'command not found' after I tried running some root command.
|
That is because the /sbin directory is not on the user's PATH.
In ~/.bash_profile or other suitable location, add:
Code:
export PATH=$PATH:/sbin
The user will need to logout and back in for that to have effect.
|
|
|
All times are GMT -5. The time now is 08:51 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|