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.
Make sure 'PermitRootLogin' is enabled on the sshd_config on the server side. Then just su to become root and run the command. Or the alternative is to add that command to the sudoers file and sudo command.
Make sure 'PermitRootLogin' is enabled on the sshd_config on the server side. Then just su to become root and run the command.
Using 'su' and the sshd_config "PermitRootLogin" directive are not related. Regardless you should never offer "PermitRootLogin Yes" as default answer unless the OP has ensured that this is a secured, trusted and isolated network and the OP understands the risks of doing things the non-SOP way.
I want to remote login as a non root user and then run a command under the root account. I have set up the ssh/scp for the non root user and this configuration works fine.
What I dont know is how to run a command under root once remotly logged in as the non-root account. I have to run this command under root, it cannot be changed. If anyone knows how to do this or has any suggestions that would be great.
Systems are Redhat ES5 x64 2.6
You CAN allow remote root logins, but that's horribly unsafe. Better if you log in as a 'regular' user. Once there, you've got a couple ways to go:
You can use 'expect' to script things, so the regular user just runs "su - root", then 'logs in', thereby putting them in as root, to run the script.
You can (better), put the script on the remote box. Put the regular user into the SUDO'ers file, make sure it doesn't prompt for a password. Then, run it with "sudo -u root -s <script name>". Will then execute as root.