You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Aman Poonia (JIRA)" <ji...@apache.org> on 2017/09/21 09:25:00 UTC

[jira] [Created] (AMBARI-22016) changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user

Aman Poonia created AMBARI-22016:
------------------------------------

             Summary: changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user
                 Key: AMBARI-22016
                 URL: https://issues.apache.org/jira/browse/AMBARI-22016
             Project: Ambari
          Issue Type: Bug
          Components: stacks
    Affects Versions: 2.5.2
         Environment: Using Centos as the test bed
            Reporter: Aman Poonia
            Assignee: Aman Poonia
             Fix For: 2.6.0


changeToSecureUid.sh might collide with existing user if it is not a local user but a network managed user
Currently we are doing 

{code:java}
function find_available_uid() {
 for ((i=1001; i<=2000; i++))
 do
   grep -q $i /etc/passwd
   if [ "$?" -ne 0 ]
   then
    newUid=$i
    break
   fi
 done
}
{code}
This will only check local user. Network manged users are not directly present inside passwd file.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)