Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SocketRPC: ensure pipe paths match up. #3066

Merged
merged 1 commit into from May 7, 2017

Conversation

@kylewickens
Copy link
Contributor

commented May 4, 2017

Cross-compiled the latest mumble to run on the Raspberry Pi 3 specifically to use the RPC calls and discovered that none of them worked. Tracked the problem down to the creation of the the pipepath in the client send method. The pipepath didn't match the pipepath created for the server SocketRPC::SocketRPC.

@mkrautz

This comment has been minimized.

Copy link
Member

commented May 7, 2017

This is a copy/paste of the socket path code from the SocketRPC::SocketRPC constructor.
It looks good to me.

@mkrautz
mkrautz approved these changes May 7, 2017

@mkrautz mkrautz changed the title FIXED: RPC calls to run on a Raspberry Pi SocketRPC: ensure pipe paths match up. May 7, 2017

@mkrautz mkrautz merged commit a6aba12 into mumble-voip:master May 7, 2017

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.