User Tools

Site Tools


build:users

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
build:users [2007/06/13 15:45]
206.197.251.70
build:users [2010/09/23 18:00]
SLUUG Administration
Line 2: Line 2:
  
  
- +===== Adding Users - Debian ​=====
- +
- +
- +
- +
-===== Adding Users =====+
  
 There are 2 ways to add a user: ''​useradd'',​ and ''​adduser''​. With the first, you specify the username and all the settings on the command-line. The second walks you through the process, asking you all the necessary questions. There are 2 ways to add a user: ''​useradd'',​ and ''​adduser''​. With the first, you specify the username and all the settings on the command-line. The second walks you through the process, asking you all the necessary questions.
Line 13: 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 -s /bin/mysh -c 'John Doe' johndoe+useradd -m -u 10999 -g useracct ​-G bronze ​-s /bin/bash -c 'John Doe' johndoe
 </​code>​ </​code>​
  
Line 23: Line 18:
   * Account majordomo is only defined on bud.   * Account majordomo is only defined on bud.
  
-===== Groups =====+===== Groups ​- Debian ​=====
  
 These groups seem to be important in Debian: These groups seem to be important in Debian:
Line 44: 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
   * "​administrative"​ accounts, which are accounts used for SLUUG business, not individual use   * "​administrative"​ accounts, which are accounts used for SLUUG business, not individual use
  
-===== Adding Groups =====+===== Adding Groups ​- Debian ​=====
  
 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 69: 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 75: 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 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 133: 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 229: Line 237:
  
 Accounts and groups will be taken from michelob since it is the primary user system, though the main difference between michelob and dark is some user passwords and minor details. ​ The same user accounts are on both. Accounts and groups will be taken from michelob since it is the primary user system, though the main difference between michelob and dark is some user passwords and minor details. ​ The same user accounts are on both.
 +
 +====== Solaris ======
 +
 +===== Adding a new user =====
 +
 +Coordinate account name, UID, GID, etc. with other systems as detailed [[#Adding Users|above in Adding Users]].
 +
 +Create the personal group if that is being used.  For that, the GID is the same as the UID.
 +
 +<​code>​
 +groupadd \
 +    -g GID \
 +    ACCOUNT_NAME
 +</​code>​
 +
 +Create the account.
 +
 +<​code>​
 +useradd \
 +    -u UID \
 +    -g GID \
 +    -c "GECOS USER NAME" \
 +    -s /​PATH/​TO/​SHELL \
 +    -d /​export/​home/​ACCOUNT_NAME \
 +    -m \
 +    ACCOUNT_NAME
 +</​code>​
 +
 +Make the home directory accessible only by the user.
 +
 +<​code>​
 +chmod go= /​export/​home/​ACCOUNT_NAME
 +</​code>​
 +
 +Set the initial password, force a password change at the next login, check status.
 +
 +<​code>​
 +passwd ​   ACCOUNT_NAME
 +passwd -f ACCOUNT_NAME
 +passwd -s ACCOUNT_NAME
 +</​code>​
build/users.txt · Last modified: 2010/09/23 18:07 by SLUUG Administration