ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
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.
Hi guys,can you help me with my problem? I have a script that is supposed to run as a different user. My problem is when I include su - user in my bash script,it always asks the password of the user which should not be the case because the script would be interrupted. Im running my script on a Solaris based server. Thanks in advance.
Sure, he certainly goes as you believe, as he got the prompt, I was just suggesting a different way.
As the script is looking like being non interactive, it would perhaps be easy to have it primarily run as root and switching to users on demand.
On the other hand, running scripts as root induce a security risk, so sudo (or Solaris RBAC) are probably a better option.
My biggest worry (as you say) with running scripts as root is a security risk. They are PARTICULARLY prone to symlink attacks. (i.e., putting values into /tmp/scriptname.tmp or some similar predictable file)