fwknop-server needs upstart support
Bug #1051958 reported by
Christian Kampka
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| fwknop (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
The fwknop package can benefit greatly from upstart supervision.
First of it is generally deployed as a single point of failure with the side effect that a failing fwknopd will probably leave the machine unmanageable by eg. ssh. Second, the current 2.x release is fairly new and rewritten in another language (ported from Perl to C) and it's stability is not as proven as the older 1.x line.
Because of that, having upstart supervise the fwknopd process ("respawn") will provide at least ease of mind if not significantly reduce maintenance problems.
Related branches
lp:~kampka/ubuntu/quantal/fwknop/upstart-support
- Dimitri John Ledkov: Approve
- James Page: Needs Fixing
- Oliver Grawert: Needs Information
- Ubuntu branches: Pending requested
-
Diff: 58 lines (+39/-0) (has conflicts)2 files modifieddebian/changelog (+9/-0)
debian/fwknop-server.upstart (+30/-0)
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in fwknop (Ubuntu): | |
| status: | New → Fix Released |
To post a comment you must log in.
This bug was fixed in the package fwknop - 2.0.3-2ubuntu1
---------------
fwknop (2.0.3-2ubuntu1) raring; urgency=low
* Add upstart support. (LP: #1051958)
-- Christian Kampka <email address hidden> Mon, 17 Sep 2012 15:11:15 +0200