Quote:
Originally Posted by willPower
lgdom handles the username -> UID / UID -> username and group -> GID / GID -> group translation for samba on the Snap server. It runs as a daemon and is active whether the server is in an Active Directory domain or a workgroup. Some other parts of GOS are dependent on the functionality of lgdom as well, such as authentication to the web interface.
If the server is in a workgroup, then lgdom looks at the passwd and group files and uses the data listed in there to map user/group names to UIDs/GIDs.
When the server is in a domain, lgdom generates IDs for each domain user and group. When winbindd pulls the domain objects from the DC, they don't arrive in any particular order, and the order changes every time the objects are reacquired from the DC. lgdom knows how to order the names based on the sequence number of the request provided by the DC during the object refresh. Each domain object is assigned a UID or GID, and these UIDs/GIDs are used to control both samba and NTFS ACLs. When the domain object cache created by winbindd isn't read properly by lgdom (this can be caused by TDB corruption, among other things), any part of the system that needs the object -> ID / ID -> object translation will fail (including the WebUI).
I'm speculating that Overland found a problem somewhere and had to release the SP1 to fix it.
|
I read this 3 times, now my head hurts...
Dyslexia is a bitch isn’t it?
I will Google for a diagram... he he he