Sponsored Content
Full Discussion: keep UIDs/GIDs consistent
Top Forums UNIX for Advanced & Expert Users keep UIDs/GIDs consistent Post 302295902 by robertngo on Monday 9th of March 2009 09:33:00 PM
Old 03-09-2009
the problem is the older informix server we are running does not support PAM authentication, is there any other to sync user account without using LDAP and NIS?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

about UIDs, very urgent

hello guys, well as i mentioned first i have a serious problem, i need your help. i have a hosting plan with linux, apache and php. i have a script (that have my UID=32256) inside my web site (in the panel folder -see below-) that creates new scripts (in the pages folder) (the new scripts... (1 Reply)
Discussion started by: mehdi
1 Replies

2. HP-UX

Valid ranges for uids for HP-UX

Hi , I am using adduser in hp-ux to create users in Hp-ux. i would like to know what are the valid values for uids and gids in hp-ux what are the rannges for the valid uids . How to check what are the used uids in Hp-ux . Thanks Narendra babu C (7 Replies)
Discussion started by: naren_chella
7 Replies

3. AIX

UIDs being overwritten immediately

We have a problem where we delete a user and their associated UID gets dumped back in the UID pool. The if we immediately create a another (new) user, AIX reuses the last UID, the one that was just released. This is causing a problem when reports are being generated because the new users name is... (2 Replies)
Discussion started by: xsys2000
2 Replies

4. Solaris

UIDs in /etc/passwd file

Hi all, I am bit confused about UIDs on my server where LDAP athentication happens. UIDs are generally in the range of 0-65534 for any Solaris OS version(correct if i am wrong). My server is running on Solaris 9. Below are user accounts available on my server. ... (10 Replies)
Discussion started by: vvpotugunta
10 Replies

5. Solaris

metadevice submirrors 0 and 1 not consistent

At a new job, I've inherited a handful of Solaris 10 SunFire V240 servers. I noticed that the metadevices are not consistent, in a way that I've not seen before.... internal mirrored disks: metadevice d60 has c1t0d0s6 as submirror 0 (d61) and c1t1d0s6 as submirror 1 (d62) metadevice... (1 Reply)
Discussion started by: Max Power
1 Replies

6. Shell Programming and Scripting

How to echo columns with consistent spacing?

for (.....) echo -e "$Name | $Age | $Sex\t|$Grade\t\t" done output: John |12 |Male |6th Jack |15 |Male |8th Zachary |15 |Male |9th I want the lines to line up...but it's out of line when the name is long (2 Replies)
Discussion started by: etranman1
2 Replies

7. Red Hat

pam_krb5 UID mapping (clashing UIDs)

Hi, I'm considering implementing pam_krb5 on RHEL 5.5 and Solaris 10, and I'm in an environment that has a number of legacy NIS domains. They've all been migrated into Active Directory, RFC2307, with the NIS maps that differed in each domain kept within its own container. However, users and... (0 Replies)
Discussion started by: cambridge
0 Replies

8. UNIX for Beginners Questions & Answers

Scripts dont give a consistent output..

I have at moment created a setup script that is capable of setting up a workspace for an kaldi enviroment. The script can be found here setup_base_file I guess you wouldn't not be able to run it, without having Kaldi installed, but since this question more relates to scripting, than the... (9 Replies)
Discussion started by: kidi
9 Replies

9. Homework & Coursework Questions

Display usernames and their UIDs

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Write a script that displays all usernames and their UIDs in the following fashion: name1 uid=999 name2... (2 Replies)
Discussion started by: baniel
2 Replies
adduser.conf(5) 						File Formats Manual						   adduser.conf(5)

NAME
/etc/adduser.conf - configuration file for adduser(8) and addgroup(8). DESCRIPTION
The file /etc/adduser.conf contains defaults for the programs adduser(8) , addgroup(8) , deluser(8) and delgroup(8). Each line holds a single value pair in the form option = value. Double or single quotes are allowed around the value, as is whitespace around the equals sign. Comment lines must have a hash sign (#) in the first column. The valid configuration options are: DSHELL The login shell to be used for all new users. Defaults to /bin/bash. DHOME The directory in which new home directories should be created. Defaults to /home. GROUPHOMES If this is set to yes, the home directories will be created as /home/[groupname]/user. Defaults to no. LETTERHOMES If this is set to yes, then the home directories created will have an extra directory inserted which is the first letter of the loginname. For example: /home/u/user. Defaults to no. SKEL The directory from which skeletal user configuration files should be copied. Defaults to /etc/skel. FIRST_SYSTEM_UID and LAST_SYSTEM_UID specify an inclusive range of UIDs from which system UIDs can be dynamically allocated. Default to 100 - 999. Please note that sys- tem software, such as the users allocated by the base-passwd package, may assume that UIDs less than 100 are unallocated. FIRST_UID and LAST_UID specify an inclusive range of UIDs from which normal user's UIDs can be dynamically allocated. Default to 1000 - 29999. FIRST_SYSTEM_GID and LAST_SYSTEM_GID specify an inclusive range of GIDs from which system GIDs can be dynamically allocated. Default to 100 - 999. FIRST_GID and LAST_GID specify an inclusive range of GIDs from which normal group's GIDs can be dynamically allocated. Default to 1000 - 29999. USERGROUPS If this is set to yes, then each created user will be given their own group to use. If this is no, then each created user will be placed in the group whose GID is USERS_GID (see below). The default is yes. USERS_GID If USERGROUPS is no, then USERS_GID is the GID given to all newly-created users. The default value is 100. DIR_MODE If set to a valid value (e.g. 0755 or 755), directories created will have the specified permissions as umask. Otherwise 0755 is used as default. SETGID_HOME If this is set to yes, then home directories for users with their own group ( USERGROUPS=yes ) will have the setgid bit set. This was the default setting for adduser versions << 3.13. Unfortunately it has some bad side effects, so we no longer do this per default. If you want it nevertheless you can still activate it here. QUOTAUSER If set to a nonempty value, new users will have quotas copied from that user. The default is empty. NAME_REGEX User and group names are checked against this regular expression. If the name doesn't match this regexp, user and group creation in adduser is refused unless --force-badname is set. With --force-badname set, only weak checks are performed. The default is the most conservative ^[a-z][-a-z0-9]*$. When --system is specified, NAME_REGEX_SYSTEM is used instead. NAME_REGEX_SYSTEM Names of system users are checked against this regular expression. If --system is supplied and the name doesn't match this regexp, user creation in adduser is refused unless --force-badname is set. With --force-badname set, only weak checks are performed. The default is as for the default NAME_REGEX but also allowing uppercase letters. SKEL_IGNORE_REGEX Files in /etc/skel/ are checked against this regex, and not copied to the newly created home directory if they match. This is by default set to the regular expression matching files left over from unmerged config files (dpkg-(old|new|dist)). ADD_EXTRA_GROUPS Setting this to something other than 0 (the default) will cause adduser to add newly created non-system users to the list of groups defined by EXTRA_GROUPS (below). EXTRA_GROUPS This is the list of groups that new non-system users will be added to. By default, this list is 'dialout cdrom floppy audio video plugdev users games' NOTES
VALID NAMES adduser and addgroup enforce conformity to IEEE Std 1003.1-2001, which allows only the following characters to appear in group and user names: letters, digits, underscores, periods, at signs (@) and dashes. The name may no start with a dash. The "$" sign is allowed at the end of usernames (to conform to samba). An additional check can be adjusted via the configuration parameter NAME_REGEX to enforce a local policy. FILES
/etc/adduser.conf SEE ALSO
adduser(8), addgroup(8), deluser(8), delgroup(8), deluser.conf(5) Debian GNU/Linux Version 3.112+nmu1ubuntu5 adduser.conf(5)
All times are GMT -4. The time now is 07:38 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy