firebird 2.0 doesn't create /var/run/firebird/2.0 entry at startup
Bug #135582 reported by
Almad
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firebird (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
firebird2.0 (Debian) |
Fix Released
|
Undecided
|
Damyan Ivanov | ||
firebird2.0 (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
After installation and configuration, package for Firebird 2.0 on Kubuntu Gutsy is not creating directory in /var/run/
Solved by creating dir and starting fbmanager manually.
Changed in firebird2.0: | |
status: | Confirmed → In Progress |
Changed in firebird2.0: | |
assignee: | mapopa → nobody |
Changed in firebird: | |
status: | New → Fix Committed |
Changed in firebird: | |
status: | Fix Committed → Invalid |
Changed in firebird2.0: | |
status: | New → Confirmed |
status: | Confirmed → In Progress |
Changed in firebird2.0: | |
status: | In Progress → Fix Committed |
Changed in firebird2.0: | |
assignee: | nobody → dam-modsoftsys |
assignee: | dam-modsoftsys → dmn-debian |
summary: |
- [gutsy] firebird 2.0 doesn't create /var/run/firebird/2.0 entry at - startup + firebird 2.0 doesn't create /var/run/firebird/2.0 entry at startup |
To post a comment you must log in.
The same is true for the firebird1. 5-super- package.
As the reporter states I have to create the directory manually for getting firebird to start, like this e.g.:
sudo mkdir -p /var/run/ firebird/ 1.5 firebird/ 1.5 -R
sudo chown firebird.firebird /var/run/
IIRC already dapper suffered of this bug.
I am slightly disappointed of Ubuntu's QA, especially because servers are also a targeted area.