The server-side use of $MIR_SOCKET is confusing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
Medium
|
Alan Griffiths | ||
mir (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
What we have now is that $MIR_SOCKET is set in DefaultServerCo
In fact, in the "no-file" case there's no globally correct value for the socket name - a value needs to be provided for each client.
When starting up DefaultConfigur
Related branches
- Cemil Azizoglu (community): Approve
- Kevin DuBois (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Mir CI Bot: Needs Fixing (continuous-integration)
-
Diff: 16 lines (+0/-7)1 file modifiedsrc/platform/options/default_configuration.cpp (+0/-7)
- PS Jenkins bot (community): Approve (continuous-integration)
- Mir CI Bot: Approve (continuous-integration)
- Kevin DuBois (community): Approve
- Cemil Azizoglu (community): Approve
-
Diff: 98 lines (+35/-7)3 files modifiedexamples/server_example.cpp (+24/-2)
examples/server_example_test_client.cpp (+11/-0)
src/server/default_server_configuration.cpp (+0/-5)
Changed in mir: | |
importance: | Undecided → Medium |
Changed in mir: | |
assignee: | nobody → Alan Griffiths (alan-griffiths) |
status: | New → In Progress |
Changed in mir: | |
milestone: | none → 0.21.0 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.21.0