oidentd doesn't have a status option in the init script
Bug #886427 reported by
William Van Hevelingen
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| oidentd (Debian) |
Fix Released
|
Unknown
|
|||
| oidentd (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Bug Description
oidentd doesn't have a status option in the init script
| Changed in oidentd (Ubuntu): | |
| status: | New → Confirmed |
| Changed in oidentd (Ubuntu): | |
| importance: | Undecided → Low |
| status: | Confirmed → Triaged |
| Changed in oidentd (Debian): | |
| status: | Unknown → New |
| Changed in oidentd (Debian): | |
| status: | New → Fix Committed |
Revision history for this message
| Peter Waller (peter.waller) wrote | #1 |
| Changed in oidentd (Debian): | |
| status: | Fix Committed → Fix Released |
| Changed in oidentd (Ubuntu): | |
| status: | Triaged → Fix Committed |
| Changed in oidentd (Ubuntu): | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Any chance of this fix finding its way into Ubuntu? It's causing some configuration managers to think that oidentd always needs to be restarted because `status` always returns a non-zero exit status.