Hi, The first of the init scripts, here: http://directory.fedora.redhat.com/wiki/Howto:SysVInit (URL to script: http://www.directory.fedora.redhat.com/download/FedoraDirectoryServer-init.d) ... does not start the Fedora Directory Server on boot if the system ulimit has been changed before the installation of FDS. If FDS detects a higher ulimit then it will write: (e.g.) nsslapd-maxdescriptors: 8192 to: /opt/fedora-ds/slapd-(servername)/config/dse.ldif So that when the script above is run during bootup, the following message will be generated in the logs, and FDS won't start: dse - The entry cn=config in file /opt/fedora-ds/slapd-fc3-dbw-1/config/dse.ldif is invalid, error code 53 (DSA is unwilling to perform) - nsslapd-maxdescriptors: invalid value 8192, maximum file descriptors must range from 1 to 1024 (the current process limit) To fix this, insert the string: ulimit -n 8192 ... somewhere near the top of the script. e.g.: myName=`basename $0` fdsRoot="/opt/fedora-ds" ulimit -n 8192 This problem is likely to be caused because the /opt/fedora-ds/setup/setup script emits the following messages if it detects a low ulimit: WARNING: There are only 1024 file descriptors (hard limit) available, which limit the number of simultaneous connections. WARNING: There are only 1024 file descriptors (soft limit) available, which limit the number of simultaneous connections. Changing the ulimit to 8192 in /etc/security/limits.conf makes the above setup problem go away but then causes the startup script to fail. -- Del -- Fedora-directory-users mailing list Fedora-directory-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
