Paradyn Group Administrivia

Disk usage

• Check current disk usage: afsdf paradyn
• Check detailed disk usage: afsdf -V paradyn

New staff accounts

• Ask lab to open new account (if necessary) [determines user identifier] (e.g., for jdoe)
  • Specify a lab-supported Unix workstation as host for mail delivery
    (typically user's desktop for UW-Madison staff/students, an x86-Solaris machine for U.Maryland, and pretty much anything for anyone else (typically basil))
• Ask lab to create/mount a new volume in development area with appropriate permissions set for new user:
  • /p/paradyn/development/jdoe
  • Development volumes are typically initially 300MB to 500MB
  • Check AFS access permissions: fs listacl
  • Check AFS quota: fs listquota
• Ask lab to provide new user access to appropriate group machines
  • U.Maryland staff are typically only provided access to a single lab-supported workstation (generally type x86-solaris which they don't have in Maryland)
  • Typically exclude: asiago, cayenne, garlic, oregano, pepper, sage, thyme
  • eden.cs.wisc.edu (SGI O200, mips-irix) is group-maintained, not by the lab
• Add name to mailing list(s)
  • paradyn-staff = paradyn-uw + paradyn-md + paradyn-other
  • Files are located in /p/paradyn/public
  • Edit the appropriate file to add the new account name (for either UW-Madison staff, U.Maryland staff or others).
  • paradyn-obsolete contains former staff members
• Add name to AFS group paradyn:staff
  • list current group membership: pts membership paradyn:staff
  • add new user to group: pts adduser -group paradyn:staff -user jdoe
• Inform new user about:
  • their development area: /p/paradyn/development/jdoe
  • group machines they may have access to
  • group books they may have access to

URL: file:/p/paradyn/public/html/internal/GroupAdmin.html
Last update: $Date: 2006/2/20 13:26:39 $