Run the sponsor_resources program to process the changes

IncludeSponsorResourcesAccountsClient

sponsor_resources takes the data under /software/accounts-master/data/sponsors and produces per-user requirements in per-machine(actually per-region) files under /software/accounts-master/data/resources. Along the way, it might detect errors in the changes you made. Fix any problems that are reported and keep rerunning sponsor_resources until all errors have gone away.

Here is an example of a "bad run":

@cscf[140]% sponsor_resources
Error: /software/accounts-master/data/sponsors/Terry line 63: Userid 'bjlafren'
 is not a standard userid
FYI:  78150(20697) computings, 1262(1180) printers, 300(0) aliases, 0(0) ppps
FYI:  1 error, 0 warnings, (0 notes)
FYI: expired sponsorship entries:  91 computings, 2 printers, 0 aliases, 0 ppps

In this case, we need to use the long version of the UWdir name (ie: "bjlafreniere")

This is an example of a "good run":

@cscf[143]% sponsor_resources
FYI:  78151(20697) computings, 1262(1180) printers, 300(0) aliases, 0(0) ppps
FYI:  0 errors, 0 warnings, (0 notes)
FYI: expired sponsorship entries:  91 computings, 2 printers, 0 aliases, 0 ppps

Run the userinfo program to verify your changes

Run the userinfo command before and after you make your changes to verify that its output reflects your intended changes. More details are here.

Run the accounts-client program

accounts-client {hostname, eg:core.cs} >& ~/hostname-date &

This will cause the desired changes to actually happen on the appropriate machine (hostname; what is described as "Computing:" in the sponsor file, which may in turn affect a region of machines). /etc/passwd and /etc/group file will be updated if necessary, as will system quota files, and home directories will be created for any newly-created users. The diagnostic output from the job will be written to the given filename in your home directory. eg:

accounts-client softbase.cs >& ~/softbase-20100208 &

If your changes will cause changes on multiple regions, you will need to run the command for each. eg:

accounts-client student.cs >& ~/student-20100208 &
accounts-client core.cs >& ~/core-20100208 &

If you run accounts-client with no name, all known regions are updated. eg:

accounts-client >& ~/ac-all-20100208 &

That can take a long time to finish.