You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
[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.
The text was updated successfully, but these errors were encountered: