LDAP connection pooling?

[James Mills <James.Mills@tenzing.com>]

All,

I have LDAP working as a central authentication server, and it is
working fine.  However, I notice that for every process I run as an LDAP
authenticated user, it opens a connection between the workstation and
the main LDAP server.  Here is an example (NOTE: ts-file02 is the main
LDAP server, and overland is my desktop):
.
.
.
bash      5731 jmills    3u  IPv4   5227       TCP
overland.seattle.tenzing.com:1223->ts-file02.seattle.tenzing.com:389
(ESTABLISHED)
startx    5740 jmills    3u  IPv4   5227       TCP
overland.seattle.tenzing.com:1223->ts-file02.seattle.tenzing.com:389
(ESTABLISHED)
xinit     5747 jmills    3u  IPv4   5227       TCP
overland.seattle.tenzing.com:1223->ts-file02.seattle.tenzing.com:389
(ESTABLISHED)
XFree86   5748   root    3u  IPv4   5227       TCP
overland.seattle.tenzing.com:1223->ts-file02.seattle.tenzing.com:389
(ESTABLISHED)
WindowMak 5751 jmills    3u  IPv4   5227       TCP
overland.seattle.tenzing.com:1223->ts-file02.seattle.tenzing.com:389
(ESTABLISHED)
xscreensa 5753 jmills    3u  IPv4   5227       TCP
overland.seattle.tenzing.com:1223->ts-file02.seattle.tenzing.com:389
(ESTABLISHED)
xscreensa 5753 jmills    4u  IPv4   5272       TCP
overland.seattle.tenzing.com:1232->ts-file02.seattle.tenzing.com:389
(ESTABLISHED)
.
.
.
lsof -i -P|grep ts-file02|wc -l
99


Is there a method of pooling these connections, maybe one per session or
one per uid?

Thanks,
James Mills

-- 
______________________________________________________________
"I was gratified to be able to answer promptly, and I did. 
I said I didn't know."
~Mark Twain