Is there any technical reason nslcd can't have a foreground mode? I'm happy
to dive into the code and see about making the necessary modifications, but
I wouldn't want to invest the time unless it's a feasible option.
On Thu, Aug 15, 2013 at 1:04 AM, Arthur de Jong <email address hidden> wrote:
> Currently nslcd does not support not forking into the background outside
> of debug mode.
>
> The pid of nslcd can be reliably determined by looking at
> /var/run/nslcd/nslcd.pid.
>
> --
> 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
>
Good to know about the PID file, but as far as I know, there is no /lists. ubuntu. com/archives/ upstart- devel/2008- August/ 000735. html(the
mechanism in Upstart for utilizing PID files. This is an intentional design
decision, see
https:/
section on the "pid file" stanza being removed)
Is there any technical reason nslcd can't have a foreground mode? I'm happy
to dive into the code and see about making the necessary modifications, but
I wouldn't want to invest the time unless it's a feasible option.
On Thu, Aug 15, 2013 at 1:04 AM, Arthur de Jong <email address hidden> wrote:
> Currently nslcd does not support not forking into the background outside nslcd/nslcd. pid. /bugs.launchpad .net/bugs/ 806761 /bugs.launchpad .net/ubuntu/ +source/ nss-pam- ldapd/+ bug/806761/ +subscriptions
> of debug mode.
>
> The pid of nslcd can be reliably determined by looking at
> /var/run/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Feature Request: Upstart scripts for nslcd
>
> To manage notifications about this bug go to:
>
> https:/
>