build:users
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
build:users [2006/10/31 02:38] 4.245.75.130 |
build:users [2008/03/11 12:51] 24.107.98.225 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Users ====== | ====== Users ====== | ||
| - | |||
| - | |||
| - | |||
| - | |||
| Line 12: | Line 8: | ||
| For ''useradd'', a command similar to the following should be used: | For ''useradd'', a command similar to the following should be used: | ||
| <code rootshell> | <code rootshell> | ||
| - | useradd -m -u 10999 -g useracct -c 'John Doe' johndoe | + | useradd -m -u 10999 -g useracct -G bronze -s /bin/bash -c 'John Doe' johndoe |
| </code> | </code> | ||
| - | To keep uids synched between the 2 (and possibly 4) systems, you must manually inspect /etc/passwd on each system to find the next available UID common to all systems. Then use this on the command to add the user on each system. Add users to all systems at the same time since it is easy to forget to do this later. All UID and GID numbers for accounts created must be over 10000 to avoid conflict with any predefined UID/GID numbers on future systems. Don't use group "users" since the GID changes from system to system, use "useracct". Group numbers not related to individual accounts should be in the range 11000 to 11999. | + | To keep uids synched between the 2 (and possibly 4) systems, you must manually inspect /etc/passwd on each system to find the next available UID common to all systems. Then use this command to add the user on each Linux system. Add users to all systems at the same time since it is easy to forget to do this later. Use the same shell and shell path on all systems. Use the same UID, GID, secondary groups, GECOS (-c) information, etc. All UID and GID numbers for accounts created must be over 10000 to avoid conflict with any predefined UID/GID numbers on future systems. Don't use group "users" since the GID changes from system to system, use "useracct". Group numbers not related to individual accounts should be in the range 11000 to 11999. |
| Conflicts and inconsistencies as of July 2006: | Conflicts and inconsistencies as of July 2006: | ||
| Line 21: | Line 17: | ||
| * The same UID/GID is used for different temporary installation accounts between the systems. | * The same UID/GID is used for different temporary installation accounts between the systems. | ||
| * Account majordomo is only defined on bud. | * Account majordomo is only defined on bud. | ||
| - | |||
| - | TODO: Default groups. | ||
| - | |||
| ===== Groups ===== | ===== Groups ===== | ||
| Line 46: | Line 39: | ||
| In addition, we've defined these groups (mainly grabbed from Michelob's /etc/group file): | In addition, we've defined these groups (mainly grabbed from Michelob's /etc/group file): | ||
| - | ^Group^Function| | + | ^Group^GID^Function| |
| - | |wheel|We've got it set up so these folks can sudo without a root password.| | + | |wheel||We've got it set up so these folks can sudo without a root password.| |
| - | |users|Default group that all users should belong to.| | + | |users||Default group that all users should belong to.| |
| - | |newslett|Not sure if it's used; only member is editor.| | + | |newslett||Not sure if it's used; only member is editor.| |
| - | |steercom|Ad-hoc list of Steering Committee attendees, who can access steercom directory on Michelob.| | + | |steercom||Ad-hoc list of Steering Committee attendees, who can access steercom directory on Michelob.| |
| - | |webhead|Users who have write access to our web sites.| | + | |webhead||Users who have write access to our web sites.| |
| - | |majordom|Used for mailing list management; ''lists'' account is included.| | + | |majordom||Used for mailing list management; ''lists'' account is included.| |
| + | |useracct|11025|Accounts for real live users, as opposed to system accounts, shared accounts, etc.| | ||
| + | |platinum|11111|Members who have paid for the Platinum membership level.| | ||
| + | |gold|11112|Members who have paid for the Gold membership level.| | ||
| + | |silver|11113|Members who have paid for the Silver membership level.| | ||
| + | |bronze|11114|Members who have paid for the Bronze membership level.| | ||
| TODO: Create groups for: | TODO: Create groups for: | ||
| - | * a group for each paid account level (eg. gold/silver) | ||
| * users who have paid up for the current year (paid2006, etc.) | * users who have paid up for the current year (paid2006, etc.) | ||
| + | * Since we're now renewing memberships year-round, this no longer makes sense. | ||
| + | * We should probably have accounts expire when the renewal is due. | ||
| + | * We should have the passwords expire every 90 days, at the least. | ||
| + | * Although we need to allow users to change their passwords on Bud before we do that. | ||
| * voting members, as defined by our articles of incorporation / by-laws | * voting members, as defined by our articles of incorporation / by-laws | ||
| + | * Doesn't make sense, since that's not used for anything except voting, and changes every year. | ||
| * officers | * officers | ||
| * board members | * board members | ||
| Line 65: | Line 67: | ||
| As with users, there are 2 ways to add a group: ''groupadd'', and ''addgroup''. | As with users, there are 2 ways to add a group: ''groupadd'', and ''addgroup''. | ||
| + | |||
| + | <code rootshell> | ||
| + | groupadd -g gid groupname | ||
| + | </code> | ||
| TODO: Adding users to groups. | TODO: Adding users to groups. | ||
| Line 71: | Line 77: | ||
| TODO: Adding sudoers. What groups should administrators be in? So far, it looks like ''wheel'' will suffice. | TODO: Adding sudoers. What groups should administrators be in? So far, it looks like ''wheel'' will suffice. | ||
| - | |||
| ===== Using a User Account ===== | ===== Using a User Account ===== | ||
| Line 77: | Line 82: | ||
| TODO: Add info about how they can change their settings. Especially things like chfn, chsh, .forward, .profile, .bashrc, passwd, etc. | TODO: Add info about how they can change their settings. Especially things like chfn, chsh, .forward, .profile, .bashrc, passwd, etc. | ||
| - | This should go on a a user documentation page, not a "build" page. | + | This should go on a [[../server_access|user documentation page]], not a "build" page. |
| ===== Migrating User Accounts ===== | ===== Migrating User Accounts ===== | ||
| Line 100: | Line 105: | ||
| * "webhead" on AIX at UID 600, GID 80 - On debian "www-data" is UID and GID 33. | * "webhead" on AIX at UID 600, GID 80 - On debian "www-data" is UID and GID 33. | ||
| * The home directory for www-data (/var/www) is not being used for the SLUUG web site, on bud it is being put in /home/web. | * The home directory for www-data (/var/www) is not being used for the SLUUG web site, on bud it is being put in /home/web. | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| ==== What to change as preparation for the move: ==== | ==== What to change as preparation for the move: ==== | ||
| Line 121: | Line 121: | ||
| === Software preparation on new systems: === | === Software preparation on new systems: === | ||
| - | * Install ksh93, tcsh, and csh using apt-get. Add sym links for path variations and add to /etc/shells. | + | * Install ksh93, tcsh, and csh using the procedure on the [[misc]] page. |
| - | <code> | + | |
| - | apt-get install ksh | + | |
| - | apt-get install tcsh | + | |
| - | apt-get install csh | + | |
| - | ln -s /bin/bash /bin/csh /bin/ksh /bin/sh /bin/tcsh /usr/local/bin | + | |
| - | ln -s /bin/bash /bin/csh /bin/ksh /bin/sh /bin/tcsh /usr/bin | + | |
| - | ln -s /usr/bin/perl /usr/local/bin | + | |
| - | ln -s /usr/bin/perl /bin | + | |
| - | </code> | + | |
| * Also install rsync for cross-system backups. Documented on the [[misc]] page. | * Also install rsync for cross-system backups. Documented on the [[misc]] page. | ||
| Line 148: | Line 140: | ||
| Edit /etc/group and /etc/gshadow. Move "useracct" just before "users". | Edit /etc/group and /etc/gshadow. Move "useracct" just before "users". | ||
| </code> | </code> | ||
| + | When tried 01/30/08 on the reloaded systems, unable to add the group with GID 4294967294 because the groupadd command failed with error message "invalid numeric argument '4294967294'". This worked before the systems were reloaded. | ||
| === User/UID changes on new systems: === | === User/UID changes on new systems: === | ||
| - | * Rename 6 installation accounts with the same name as an existing user account. Do not change UID or GID number. | + | * Rename 6 installation accounts with the same name as an existing user account. Do not change UID or GID number. For the reloaded systems, there are different accounts on each system, and the decision was to not rename them, but to not copy them from michelob and change the UID of the existing accounts. So this step was not done on the reloaded systems. |
| <code> | <code> | ||
| - Repeat for each account: | - Repeat for each account: | ||
| Line 205: | Line 198: | ||
| 2>&1 | tee "${work_base}"/filter_passwd.log | 2>&1 | tee "${work_base}"/filter_passwd.log | ||
| </code> | </code> | ||
| + | The code is documented on [[filter_passwd.pl]] and [[odm-comb.pl]]. | ||
| * Add to normal and shadow passwd files on bud and budlight. | * Add to normal and shadow passwd files on bud and budlight. | ||
| <code> | <code> | ||
build/users.txt · Last modified: 2010/09/23 18:07 by SLUUG Administration
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
