05-30-2019
I was able to get this resolved by logging in as root, instead of using sudo from my user account.
I thought sudo invokes the root permissions, but perhaps not fully?
10 More Discussions You Might Find Interesting
1. Red Hat
Hi,
I am beginer to Linux. I have installed Redhat Linux AS 4.0 on my System.Later I created a User Oracle10g for Installing Oracle.Then I logged onto Oracle10g user and crated a Bash Profile and when I run that profile there was an error in that Profile. from then If I type any of Linux Command... (2 Replies)
Discussion started by: praswer
2 Replies
2. Shell Programming and Scripting
Hello everyone,
I am using Linux and tcsh shell. I am trying to run a free open source program( which is in the form of a binary file), but every time I run it it gives me an error saying:
newhtsg_v1.0:Command not found.
I have set permission also for the same.
What else can I do to make... (4 Replies)
Discussion started by: ad23
4 Replies
3. IP Networking
$ host 80.159.xx.xxx
Host 222.79.xxx.xxx.in-addr.arpa not found: 3(NXDOMAIN)
What does this mean? The person currently using the IP address in IRC is chatting right now, but how come if he's online it doesn't return any information? (1 Reply)
Discussion started by: guitarscn
1 Replies
4. Shell Programming and Scripting
I have been experiencing this problem intermittantly, I thought the problem was '/bin/sh -> /bin/dash' but I changed that to bash and the problem persists.
I am writing functions to be included in user's '.bash_profile' through source or '.' filename a quick example of the problem is illustrated... (3 Replies)
Discussion started by: bsquared
3 Replies
5. UNIX for Dummies Questions & Answers
I have a program called abc installed in /usr/local/bin.
My path is as follows:
# echo $PATH
/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin
However, when entering the abc command, the following error appears:
# abc
abc: Command not found
When... (7 Replies)
Discussion started by: figaro
7 Replies
6. Linux
I installed in VM the Mandriva Linux.
But when I fire the make command it gives me command not found error.
Seems make is not installed.
I also checked in Mandriva control center and no development package is seen there.
Will pls let me know how to proceed and get make and other development... (2 Replies)
Discussion started by: rupeshkp728
2 Replies
7. Shell Programming and Scripting
Hello All,
I am running source command on my project configuration file app.cfg which has conditional statements with make file systax E.g ifeq ($(APP_CMP_DIR),trunk).
When I source this file it throws error: syntax error near unexpected token... (1 Reply)
Discussion started by: anand.shah
1 Replies
8. UNIX for Dummies Questions & Answers
$ cat nu
who | wc -l
$ ls -l nu
-rwxr-x--- 1 _ _ 11 Jul 30 12:37 nu //the nu is displayed in green color
$ nu
bash: nu: command not found
I am using a book from 1986 on Unix System V, Release 3, and the Unix system I am connecting to is from my college.
Below is the notes from the book:... (4 Replies)
Discussion started by: chip
4 Replies
9. Shell Programming and Scripting
Could you let me know if my path is having bourne bash
echo $PATH
/u01/app/oracle/product/10.2.0/db_1/bin:/usr/sbin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/oracle/bin
$ which bash
/bin/bash
$ which ls
alias ls='ls --color=tty'
/bin/ls
Below is... (3 Replies)
Discussion started by: csguna6
3 Replies
10. IP Networking
One of our email recipients has 17 mx records, and our emailing program postfix on linux does not retrieve these records. When using dig, the same thing happens.
This command returns no mx records
>dig mx fnb.co.za
But when using +trace, the records get returned
>dig mx fnb.co.za +trace
... (4 Replies)
Discussion started by: Joop Kaashoek
4 Replies
LEARN ABOUT LINUX
sudo_root
sudo_root(8) System Manager's Manual sudo_root(8)
NAME
sudo_root - How to run administrative commands
SYNOPSIS
sudo command
sudo -i
INTRODUCTION
By default, the password for the user "root" (the system administrator) is locked. This means you cannot login as root or use su. Instead,
the installer will set up sudo to allow the user that is created during install to run all administrative commands.
This means that in the terminal you can use sudo for commands that require root privileges. All programs in the menu will use a graphical
sudo to prompt for a password. When sudo asks for a password, it needs your password, this means that a root password is not needed.
To run a command which requires root privileges in a terminal, simply prepend sudo in front of it. To get an interactive root shell, use
sudo -i.
ALLOWING OTHER USERS TO RUN SUDO
By default, only the user who installed the system is permitted to run sudo. To add more administrators, i. e. users who can run sudo, you
have to add these users to the group 'admin' by doing one of the following steps:
* In a shell, do
sudo adduser username admin
* Use the graphical "Users & Groups" program in the "System settings" menu to add the new user to the admin group.
BENEFITS OF USING SUDO
The benefits of leaving root disabled by default include the following:
* Users do not have to remember an extra password, which they are likely to forget.
* The installer is able to ask fewer questions.
* It avoids the "I can do anything" interactive login by default - you will be prompted for a password before major changes can happen,
which should make you think about the consequences of what you are doing.
* Sudo adds a log entry of the command(s) run (in /var/log/auth.log).
* Every attacker trying to brute-force their way into your box will know it has an account named root and will try that first. What they do
not know is what the usernames of your other users are.
* Allows easy transfer for admin rights, in a short term or long term period, by adding and removing users from the admin group, while not
compromising the root account.
* sudo can be set up with a much more fine-grained security policy.
* On systems with more than one administrator using sudo avoids sharing a password amongst them.
DOWNSIDES OF USING SUDO
Although for desktops the benefits of using sudo are great, there are possible issues which need to be noted:
* Redirecting the output of commands run with sudo can be confusing at first. For instance consider
sudo ls > /root/somefile
will not work since it is the shell that tries to write to that file. You can use
ls | sudo tee /root/somefile
to get the behaviour you want.
* In a lot of office environments the ONLY local user on a system is root. All other users are imported using NSS techniques such as
nss-ldap. To setup a workstation, or fix it, in the case of a network failure where nss-ldap is broken, root is required. This tends to
leave the system unusable. An extra local user, or an enabled root password is needed here.
GOING BACK TO A TRADITIONAL ROOT ACCOUNT
This is not recommended!
To enable the root account (i.e. set a password) use:
sudo passwd root
Afterwards, edit the sudo configuration with sudo visudo and comment out the line
%admin ALL=(ALL) ALL
to disable sudo access to members of the admin group.
SEE ALSO
sudo(8), https://wiki.ubuntu.com/RootSudo
February 8, 2006 sudo_root(8)