Support Procedures for Informatics.

This page documents major tasks performed by the Support Staff.
SupportTips documents various troubleshooting and helpful tips.

The Support FAQ gives help for staff and students of Informatics.

  1. Account Management
  2. Mail
  3. Web
  4. Restores and Backups
  5. Linux
  6. Windows
  7. RT
  8. Printing
  9. CVS and SVN Repositories
  10. Misc

Account Management

Quotas .

Quotas are 1Gb for all undergrads and Msc Students, 5Gbs for Phd students.

Please do not increase a student quota just because they have run out of space. They should be encouraged to login at a text login and delete files.

Fourth year ugrads and Msc students can have their quotas increased only for their project but the request must be endorsed by their supervisor. Please don't give extra quota if there is not enough space on the partition to accomodate it.

The staff quota of 5Gbs is there as a notional limit to help with housekeeping and disk management. It can be increased at any time. Again, make sure there is enough room on the partition.

Setting a quota.

NEW Account Management Documentation - prometheus.

Discussion notes regarding the main points are on this wikipage . More detailed documentation on Prometheus is available here .

Useful commands (to be run as 'asu' only on machines with tools installed) are:

The roles and the getrolemembers commands have been replaced by: prometheusroles and prometheusrolemembers both of which can be found in: /afs/

The old Account Management Documentation is still available here, which contain info about policy and high level procedures.

Creating an Account.

In order to create an account there has to be a database entry with a UUN. The UUNs are obtained by the admin staff.
Computing staff should not create database entries.

October 2010

Account creation is now an automatic process. As it is driven from the School Database is it is even more important that the db entry is correct.

Email is sent out twice a day to the support team with the list of accounts that have been created but which have not yet had their initial password printed out. Accounts will not appear on this list until the start date in the database.

When we receive a request for an account, the following needs to be done:

Mail Accounts.

From October 2007 all new staff will use Staffmail. Most visitors will not get mail accounts and should have supplied one to the admin staff for their database entry. See this services unit note on visitor email.

Mail accounts will be of the form:-
Users can still advertise their email address as but it will be automatically forwarded to their staffmail account. Until there is a script or some automatic method of creating the forwarding it should be done in the following way:-

On nutty as root:-

cd /opt/sendmail
co -l aliases-staffmail
edit aliases-staffmail
ci -u aliases-staffmail

The user should be subscribed to sys-announce and seminars. On as mailman do:

/var/mailman/bin/add_members -r - sys-announce

enter the email address(es) and Ctrl-D to finish.  Repeat for seminars.

More info on using staffmail is available here.

Admin Accounts.

Some info on how to grant access to shared areas and staff only web pages is available here

Changing a Username.

This happens when when there is a change of status eg student to staff. A new UUN is obtained from IDMS by the admin staff and the new contract details entered in the database.
It is preferable if the UUN entry in the database is not changed until the account is ready to be changed.
The user should be logged out when this happens. The following needs to be done.

AFS Username change but keeping the same UID

Most of the steps are the same as Changing a Username, except that the user volume name and PTS database entry needs to be updated with the new uun. The example below is for changing a username from kr to kreid5.

Changing a UID.

The following guide explains how to change an incorrect uid number of a current Informatics staff member to match their correct University uid. The user should be logged out when this happens. The following needs to be done.

Moving AFS Home Directories.

Full documentation is available here.


vos exam user.lmb

vos remove -verbose sphinx /vicepx user.lmb.readonly
vos remove -verbose phoenix /vicepx user.lmb.readonly

vos move -verbose user.lmb sphinx /vicepx sphinx /vicepxx
vos backup -verbose user.lmb

vos addsite -verbose sphinx /vicepxx user.lmb
vos addsite -verbose phoenix /vicepxx user.lmb

vos release -verbose user.lmb

This can be done without the need for the user to log out.

Removing AFS Home Directories.

Full documentation is available here.

Deleting and Archiving Accounts.

Instructions for archiving and deleting accounts are available.

Moving NFS users to AFS.

To check how many users on a particular partition type:
/usr/sbin/vos listvldb -server phoenix -part viceph | grep user
Partitions are 50GB so there should be a maximum of 10 users per partition. (On some there will be less since some users have a quota of more than 5GB - check the progress table on the Services wiki).

