How to create multiple IDs with same UID in AIX ? How to change UID of IDs in AIX?

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
How to create multiple IDs with same UID in AIX ?
How to change UID of IDs in AIX ?
users aix uid
add a comment |Â
up vote
0
down vote
favorite
How to create multiple IDs with same UID in AIX ?
How to change UID of IDs in AIX ?
users aix uid
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
How to create multiple IDs with same UID in AIX ?
How to change UID of IDs in AIX ?
users aix uid
How to create multiple IDs with same UID in AIX ?
How to change UID of IDs in AIX ?
users aix uid
edited Jul 12 at 18:47
Jeff Schaller
30.8k846104
30.8k846104
asked Jul 12 at 18:39
Rahul Raj
32
32
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
You cannot.
The (eventual) mkuser command will not create IDs with the same UID. Quoting the mkuser man page:
Note
ID collision detection in the target registry is always enforced regardless of the dist_uniqid system attribute.
Using either smitty or the command-line will land you in the same situation.
As for changing a user's UID, you would use the chuser command or smitty (which then calls chuser), but it uses the same restriction as mkuser does:
However, when the ID is changed using the chuser command, ID collision checking is also controlled by the dist_uniqid attribute in the usw stanza of the /etc/security/login.cfg file. The behavior of ID collision control is the same as that described for the mkuser command.
For extra fun, check out the command that smitty runs during a User change (smitty chuser):
x()
if [ $# -ge 2 ]
then
for i in "$@"
do
spam="$spam "$i""
done
eval chuser $spam
fi
x id='1234' username
That code is... not good. Why not justchuser "$@"? Or does it rely onspamnot getting reset?
â Kusalananda
Jul 12 at 19:52
@K That structure is one that a lot of smitty menus use, so I suspect the author copy/pasted a different one and replaced the guts for thechuserflags, none of which need any special handling. The smitty menu generates that code based on user input in the menu. It does at least quote the data going into it (twice), but I was amused at the author's choice for the variable's name.
â Jeff Schaller
Jul 12 at 20:01
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
You cannot.
The (eventual) mkuser command will not create IDs with the same UID. Quoting the mkuser man page:
Note
ID collision detection in the target registry is always enforced regardless of the dist_uniqid system attribute.
Using either smitty or the command-line will land you in the same situation.
As for changing a user's UID, you would use the chuser command or smitty (which then calls chuser), but it uses the same restriction as mkuser does:
However, when the ID is changed using the chuser command, ID collision checking is also controlled by the dist_uniqid attribute in the usw stanza of the /etc/security/login.cfg file. The behavior of ID collision control is the same as that described for the mkuser command.
For extra fun, check out the command that smitty runs during a User change (smitty chuser):
x()
if [ $# -ge 2 ]
then
for i in "$@"
do
spam="$spam "$i""
done
eval chuser $spam
fi
x id='1234' username
That code is... not good. Why not justchuser "$@"? Or does it rely onspamnot getting reset?
â Kusalananda
Jul 12 at 19:52
@K That structure is one that a lot of smitty menus use, so I suspect the author copy/pasted a different one and replaced the guts for thechuserflags, none of which need any special handling. The smitty menu generates that code based on user input in the menu. It does at least quote the data going into it (twice), but I was amused at the author's choice for the variable's name.
â Jeff Schaller
Jul 12 at 20:01
add a comment |Â
up vote
1
down vote
You cannot.
The (eventual) mkuser command will not create IDs with the same UID. Quoting the mkuser man page:
Note
ID collision detection in the target registry is always enforced regardless of the dist_uniqid system attribute.
Using either smitty or the command-line will land you in the same situation.
As for changing a user's UID, you would use the chuser command or smitty (which then calls chuser), but it uses the same restriction as mkuser does:
However, when the ID is changed using the chuser command, ID collision checking is also controlled by the dist_uniqid attribute in the usw stanza of the /etc/security/login.cfg file. The behavior of ID collision control is the same as that described for the mkuser command.
For extra fun, check out the command that smitty runs during a User change (smitty chuser):
x()
if [ $# -ge 2 ]
then
for i in "$@"
do
spam="$spam "$i""
done
eval chuser $spam
fi
x id='1234' username
That code is... not good. Why not justchuser "$@"? Or does it rely onspamnot getting reset?
â Kusalananda
Jul 12 at 19:52
@K That structure is one that a lot of smitty menus use, so I suspect the author copy/pasted a different one and replaced the guts for thechuserflags, none of which need any special handling. The smitty menu generates that code based on user input in the menu. It does at least quote the data going into it (twice), but I was amused at the author's choice for the variable's name.
â Jeff Schaller
Jul 12 at 20:01
add a comment |Â
up vote
1
down vote
up vote
1
down vote
You cannot.
The (eventual) mkuser command will not create IDs with the same UID. Quoting the mkuser man page:
Note
ID collision detection in the target registry is always enforced regardless of the dist_uniqid system attribute.
Using either smitty or the command-line will land you in the same situation.
As for changing a user's UID, you would use the chuser command or smitty (which then calls chuser), but it uses the same restriction as mkuser does:
However, when the ID is changed using the chuser command, ID collision checking is also controlled by the dist_uniqid attribute in the usw stanza of the /etc/security/login.cfg file. The behavior of ID collision control is the same as that described for the mkuser command.
For extra fun, check out the command that smitty runs during a User change (smitty chuser):
x()
if [ $# -ge 2 ]
then
for i in "$@"
do
spam="$spam "$i""
done
eval chuser $spam
fi
x id='1234' username
You cannot.
The (eventual) mkuser command will not create IDs with the same UID. Quoting the mkuser man page:
Note
ID collision detection in the target registry is always enforced regardless of the dist_uniqid system attribute.
Using either smitty or the command-line will land you in the same situation.
As for changing a user's UID, you would use the chuser command or smitty (which then calls chuser), but it uses the same restriction as mkuser does:
However, when the ID is changed using the chuser command, ID collision checking is also controlled by the dist_uniqid attribute in the usw stanza of the /etc/security/login.cfg file. The behavior of ID collision control is the same as that described for the mkuser command.
For extra fun, check out the command that smitty runs during a User change (smitty chuser):
x()
if [ $# -ge 2 ]
then
for i in "$@"
do
spam="$spam "$i""
done
eval chuser $spam
fi
x id='1234' username
answered Jul 12 at 19:11
Jeff Schaller
30.8k846104
30.8k846104
That code is... not good. Why not justchuser "$@"? Or does it rely onspamnot getting reset?
â Kusalananda
Jul 12 at 19:52
@K That structure is one that a lot of smitty menus use, so I suspect the author copy/pasted a different one and replaced the guts for thechuserflags, none of which need any special handling. The smitty menu generates that code based on user input in the menu. It does at least quote the data going into it (twice), but I was amused at the author's choice for the variable's name.
â Jeff Schaller
Jul 12 at 20:01
add a comment |Â
That code is... not good. Why not justchuser "$@"? Or does it rely onspamnot getting reset?
â Kusalananda
Jul 12 at 19:52
@K That structure is one that a lot of smitty menus use, so I suspect the author copy/pasted a different one and replaced the guts for thechuserflags, none of which need any special handling. The smitty menu generates that code based on user input in the menu. It does at least quote the data going into it (twice), but I was amused at the author's choice for the variable's name.
â Jeff Schaller
Jul 12 at 20:01
That code is... not good. Why not just
chuser "$@"? Or does it rely on spam not getting reset?â Kusalananda
Jul 12 at 19:52
That code is... not good. Why not just
chuser "$@"? Or does it rely on spam not getting reset?â Kusalananda
Jul 12 at 19:52
@K That structure is one that a lot of smitty menus use, so I suspect the author copy/pasted a different one and replaced the guts for the
chuser flags, none of which need any special handling. The smitty menu generates that code based on user input in the menu. It does at least quote the data going into it (twice), but I was amused at the author's choice for the variable's name.â Jeff Schaller
Jul 12 at 20:01
@K That structure is one that a lot of smitty menus use, so I suspect the author copy/pasted a different one and replaced the guts for the
chuser flags, none of which need any special handling. The smitty menu generates that code based on user input in the menu. It does at least quote the data going into it (twice), but I was amused at the author's choice for the variable's name.â Jeff Schaller
Jul 12 at 20:01
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f454958%2fhow-to-create-multiple-ids-with-same-uid-in-aix-how-to-change-uid-of-ids-in-ai%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password