Comment 39 for bug 806761

Hi Arther,

Good to know. I think the behavior I'm seeing is most likely a result of
some change to Upstart, because I'm using the same modified 0.8.10-1
package that I've used in the past. Even so, the process ID that Upstart
decides to track is very definitely incorrect whether I track the first or
second call to fork(). I'm running `ps auxw | grep nslcd` to verify the PID.

Running in the foreground is the only way Upstart will reliably select the
correct process ID. This is true for both my main workstation and a
virtualized testbed. Is there some way to run nslcd in the foreground
without enabling debug mode?

On Wed, Aug 14, 2013 at 3:58 AM, Arthur de Jong <email address hidden> wrote:

> It is not recommended to run nslcd in debug mode in production.
>
> Anyway, on start-up nslcd will call daemon() to daemonise. I thought
> that daemon() called fork() twice but according to the manual page it
> only forks once. After that, it starts a number of threads (configured
> by the threads option in nslcd.conf) and optionally starts another sub-
> process to do cache invalidation. This last process is only started in
> 0.9.0 and later if configured and is started before dropping privileges
> so runs as root (while other processes commonly run as user nslcd).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/806761
>
> Title:
> Feature Request: Upstart scripts for nslcd
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+subscriptions
>