1. Run the create_afsuser command (as if for a new user, as per Roger's notes.)

2. rsync the files. First of all find the machine that the nfs directory is on. Then, on that machine:

qxprof rsync.gentry_allow
This gives a list of machines that you'll be able to rsync from. On one of those machines, as yourself, do the 'asu' bit and then 'nsu' (if you don't 'nsu', then files will be owned by your admin principal!). After that, do:
rsync -avz <nfs-server-name>::<home_partition>/<username>/ <afs-path-name>
rsync -avz phoenix::ptn006/mmarina/ /afs/
Note: remember the trailing '/' at the end of the nfs argument. Missing this out would create an extra mmarina directory!

3. Update ldap

/usr/sbin/update_user -afsdir /afs/ mmarina
When you disable an account by renaming the home directory eg lmb to this triggers a complete backup. This causes the backups to be bigger than they need be. The solution is to create a .nsr file in the top level of the home directory. Please remember to remove it if you enable the account again. The .nsr file needs to contain
+skip: *

4. Check the afs home directory for links created during the move which point to platspec/DotFiles. Delete these links (especially the ones relating to gnome config as they will be broken and produce a grey screen when user logs on).

It's also recommended to compare quota usage before and after the move as some types of compressed directories can unpack during rsync.

Editing Admin Principals.

Run /usr/kerberos/sbin/kadmin This produces:-
Authenticating as principal lmb/admin@INF.ED.AC.UK with password.
Enter password:
Typing ? at the prompt will give a list of commands.

To change an existing user's password:-
kadmin: cpw lmb
Enter password for principal "lmb":
Re-enter password for principal "lmb":
Password for "lmb@INF.ED.AC.UK" changed.
kadmin: cpw lmb/admin
Enter password for principal "lmb/admin":
Re-enter password for principal "lmb/admin":
Password for "lmb/admin@INF.ED.AC.UK" changed.

To add a new user password:-
Authenticating as principal rwb/admin@INF.ED.AC.UK with password.
Password for rwb/admin@INF.ED.AC.UK:
kadmin: add_principal newuser
Enter password for principal newuser:
Re-enter password for principal newuser:
kadmin: add_principal newuser/admin
Enter password for principal newuser/admin:
Re-enter password for principal newuser/admin:

AFS Documentation.

General AFS Documentation for Users, COs and CSOs is available here, which includes basic AFS admin documentation for COs and CSOs.

Accounts on the PostgreSQL Service.

Documentation is available here.

Setting up a client to use account management tools

In the Research and Teaching Unit's documentation page: available here.

Creating missing roles files.

When new taught courses are created, students who enrol on those courses will get a primary role in LDAP of the form module-<new-course-code>. However it is usually the case that the role record has not yet been created and this is reported as an error by the buildcaps script and sent by cron to root on the master ldap server. A similar thing happens (although it is far rarer) if new degrees or classes are created; the missing degree-<new-degree-code> or class-<new-class-code> need to be created.

The root mail for the ldap master server (in the shared IMAP folder sysman/rootmail) should be checked every few days for mail from cron with output from the command /usr/bin/k5start -f /etc/krb5.keytab ldaptrigger/ /usr/bin/buildcaps. Error messages will detail any missing (i.e. undefined) roles. Any missing primary roles should be created so that they are similar to existing roles of the same type. If the missing role is one of a type that you don't recognise then check to see whether it is a secondary role and if it is then don't create the missing role since it might be an erroneously added secondary role.

You can check which roles exist of type foo by running the command:

ldapsearch cn=foo* -b "ou=Roles,dc=inf,dc=ed,dc=ac,dc=uk" cn

To create a missing role, for example the course role module-caa, use rfe with a template taken from an existing course role such as module-ad, execute the command:

rfe -n -t roles/module-ad roles/module-caa

and edit the new roles file to change the course name of the template, ad in this example, to the name of the new course, caa in this example. References to any other roles within the template need to be edited accordingly.

Giving access to submissions directory.

Non-staff who require access (Teaching Assistants) should be given the secondary role submit. Documentation on using practical submission system is here: Practical Submission Guide

Giving access to ITO exam preparation machines.

Non-staff who require access (Teaching Assistants) should be given the secondary role examprep. This gives them the crucial capability "login/staff/examprep"

Giving access to Beowulf cluster.

Give the user the secondary role beowulfuser. Make a directory for the user on illustrious:/gpfs/home

Once the role has propagated, check they appear in ValidUsers on illustrious using qmon tool. Usually you will have to push this, as root with this command:

