On 31/03/11 14:29 +0100, Markus Moj wrote:
So what do you mean by specify a gid? This is not a self scripted init script this one is 100% Red Hat we have changed nothing within the start script.
Redhat may not, but it's not uncommon for other OSs to do so.
I'm assuming that the error message you are seeing is permissions related, possibly due to the fact that slapd is running under a different effective gid when you start it from the command line versus when you start it from an init script.
One way to trouble shoot that is to explicitly specify a gid (-g) from your init script and your command line.
Hi, Could it be due to SELinux enforcing?
Could you check with "getenforce" command to see if this is the case? If so, could you check your /var/log/audit/auth.log (or similar) and tell if you see something wrong in it?
M.
On Thu, Mar 31, 2011 at 4:08 PM, Dan White dwhite@olp.net wrote:
On 31/03/11 14:29 +0100, Markus Moj wrote:
So what do you mean by specify a gid? This is not a self scripted init script this one is 100% Red Hat we have changed nothing within the start script.
Redhat may not, but it's not uncommon for other OSs to do so.
I'm assuming that the error message you are seeing is permissions related, possibly due to the fact that slapd is running under a different effective gid when you start it from the command line versus when you start it from an init script.
One way to trouble shoot that is to explicitly specify a gid (-g) from your init script and your command line.
-- Dan White
openldap-technical@openldap.org