[Bug 806761] Re: Feature Request: Upstart scripts for nslcd

[Caleb Callaway]

I'm assuming the lack of comments indicates that there are no violent
objections to the path I'm taking. The current revision has been working
quite well on my system, as well as a testbed VM. So, I'm re-subscribing
ubuntu-sponsors and attaching the revised patch.

Overview of changes:

-changed "start on" condition to start once at runlevels [23456], and added a if-up.d script to signal nslcd to start whenever an interface comes up
-took advantage of Upstart's built-in log facilities; removed redundant "starting..." messages.
-check state of job in post-start loop
-use "stop; exit 0" instead of "exit 1"
-removed unused env stanzas
-use install -d instead of mkdir+chown

What hasn't changed:

-The scripts still use an /etc/defaults file--I know of no way to do expansion with env variables, which is a requirement for several default values.
-Logging of diangostic information when the job terminates because of an improperly configured environment (e.g. missing binaries)

** Patch added: "Upstart script patch, rev 4"
   https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+attachment/3240212/+files/nslcd-upstart.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/806761

Title:
  Feature Request: Upstart scripts for nslcd

Status in “nss-pam-ldapd” package in Ubuntu:
  In Progress

Bug description:
  This forum thread contains Upstart scripts that makes nslcd (and by
  extension the whole nss-pam-ldapd package) more resilient in the face
  of network connectivity outages:
  http://ubuntuforums.org/showthread.php?t=1335022

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/806761/+subscriptions