qconf -au <username> validusers

Killing Jobs on Beowulf Cluster.

First log onto illustrious,run qmon and kill the jobs (you may have to force them).


Creating a Mailing List.

In the services unit's ( former mail team) documentation page: available here.

Mailing Lists and Aliases.

Official documentation available here.

Sharing Mail Folders.

When using Staffmail it is possible to grant access to some of your mail folders to other users. It appears under "Other Users".
See the IS documentation here.

Informatics Mail has the facility to let a group of users read the mail in a shared mail account. The instructions for setting these up are available on the services-unit's documentation at: However, the services unit would prefer to continue to set these up themselves. Once this is set up it appears under "#shared".

Forwarding mail for staff after they leave.

IS policy is published here.

The request should come from the School and go to

Please note the following taken from the IS policy page:

This refers to mail sent to @ed addresses.


How do I publish on the Informatics Web Server?

The Services Unit notes are available here.

User Documentation is available here.

A publishing account is required. The application form is available here.

This form creates an RT ticket in the support queue. Check that the request is from a staff member or Teaching Assistant.

Giving Access to the Teaching Pages.

To view password protected pages such as
Ask the user to run ~neilb/bin/share/genwebsalt and type a password of choice. The instructions tell them to send encryption to, which generates an RT ticket in services queue. You could also ask them to put it in support ticket if you want to process it yourself.

Add the user to $CVSROOT/conf/access/passwd.staff (via CVS) after checking that they are indeed staff and that they have provided their dice UUN.

How do I publish my own web pages and CGI scripts?

Everything you ever wanted to know about publishing but were afraid to ask is available here.

Altering User Quota for Homepage

This is set in the quotas file as for homedir quotas. Make sure there is only one entry per user.
On run om quotas run

Creating a new Wiki Web.

We should no longer create wikis on unless the requestor needs something that the IS wiki service does not cover (which should be rare).

They should be directed to: IS wiki service.

If they have to have an Informatics wiki then they should be directed to:

especially the notes at:

Adding new wiki is a web based operation at Managing Webs.

Under Adding a New Wiki Web, fill in the name, description and Use to fields. Click Create New Web. The new web will be available at:[MyNewWeb]/WebHome.

To create a new group (optional) for access control go to TWikiGroups . Enter the new Group name and click add. You will automatically be the only member of that group, so you will need to set it to the requestor's wiki name instead.
To change the name, go to the new group page at[MyNewGroup]. Click Edit at the top left of the page. Set GROUP = Main.[RequestorsName].
You can still do this even if they have not registered yet at: TWikiRegistration

All users will need to register, and the requestor will be able to add people to the group. If the requestor wants to restrict access to the wiki web, then edit the webpreferences accordingly. An example of a very restricted web, so that non-members of the group cannot even view the pages (except we can as administrators) is PASTA.

Creating AFS group web space.

We have a number of URL options e.g.,,

To create a URL such as

  1. Decide where the group space should be mounted in the filesystem, e.g /afs/ or under workshop, conference etc. Create the space and backup volumes as per instructions at
  2. Create a subdir called 'html' in this group space, and set ownership so that this will match the ownership of the symlink you will shortly be creating on the web server.
    [gecko]joxley/admin: chown root:root /afs/
    Set the acl's so that the web server has list access to the top level, then read and list for the html subdir
    [gecko]joxley/admin: fs setacl /afs/ system:groupwebserver l
    [gecko]joxley/admin: fs setacl /afs/ system:groupwebserver rl
  3. Create symlink on (currently toaster) in one of the subdirs under /disk/data/httpd/ depending on what you want the URL to be. Note that conferences and workshops are plural here whereas the afs filespace volumes are singular!
    [toaster]root: cd /disk/data/httpd/groups
    [toaster]root: ln -s /afs/ euphoria

Restores and Backups

Where do I find the Mirror Backups?

All partitions are mirrored nightly and are available to nfs users as /yesterday/home/username
There is a script available which tells you where a particular partition is mirrored. It is called mirrorgrep and there is a copy in /group/support/support-team/
The mirror partitions can be accessed at:- ls /partition/rmirrorXX

AFS users have a directory in their homedirectory called Yesterday.

Restores from Networker

The nwrecover program can only be run on a SUN machine. To be able to run X you need to have an entry in the machine's /etc/passwd file, and have a dummy homedir created under /disk/home/

