Error in slapd init script from blfs-bootscript

[Tim Tassonis]

Hi all

I found a little error in the slapd init script from blfs-bootscripts: I requests a start in runlevel 2 and at the same time requests $network

$network however is not present in runlevel 2

install_initd from initd-tools rightly complains about this, I would not have notices otherwise...

The following fix makes everything fine:

< 19c18 < # Default-Start: 2 3 4 5 ---

# Default-Start: 3 4 5

[Tim Tassonis]

I just found another error, when installing on another machine:

The script also requests $remote_fs, which may not be present and definitely is no sane requirement for an ldap server.

[bdubbs@…]

I understand what you are saying, but how are you using it? We really don't use the the commented section:

### BEGIN INIT INFO
# Provides:          slapd
# Required-Start:    $remote_fs $network $syslog
# Required-Stop:     $remote_fs $network $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: OpenLDAP standalone server
# X-LFS-Provided-By: BLFS
### END INIT INFO

It is intended for other utilities not in LFS/BLFS

[Tim Tassonis]

In BLFS, Chapter 12. System Utilities, there are the initd-tools. I installed them and quite like them, as they care for all the rc*.d symlinks and do it very nicely.

They install two programs install_initd and remove_initd, which will set all the right symlinks in the right directory and orders them correctly based on the dependencies.

As it works so well with most blfs-bootscripts, I thought others use them as well and regarded this init scripts as buggy.

[bdubbs@…]

OK. I'll try to address it.

[Tim Tassonis]

Just as an info: removing the 2 from Default-Start: and removing both instances of $remote_fs will fix it.

[bdubbs@…]

Fixed at revision 17722.