Originally Posted by Max8 (Post 172515)

I have heard the term before but never asked.... what is "lgdom"?

Originally Posted by willPower (Post 172554)

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.

Originally Posted by Phoenix32 (Post 172509)

I asked Overland about this Service Pack and this is the reply...


I am sorry but at this time Overland Engineering have not yet posted the Release notes for what was fixed in GOS 5.2.056 SP1 service pack. The major fixes were related to lgdom with users not able to log onto the Web Ui page as well as better Domain compatibility with Windows 2008 and Windows7.


There you have it, from the source.