Restores from TIBS

A full working example is available here.

Self Managed Backups

Instructions available for Self Managed Backups .


Moving machine's wire without re-installing

  1. Edit the profile, adding (just above the mac address) the line
    !network.ipaddr_eth0 mSET(DHCP)
    at the same time change the live wire header to the new wire.
  2. Check that the resource has reached the machine by doing
    qxprof network.ipaddr_eth0
  3. Change the IP address in dns/inf and wait for it to ship to machine by doing
    nslookup machine name
  4. Connect the machine to the new wire.
  5. Reboot
  6. Remove the line inserted at step 1 from the profile.
  7. Steps 1 - 3 should be carried out on the original wire, steps 4 to 6 on the new wire.

Setting Up Shared Filespace on NFS..

Shared areas are for groups of people to have access to the same files. This can be for 
teaching purposes, collaborative working or arranging a conference. It depends on the
nature of usage as to how restrictive access needs to be. You can set up a shared area
without setting up a new group. eg /group/support/support-team is a shared area for
support for which the group is sysmans.

1. Choose the Group Name.

The name is usually the name of the project or conference or teaching module or
similar. Have a look in the groups file for inspiration. Throughout this example
the group is called cs3 and the GID is 10101.

2. Create the group name to GID mapping: rfe groups and add a line, eg. "cs3 10101".
This associates the name of the group with its group identity number
You should all now be able to "rfe amdmap/group" to add things to the /group hierarchy.
The format of the file is explained in the comment at the top. Please
be careful! Ask for help if you're unsure...

3. On a fileserver create the group directory on some partition somewhere, it will then
be visible from a DICE machine as, eg: /amd/partition/ptnxxx/cs3
There is a file in the support area called "partitions" which lists (not definitively)
what each partition is used for. On the fileserver you would also need
to "chown root:10101 cs3" and set the directory so that it is group writeable:
chmod g=rwxs cs3 "g=rwxs" means that any new files created in that directory inherit
the same group, and are group readable and writeable. You have to use the numeric GID
here unless unless the group already exists.

4. Next you need to either add the group membership as a capability of an existing
role or create a new role. Which you do rather depends on the nature of the group
(and keeping in mind the 7 groups per user maximum). Example of using an existing role:
rfe roles/staff and add a line "group/cs3" to add that group to all staff. Example of
creating a new role: rfe -n roles/cs3 and add a line "group/cs3" (and thats all you need
in it). You then need to add this new cs3 role to each person that you want to be a member
of the group. You do this using the AMT stuff, something like:
update_user lmb -second +cs3 to give Lindsey that role (consequently making her a member
of the group). The '+' means add the role, note you can also use an abbreviated version
of the option to save some typing. Test by giving yourself the role and running
'om ldap kick' on your machine. Then run 'sterm machine_name' and then 'id' to check
you have the new group. If it hasn't appeared yet, run 'newgrp group_name' to force it
through. If 'id' now shows the new group, you should be able to write a file into the new
group area without the 'permission denied' error. Then run "om ldap kick" on a client
machine you want to try it all out on.

You should then be able to list the cs3 group
timc : people staff cs3
then try, eg.
defiant[timc] cd /group/whatever/cs3
defiant[timc] touch wibble
defiant[timc] ls
defiant[timc] rm wibble
Note that shared filespace for "all-staff" is already setup in the sense that the group
exists and staff are already a member of that group. All you would need to do would be to
create a directory on a fileserver group writeable by the DICE staff GID (10010).

Setting Up Shared Filespace on AFS.

Instructions are available here.

Creating New Unix Groups and Membership

To create a new Unix group, name mapping and setup membership under DICE follow the procedure below.
  1. Create the group name and gid mapping with rfe groups. The syntax should be clear enough from the existing entries and is documented at the start of the file.
  2. Add the group capability to an existing role and all accounts with that role will then get membership of the group. So, for example, use rfe roles/staff and add a single line group/GROUPNAME to make the group membership a capability of the staff role (the syntax must be group/GROUPNAME where GROUPNAME is the name of the group for the GID mapping as defined above for this to work correctly). You may prefer to create a new role for the group, particularly if it will only have a few members and the group is not something that is naturally part of the authorization set of an existing role. In this case use rfe -n roles/GROUPNAME to create a new role and put a single line in the file as above.
  3. Where the role containing the group membership capability is not a primary role or a role that the accounts needing membership will already have by default you will need to add the role to individual accounts which are to be members of the group so they get that capability. Do this using AMT, for example, update_user jbloggs -second +ROLENAME where ROLENAME is the role containing the group membership capability created above.
  4. Finally, because LDAP triggers are not functioning yet, run buildcaps to create and/or update the entries in the Capabilities map, the Netgroup map and also the Groups map. Note that to avoid getting an error back when you run buildcaps you need to ensure that the group has a correlating name/gid mapping first (that is,you cannot create the capability group/wibble with any members until wibble has a GID defined by using rfe groups).
  5. After LDAP propagation to the clients the group and membership setup is now complete.

