Sysadmin:New Sysadmins: Difference between revisions
Jump to navigation
Jump to search
New page: There are quite a few areas to update when a new system administrator joins the content group (or someone leaves the content group, actually...). === Keys === The sysadmins get a copy of ... |
|||
| Line 14: | Line 14: | ||
There are a few (physical) machines that don't use NIS and need to have users added by hand: | There are a few (physical) machines that don't use NIS and need to have users added by hand: | ||
* [[Sysadmin:FourtyTwo|Forty-Two]] - if it's up and running by then | * [[Sysadmin:FourtyTwo|Forty-Two]] - if it's up and running by then | ||
* [[Sysadmin:Servers:Forty_one]] | * [[Sysadmin:Servers:Forty_one|Forty-One]] | ||
In NIS, users need to be added to the wheel group. | In NIS, users need to be added to the wheel group. | ||
Revision as of 21:07, 20 January 2009
There are quite a few areas to update when a new system administrator joins the content group (or someone leaves the content group, actually...).
Keys
The sysadmins get a copy of CA and CMP1. These need to be requested with a form and signed by the new sysadmin and by either Charlie or Kay.
Bookkeeping
Sysadmins should probably register for CS281: Applied Groups if they want this to show up on their transcript. They can either take the class for zero or one credit hour (pass/fail). This can't be done online since it requires instructor permission, but have Charlie sign the sheet.
E-mails
- The new admins need to be added to the CS-Admin mailing list.
- Nagios needs to be updated to include the users in e-mails sent out. This doesn't go to the mailing list in case the CS department's e-mail stack is part of the problem. Also there are sys admin alumns on the mailing list who don't need to know about servers going down on a daily basis.
Accounts/Permissions
There are a few (physical) machines that don't use NIS and need to have users added by hand:
In NIS, users need to be added to the wheel group.
Passwords
There are lots of them.