Question & Answer
Question
I created /etc/security/mkuser.sys.custom per the IBM Documentation for mkuser.sys.
The shipped mkuser.sys file must not be customized directly. If a customized version is required, a new file /etc/security/mkuser.sys.custom must be created. The mkuser.sys program detects this new program and if it is present on the system, it runs it instead of the original mkuser.sys.
When I run mkuser, the command spawns many processes, and never returns. Why is the mkuser command in a loop?
Answer
If you copied /etc/security/mkuser.sys.custom from /etc/security/mkuser.sys, there is a line where the script executes the mkuser.sys.custom if it exists.
Comment, or delete this section, so the script does not invoke itself.
|
# vi /etc/security/mkuser.sys.custom # If a customer mkuser.sys.custom script exists
# then execute it instead and exit passing all arguments # and returning the return code from mkuser.sys.custom # if [ -x /etc/security/mkuser.sys.custom ]
then /etc/security/mkuser.sys.custom $* exit $? fi CHANGE: # if [ -x /etc/security/mkuser.sys.custom ]
# then # /etc/security/mkuser.sys.custom $* # exit $? # fi |
| SUPPORT |
|---|
|
If you require more assistance, use the following step-by-step instructions to contact IBM to open a case for software with an active and valid support contract. 1. Document (or collect screen captures of) all symptoms, errors, and messages related to your issue. 2. Capture any logs or data relevant to the situation. 3. Contact IBM to open a case: -For electronic support, see the IBM Support Community: 4. Provide a clear, concise description of the issue. - For more information, see: Working with IBM AIX Support: Describing the problem. 5. If the system is accessible, collect a system snap, and upload all of the details and data for your case. - For more information, see: Working with IBM AIX Support: Collecting snap data |
Related Information
Was this topic helpful?
Document Information
Modified date:
11 May 2021
UID
ibm16451611