Merge lp:~jameinel/launchpad/lp-service into lp:launchpad/db-devel
Status: | Superseded |
---|---|
Proposed branch: | lp:~jameinel/launchpad/lp-service |
Merge into: | lp:launchpad/db-devel |
Diff against target: |
273 lines (+194/-11) 2 files modified
bzrplugins/lpserve/__init__.py (+53/-1) bzrplugins/lpserve/test_lpserve.py (+141/-10) |
To merge this branch: | bzr merge lp:~jameinel/launchpad/lp-service |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Michael Hudson-Doyle | Approve | ||
Launchpad code reviewers | Pending | ||
Review via email: mp+40386@code.launchpad.net |
This proposal has been superseded by a proposal from 2010-11-29.
Commit message
Add '--pid-file' to launchpad-
Description of the change
This adds a --pid-file option to "bzr launchpad-
This was brought out of the discussion of trying to get the service rolled out into qastaging.
see https:/
It would seem that 'start-stop-daemon' could be told to do the forking and pid-file management (--background and --make-pidfile), but it seems to state that "This is a last resort, and is only meant for programs that either make no sense forking on their own, or where it's not feasible to add the code for them to do this themselves."
The change seems reasonably localized, and hopefully reasonably tested. In general with IPC, I'm not always sure how to avoid both race conditions, hangs, and spurious failures. I chose 2.0s as a way to wait for the process to cleanup properly, but not block forever and hang the test suite.
Note that I still need some reviewer hand-holding to submit this to ec2, etc.