w2ksetup(8) [osf1 man page]

w2ksetup(8)						      System Manager's Manual						       w2ksetup(8)

NAME

       w2ksetup - Setup script for Windows 2000 Single Sign On

SYNOPSIS

       /usr/sbin/w2ksetup

DESCRIPTION

       Use  the  w2ksetup  script  to configure the Windows 2000 Single Sign On (SSO) after you install the optional software subsets. To use this
       script, you must have access to a Windows 2000 account that is a member of the Administrators group, but is not the  default  Administrator
       account. If no such account exists, you may need to create one before running the setup script.

       The  script  prompts  you  to enter the following information: A domain name, such as sso.w2k.com. Typically this is the same as the domain
       name server (DNS) domain.  The host name of the Windows 2000 domain controller, such as 2millen.sso.w2k.com

SEE ALSO

       Commands: ldapcd(8)

       Files: ldapcd.conf(4)

																       w2ksetup(8)

ldapcd.conf(4)						     Kernel Interfaces Manual						    ldapcd.conf(4)

NAME

       ldapcd.conf - Configuration file for the single sign-on daemon.

SYNOPSIS

       # comment_string parameter: integer identifier: string identifier: "quoted_string,quoted_string,..."

DESCRIPTION

       The  ldapcd.conf file stores the current configuration of the Windows 2000 Single Sign-on daemon (SSO).	The information stored in the file
       is specified when you configure Windows 2000 Single Sign-on and is not normally changed.

       The ldapcd.conf file also contains the default operating parameters for the daemon which you can tune for performance.  You might  need	to
       tune performance if users wait a long period of time for the UNIX server system to respond.

       To tune the Windows 2000 SSO software, use a text editor to modify the values of the caching parameters as follows: The number of open con-
       nections that the caching daemon makes to the active directory.	Increasing the value of this entry opens more connections  to  the  active
       directory,  however  this  consumes more file descriptors and increases the load on the active directory. Typically, 4 connections are ade-
       quate for a workstation and 15 connections are adequate for a server.

	      Default: 4 connections The maximum number of user entries to store in cache.  Increase or decrease this value as the maximum  number
	      of users increases or decreases.

	      Default:	500  entries  The  maximum number of seconds to cache a user entry.  Increasing this value increases performance because a
	      user's entry is readily available in the cache. If you delete a recently used user account, its entry remains in the cache  for  the
	      amount of time specified by this parameter.

	      Default:	900  seconds.  The maximum number of group IDs to cache. Increasing this value increases performance because group IDs are
	      readily available in the cache.

	      Default: 100 group IDs The maximum number of seconds to cache group IDs.

	      Default: 900 seconds

   Using a Revised Configuration
       If you change the value of a cache parameter in the /etc/ldapcd.conf file, you must enter the following command to read the new	configura-
       tion and restart the daemon: # /sbin/init.d/ldapw2k restart

EXAMPLES

       The  following  example	shows  a  typical  configuration  file:  #  connections: 4 pw_cachesize: 500 pw_expirecache: 900 gr_cachesize: 100
       gr_expirecache: 900

       usesasl: 1

       directory: server1 searchbase:  "cn=users,DC=SSO,DC=TWOTEN,DC=COM"  machine_acctname:  emera.ggg.bbb.com  machine_dn:  "cn=emera,cn=comput-
       ers,DC=SSO,DC=TWOTEN,DC=COM"

FILES

       Location of the file.

RELATED INFORMATION

       Commands: ldapcd(8), lw2ksetup(8)

       Windows 2000 Single Sign-On Installation and Administration Guide.  delim off

																    ldapcd.conf(4)