Update to the "AMGH HOW-TO" guide

I have added a section to the guide which describes why you probably don't want to create an AMGH script using the SRDS registration database, and some tips if you should decide to do this anyway :). It appears to be a common request.
In the spirit of a proper blog (which this really isn't), here's the new text in case somebody would like to comment:


Why not write an AMGH script utilizing information in the SRDS token registration database?


Initially this may seem attractive but keep in mind that AMGH is intended to work across FOGs, so you really ought to use a single, consistent database which can be shared across FOGs and is not subject to FOG-local typos or errors. Such errors can create inconsistent and hard to diagnose behavior.

If you do go this route, do not be tempted to use the "-c" option to utuser. Although it will restrict the output only to relevant tokens it will have an undesirable performance impact since it involves the Authentication Manager (utauthd) at what can be a critical time (e.g. as a server is first coming up many Sun Rays may be connecting to utauthd simultaneously and creating sessions, all going into the greeter at once so invoking AMGH). "utuser -l" generates more output but does not involve utauthd so will actually scale better in such scenarios.

Comments:

Post a Comment:
Comments are closed for this entry.
About

bobd

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
Bookmarks