doc: improve documentation for "ing" events

Reported by Mark Russell on 2011-02-11
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
upstart
Wishlist
Unassigned

Bug Description

Example:

Centrify Suite's ActiveDirectory to NIS gateway needs to be started before other services that need its user authentication services. Meaning adnisd and centrifydc services need to start before cron, at, nis, nfs, and autofs.

Mark Russell (marrusl) wrote :

This was made to work eventually but only by modifying several other Upstart jobs, as well as using Upstart jobs for NIS taken from bug 569757

I've attached the entire /etc/init folder from the system that is now starting up properly. The jobs that were modified include: cron.conf, atd.conf, autofs.conf, statd.conf, portmap-boot.conf (need to double check this list).

nis scripts:
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/1423483/+files/ypbind.conf
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/1423484/+files/yppasswdd.conf
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/1423485/+files/ypserv.conf
https://bugs.launchpad.net/ubuntu/+source/nis/+bug/569757/+attachment/1423486/+files/ypxfrd.conf

Clint Byrum (clint-fewbar) wrote :

Hi Mark,

It appears most of this was taken from bug #569757 . I've commented quite a bit there, and stated that for a Stable Release Update, it may be too invasive to convert the whole of NIS to upstart completely, but that we must do so going forward for NIS to function properly.

Mark Russell (marrusl) on 2011-02-17
summary: - can't map centrifydc and adnisd reverse dependencies
+ docs: unclear how 3rd party vendors can insert upstart jobs that block
+ system services
description: updated

Yes, I don't want bug 569757 to distract from the primary issue. Let's leave NIS aside.

It seems that if there is only one system service you need to start before this can be done easily, but it is unclear how to make sure you start before, say, several services as in the example.

If you need to start before just cron, "start on starting cron" will work. But "start on (starting cron or starting autofs or starting atd)" has the strong possibility of racing.

Clint Byrum (clint-fewbar) wrote :

Indeed, because of the way upstart works, you need an intermediary job to block all of those until your job is started.

Consequently, socket activation should make this a lot easier in the future.

For now, we plan to document the "wait job" technique more cleanly, and provide the wait-for-state job to implement it in a generic sense.

Changed in upstart:
status: New → Triaged
importance: Undecided → Wishlist
summary: - docs: unclear how 3rd party vendors can insert upstart jobs that block
- system services
+ doc: improve documentation for "ing" events
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments