hi, thanks for your replyThat's what I thought too, but it's definitely not that. Below some commands I run once Debian is up and running, and once I'm already logged in :
# /etc/init.d/slapd startStarting OpenLDAP: slapd (just to check that my init.d/slapd script works)
# /etc/init.d/slapd stop Stopping OpenLDAP: slapd # service slapd startStarting OpenLDAP: failed ==> so I'm unable to run slapd with service
# /etc/init.d/slapd Starting OpenLDAP: slapd # service slapd stopStopping OpenLDAP: slapd ==> but it can be stopped with service
I can start slapd with my init.d script, but I'm unable to start it with the service command
Le 26/01/2013 01:19, berenger.morel@neutralite.org a écrit :
Le 25.01.2013 23:16, Benin Technologies a écrit :Hi, Running Debian 6.0.4 Does anybody have an idea why a program wouldn't start at boot, while it's init.d script works fine ?I experience the problem with OpenLDAP 2.4.33, when compiled with back-sql :/etc/init.d/slapd start WORKS FINE # update rc.d slapd defaults At boot, I got "Starting OpenLDAP: slapd failed!"Maybe init try to start slapd when one of it's dependencies is not started yet? I think you can check that by looking into /etc/rc.X, where X is your current runlevel. IIRC, having a "file" (a symlink in fact) named with K means disabled, and S means enable. The file name represent the priority.I might be totally wrong, so please wait for confirmation or do some researches about init before playing with that stuff ;)