Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sudo -u x -i doesn't work #2

Open
alanfgates opened this issue Jun 18, 2014 · 2 comments
Open

sudo -u x -i doesn't work #2

alanfgates opened this issue Jun 18, 2014 · 2 comments
Labels

Comments

@alanfgates
Copy link
Contributor

[vagrant@nn ~]$ sudo -u hive -i
This account is currently not available.

But:
[vagrant@nn ~]$ sudo -u hive bash
bash-4.1$ whoami
hive

Pretty minor, but it's still useful.

@alanfgates alanfgates added the bug label Jun 18, 2014
@omalley
Copy link
Contributor

omalley commented Jun 18, 2014

It is because hive doesn't have a shell defined. In particular, it looks like:
hive:x:493:493:Hive:/var/lib/hive:/sbin/nologin
I see the other service accounts have bash as their shell. In general, the user accounts should have /sbin/nologin as their shell since it is considered more secure. I suspect the difference is coming up because vagrant is creating the hive user and the hadoop rpms are creating the hdfs and yarn users.

@davidhoyle
Copy link

Okay, thanks very much for the additional info!

On Wed, Jun 18, 2014 at 6:26 PM, omalley [email protected] wrote:

It is because hive doesn't have a shell defined. In particular, it looks
like:
hive[image: ❌]493:493:Hive:/var/lib/hive:/sbin/nologin
I see the other service accounts have bash as their shell. In general, the
user accounts should have /sbin/nologin as their shell since it is
considered more secure. I suspect the difference is coming up because
vagrant is creating the hive user and the hadoop rpms are creating the hdfs
and yarn users.


Reply to this email directly or view it on GitHub
#2 (comment).

CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

@omalley omalley added bug and removed bug labels Jun 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants