110 likes | 234 Vues
This guide outlines the process for renewing AFS tokens for users with active UMBC (AFS) accounts. It covers the different types of accounts, including how AFS accounts enable access to essential systems like gl.umbc.edu and umbc7.umbc.edu, while non-AFS accounts do not qualify for this renewal procedure. Steps for renewing tokens using UNIX commands such as `klog` or `kinit` are provided, along with troubleshooting tips for ensuring no unusual or runaway processes are affecting token expiration.
E N D
Preliminary Notes • Active UMBC (AFS) account exists for the user • AFS accounts include access to systems such as gl.umbc.edu and umbc7.umbc.edu • Non-AFS accounts include access to systems such as cs.umbc.edu and umbc2.umbc.edu (for which this procedure will NOT work!) • User has been logged on for 24+ hours
Tokens • An ID • Contains user’s time stamp • Contains user’s life time • Keeps time records for the duration of a login session • Expires after 24+ hours
When Tokens Expire… • To renew tokens: • At the UNIX command line prompt, type: • klog or kinit • Where: • klog - kernel error logging interface • kinit - kernel initiation • In this case, we will use kinit • User verification will be required via password
“Run-away” or Unusual Processes • Make sure that no “run-away” or unusual process exist • This may be resulting in the token expirations • To retrieve a list of running processes • Type the following at the UNIX command prompt: • ps -fu <username>
Purposes for Verifying Running Processes • To make sure a process has not been left running by mistake • To make sure no ‘unusual’ process exists • May suggest suspicious activity • Especially if user is logged in via ‘insecure’ TELNET!