Comment 43 for bug 806761

I'd agree that "expect fork" looks like the correct approach, and until the
latest release, using that stanza seemed to work without issue.

It's true that adding functionality to accommodate a service management
system is a poor separation of concerns, but nslcd's generation of a PID
file does establish a precedent for doing so, as does other daemons' use of
the -n switch. it seems making this sort of compromises is a fairly common
practice.

Ultimately, though, I'm just trying to follow the path of least resistance
to my goal of making it painless to have mobile access to LDAP account
information. No custom scripts, no PPAs, no service restarts when I boot up
my laptop and have to manually establish a wireless connection in a coffee
shop. Right now, adding a -n switch to nslcd seems like the next step
forward on that path.

On Sat, Aug 17, 2013 at 2:33 PM, Arthur de Jong <email address hidden> wrote:

> According to the mailing list post you would expect that "expect fork"
> should be the right thing to do.
>
> If you really want to implement a command-line switch for this (I think
> it is a bit silly to have to do this for upstart), please name it -n
> (this seems to be used by a few daemons that provide such an option).
> The change itself shouldn't be too complicated.
>
> --
> 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
>