sobby does not appear to use socket reuse flags
Bug #306955 reported by
Chris Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
net6 |
New
|
Undecided
|
Unassigned | ||
obby |
New
|
Undecided
|
Unassigned | ||
libinfinity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Won't Fix
|
Undecided
|
Unassigned | ||
Karmic |
Won't Fix
|
Undecided
|
Unassigned | ||
net6 (Ubuntu) |
Fix Released
|
Medium
|
Philipp Kern | ||
Hardy |
Won't Fix
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
Medium
|
Philipp Kern |
Bug Description
Binary package hint: sobby
Restarting sobby can produce the following (from strace output):
bind(4, {sa_family=AF_INET, sin_port=
The server is not running, but the socket will be in TIME_WAIT or similar, so sobby should specify the appropriate REUSE option when it creates its listening socket, allowing for instant restarts.
Related branches
Changed in sobby (Ubuntu): | |
assignee: | nobody → Philipp Kern (pkern) |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in net6 (Ubuntu Hardy): | |
assignee: | nobody → Philipp Kern (pkern) |
status: | New → Incomplete |
Changed in net6 (Ubuntu Hardy): | |
assignee: | Philipp Kern (pkern) → nobody |
tags: | added: patch |
To post a comment you must log in.
In theory that's a security measure and it should not happen if sobby is SIGTERM'ed (i.e. if the socket is closed cleanly), or does it?