Forcing LDAP Client Replication

See Automatic and Forced LDAP Replication.

Installing Crossover Office

Instructions are available here.

Creating and Expanding Partitions

Instructions are available here.
Please do not expand partitions unless absolutely necessary. The disk usage on full partitions should be reduced before partitions are expanded.

DIY Dice.

Documentation available at:-
Infrastructure Support for a DIY DICE Machine (notes for COs/CSOs)
How to Install a DIY DICE Machine. User Instruction
A few more details here: General Management of a DIY DICE machine
DIY DICE Home Page

Creating a Subversion Repository.

Instructions are available here.

Conference Kiosk mode

To turn a machine into a conference kiosk, simply add this header and reboot:
#include <dice/options/conf-kiosk.h>

Adding a machine to condor pool.

Notes are on rat-unit page: Informatics Condor Pools

Going back to a previous version of an LCFG

The backout via RCS needs to be done on the rfe server (note that all actions are as root):

tobermory# cd /var/rfedata/lcfg/profiles

- and file locked:
tobermory# co -l lessard
RCS/lessard,v --> lessard
revision 1.69 (locked)

- you can check which version you want to revert to with:
tobermory# co -p -r1.66 lessard
RCS/lessard,v  -->  standard output
revision 1.66
/* lessard */
/* End of file */
- and when you know which one you want, overwrite the existing version:
tobermory# co -p -r1.66 lessard > lessard
RCS/lessard,v  -->  standard output
revision 1.66
- and check it back in:
tobermory# ci -u  lessard
RCS/lessard,v  <--  lessard
new revision: 1.70; previous revision: 1.69
enter log message, terminated with single '.' or end of file:
>> reverted to 1.66 (recovered fstab info)
>> .

Server Room Cluster Machines

Instructions for setting up and removing a machine from the cluster.

Instructions for maintaining the cluster.

Remember: The cluster machines are SL5 and must be reinstalled with F13 before reuse and the comment "Server Room Cluster" removed from the inventory


Setting up an Admin PC.

Instructions are available here to install a machine from an image. 
Before May 2005
These instructions are no longer valid but contain some useful info.  They will disappear when the info is moved.

After May 2005
Instructions for installing MDP machines are available here.  These instructions are a work in progress.

Registering someone for the Samba server.

Here's what to do. And here's the user-orientated Samba information.

Setting up Printing on a Windows PC

Instructions available here.

Instructions for printing under Windows XP

Adding a GPO to an MDP machine

Check before installing new software that, if a licence is required, it has been purchased. To add a GPO to a user's MDP machine, log in to a support office MDP machine.

Some MS Outlook Tips.

The important data is held in .pst files. This includes Contacts and Tasks. Some info on how to manage these files explained is here.

Personal Folders should be configured to be located in the user's home directory. By default they are in:
C:\Documents and Settings\uun\Local Settings\Application Data\Microsoft\Outlook. This is not backed up as Local Settings are not copied back to the IS profile server.

Central Samba Service - filespace for groups.

We will likely be migrating group space from admin.smb to IS Central Services samba server.

Group InfCom have now moved to central samba from afs and it seems to have gone well. A request was made via for 20GB and list of users provided to them. Below is their reply:

As requested have created a shared folder

Security is controlled by AD group "Scieng1 InfCom Users"

Below links show how to map network drives in Windows and Macs for
non-managed machines:

Data is backed up in this area to Volume Shadow copy twice a day (05:00
and 12:00) and can be restored back from upto a week. 

The MDP users were able to successfully map the drive, and copied and pasted their existing data over themselves.

