!!! Limber
[{$pagename}] [EDirectory Background Processes] is responsible with maintaining [NDS] Tree connectivity and periodically, each [NcpServer] in the NDS tree checks and verifies that it still knows the correct tree name. 


[{$pagename}] is the process that performs Agent [Configuration] [Synchronization]. [{$pagename}] (may also be referred to as Connectivity Check) may trigger other processes to refresh their configuration (i.e. [LDAP], etc.) 

[{$pagename}] is scheduled to run every 4 hours by default, which is configurable in [NDS] [Imonitor]. [{$pagename}] will also run when requested or when a change is noticed that needs to be synchronized.

[{$pagename}] check is executed when the [NcpServer] boots, when the [NDS] processes are restarted and when the server receives a specific [{$pagename}] request from another [NcpServer].

[{$pagename}] process typically runs when a tree name changes or with [IP] or [IPX] address changes. A [NcpServer] holding the Master [NDS Partition] needs to send out the request. Additionally, the Limber process will run when the Master [NDS Partition] of a server receives change information from another [NcpServer]/partition on the NDS tree.

After questioning several sources, it is still unclear to me why this process is named [{$pagename}], so that will remain a mystery for now. However, naming issues aside, [{$pagename}] is an [EDirectory Background Processes] that is responsible for
* Making sure that the [eDirectory] referral information for this server is properly maintained in each [partition] hosted on this [NcpServer].
* Making sure that the [NcpServer] hosting the Master [replica] of the [partition] in which the Server object for this [NcpServer] resides has the correct [Relative Distinguished Name] ([RDN]) for this server. 
* Making sure the server object in [eDirectory] correctly reflects the [Operating System] [version] and [NetworkAddress] in use on this server.
* Making sure the name of the [eDirectory] tree in which this server resides is correctly reported.
* Monitoring the [NDS External References]/[DRL] links between this server and the [partition] replica that holds this server's [eDirectory] Server object. This is done to make sure that the [eDirectory] server can be properly accessed via its eDirectory object.
* Making sure this server's identification information is correct.

[{$pagename}] can be monitored indirectly through 
* [Ndsrepair] using the Check External Reference, Report Synchronization Status, and Replica Ring repair options. 
* [Ndstrace] ([LMBR] Flag) also provides the ability to monitor Limber directly.

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]