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.
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.
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.
Hi All, I am using Redhat8 and try to permit root command to user "ken" by using sudo, i have edited visudo and try to test it but fail. What's wrong ?
[root@localhost /]# visudo
# sudoers file.
# Host alias specification
# User alias specification
# Cmnd alias specification
# Defaults specification
# User privilege specification
root ALL=(ALL) ALL
ken ALL=(ALL) ALL
# Uncomment to allow people in group wheel to run all commands
# %wheel ALL=(ALL) ALL
[ken@localhost tracy]$ sudo service xinetd restart
sudo: service: command not found
[ken@localhost tracy]$ sudo init 0
sudo: init: command not found
sudo opens up a new shell with your current path, with elevated privs as per sudoers file.
Normally (and for good security), the current dir (ie '.') is NOT in your path, otherwise a hacked prog in your 'current' dir could be run by you with elevated privs.
Always use full path for cmds called via sudo, or specify the cmd in the sudoers file (better/more secure).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.