However, from a laptop on an AT dhcp wire, the drive could not be mapped until a firewall hole was opened. The laptop needed a static IP registered, profile created to include the ipfilter.h header, and the hostname added to ipfilter.h in the same place as the AT MDP machines. Users would need to use Uni VPN to access the drive from home.


The RT Supremo.

The job of the Supremo has mostly disappeared. However, the job of monitoring the tickets is now the responsibility of the CSOs on duty in the Support Offices. Others may monitor the queue and take tickets in an ad hoc manner.

The job of the Duty CSOs is to make sure that all tickets get attention. The goal is to respond in some way to every ticket within a day. Tickets marked URGENT need to be assessed quickly according to the guidelines detailed the the RT Best Practice document available here.

Categorising Tickets.

All tickets should be categorised. There is no need to try to put something in every box but some degree of categorisation makes it easier to search old tickets and to produce meaningful statistics.



A comprehensive guide to printing under DICE is available here.

Status Check using CUPS Web Interface

The web page is available here.

On this web page you can check the CUPS queue for stuck jobs if you click on the printername. You can't cancel a job from this interface, so if the printer is not running (e.g. showing red):

on as root run /usr/sbin/cupsdisable < printername >

Cancel the offending job(s)

lprm < jobNo >


Further CUPS documentation can be found here: CUPS Wiki page

Status Check using Printer Web Interface

Log on to a print server and run a browser. Not the one you normally use or it will spawn a new window, which is not what you want. Browse to eg: You can examine and change the printer settings.

To find jobs in the print queue: login to the print server, become root and look for the df* files in /var/spool/lpd/queuename.

Determine IP address of selfmanaged machine being printed from

Until kerberised printing has been set up in Forum, we can't determine real user/UUN from a print job submitted from a selfmanaged machine/laptop as we only see the name of their local account. We can establish which IP address they were connected to meaning we can then determine their location via netmon.

on infcups as root, grep for their 'Name' of file, 'User' or jobID in the following file:


which shows the following info, one line per page printed:

if213m0 joxley 374683 [22/Nov/2011:14:32:11 +0000] 1 1 -

PCOUNTER: How to credit a student with more printing quota, and how to check print job and deposit history

The reports are slow to generate, and apparently it may be quicker to grep through the raw log files under \\pds\pcounter\data.

There is also a full pcounter manual available.

CVS and SVN Repositories

Creation of CVS repositories

See for details on how to create a repository. Note that the final decision on whether or not a repository should be created (in cases where this is not already clear) should still be the responsibility of the Services Unit.

Creation of SVN (subversion) repositories

See for details. As above, the final decision on whether a repository should be created remains with the Services Unit.

Coltex (Collaborative LaTeX)

Coltex (Collaborative LaTeX) is a system allowing multiple people to share and edit a common LaTeX document.

Staff by default have permissions to create new coltex repositories. To grant a PhD student permission just give them the 'coltex' secondary role. Other students should require approval by their supervisor.


Maintaining the School Database for Admin Users

Documentation is available describing data entry into the old database and the the new database. There is also documation describing the features of the new database.

Maintaining the School Inventory

The School Inventory should be maintained from the command line using the commands invedit and invquery.

However, direct access to the inventory through the School Database is needed to enter details of some machines. The Database is available at

Choose the Legacy Computing tab and the necessary tables will appear. The appearance is similar to the old database interface, in that, all the same fields appear and it work in a similar way. All Dice machines have their inventory entry made automatically. Unfortunately, laptops and self-managed machines have to have their entries in the database created by hand unless they have a dns entry. Even then there can be problems.

Here is the procedure for entering such data. It should be done in this order otherwise strange things happen. Even if you follow the procedure carefully, it can still go horribly wrong. Contact Lindsey with any questions.

vboxuser group for usb access within virtualbox

By default, users are unable to access their usb devices from within a virtual machine on dice. They will see the following message "VirtualBox is not currently allowed to access USB devices. You can change this by adding your user to the 'vboxusers' group."

Support can enable this by adding the following to the machine lcfg profile: !auth.grpent_vboxusers mCONCAT(:<%sysinfo.allocated%>)

Home : Systems : support 

Informatics Forum, 10 Crichton Street, Edinburgh, EH8 9AB, Scotland, UK
Tel: +44 131 651 5661, Fax: +44 131 651 1426, E-mail:
Please contact our webadmin with any comments or corrections. Logging and Cookies
Unless explicitly stated otherwise, all material is copyright © The University of Edinburgh