Merge lp:~clint-fewbar/ubuntu/natty/portmap/new-boot-events into lp:ubuntu/natty/portmap
Proposed by
Clint Byrum
Status: | Merged | ||||
---|---|---|---|---|---|
Merged at revision: | 15 | ||||
Proposed branch: | lp:~clint-fewbar/ubuntu/natty/portmap/new-boot-events | ||||
Merge into: | lp:ubuntu/natty/portmap | ||||
Diff against target: |
94 lines (+52/-3) 5 files modified
debian/changelog (+12/-0) debian/portmap.portmap-boot.upstart (+10/-0) debian/portmap.portmap-wait.upstart (+22/-0) debian/portmap.portmap.upstart (+5/-2) debian/rules (+3/-1) |
||||
To merge this branch: | bzr merge lp:~clint-fewbar/ubuntu/natty/portmap/new-boot-events | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Steve Langasek | Needs Fixing | ||
Review via email: mp+45292@code.launchpad.net |
Description of the change
This changes the way portmap is started on bootup so that it includes the ON_BOOT=y flag, which is needed to satisfy statd's very specific startup needs. It also adds the 'portmap-wait' job that allows starting and/or waiting on portmap to startup without using its started event.
To post a comment you must log in.
On Wed, Jan 05, 2011 at 08:44:10PM -0000, Clint Byrum wrote: portmap. portmap. upstart' portmap. portmap. upstart 2011-01-05 20:44:09 +0000 filesystems
> === renamed file 'debian/upstart' => 'debian/
> --- debian/upstart 2010-04-17 01:42:21 +0000
> +++ debian/
> @@ -7,8 +7,8 @@
> description "RPC port mapper"
> author "Steve Langasek <email address hidden>"
>
> -start on (virtual-
> - and net-device-up IFACE=lo)
> +# Note that portmap is started by portmap-boot.conf and so intentionally
> +# has no start on
>
> expect fork
> respawn
>
The previous job had 'and net-device-up IFACE=lo' as a start condition, but
this has been dropped from the new portmap-boot job without explanation.
Have you confirmed that the interface doesn't need to be up for portmap to
start successfully? If not, this condition should be reintroduced.
Please wrap changelog entries at 80 characters - you should find that
lintian reports an error for over-long changelog lines here.
-- www.debian. org/
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://
<email address hidden> <email address hidden>