10-04-2017
Esc-k and command history
Good afternoon, I am an Oracle DBA that is a bit stumped on the sudo and viewing historical commands. In the past on solaris 10 we would all first use our own username and password to putty to our unix box. Then in our /home/"my username"/.profile file it is setup to use sudo -u oracle for us to be able to utilize the oracle account on the unix box. When we did if we ever did esc-k we would only see our own command history. Now on Solaris 11 it seems that we see everyone's history commands when we perform exactly the same steps as before. Any clue on where and why this has changed? Also any suggestions on how to fix it? Thanks.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I am using ksh shell, and I am unable to use the command !n (where n is the number in the history list).
Please help me...
:confused: (2 Replies)
Discussion started by: jack
2 Replies
2. UNIX for Dummies Questions & Answers
Dear Techs,
In the past on a different box (HP) I use to be able to complete something I was typing by entering a portion of the filename in the pwd and I would hit the Esc key and it would match the rest of the filename. I did this without understanding how it was setup.
Now I am on a new... (1 Reply)
Discussion started by: jxh461
1 Replies
3. UNIX for Dummies Questions & Answers
How do I make the history command, in addition to the past commands, display the hard path to the place where i modified or did my past action?
thanks in advance (2 Replies)
Discussion started by: cleansing_flame
2 Replies
4. Filesystems, Disks and Memory
I am working on solaris and audit is not configured on server.
I get last commands used on server by HISTORY command, but I want some extra information like by which user command fired & by which host id
Because same time we have many people use one login & fire commands
& want History command... (2 Replies)
Discussion started by: akash_wagh
2 Replies
5. UNIX for Dummies Questions & Answers
hi,
i had to submit a project into a directory. i copied it from my location to the specified folder, no problemo.
just one thing though.
after i copied and searched for the time i copied using the history command, the system would not show. even using the up arrow key would not display my... (0 Replies)
Discussion started by: iluvsushi
0 Replies
6. UNIX for Dummies Questions & Answers
Hi All.
Suppose I am in a "verylongpath" directory and I type "gedit thisfile".
At a later stage, the command is accessible from the hystory, but it is
useless if I have moved to another directory. The same applies to
"cd myfolder", etc.
Is there a way to instruct shell history to... (1 Reply)
Discussion started by: bruno69
1 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
How can i view command history of a day.
when i used history command in my AIX server, it shows only last 16 commands. Is there a location where all the history is stored ?
Thanks in advance! (2 Replies)
Discussion started by: lramsb4u
2 Replies
8. UNIX for Dummies Questions & Answers
Can anyone tell this:
If two users are logged into the same server from different locations. Is there a way to see the history command of the other user? I tried the history command, but it is showing me only the commands I used.
Thanks in advance for your help.
Iamnew2solaris (1 Reply)
Discussion started by: iamnew2solaris
1 Replies
9. AIX
How to get the other user history file. I would like to check the commands issues from my teammate. (1 Reply)
Discussion started by: Mariappan.m
1 Replies
10. Red Hat
Hi,
I would like to know commands which i have executed on terminal should not be present in the history.How can i approch please help me.
Regards,
Mastan (1 Reply)
Discussion started by: mastansaheb
1 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)