-
Notifications
You must be signed in to change notification settings - Fork 48
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
Documentation issue: FIFO access on modern linux & opensips-cli / mi_fifo defaults #114
Comments
Seems like there's something else going on here as well where documentation says to use a |
Hey, @Igneous! Thanks for the feedback, I agree that if the Regarding the |
Yeah absolutely. I'll shoot you a PR sometime in the next couple days -- it'd be an exciting privilege to contribute to osips |
Just wanted to detail my first experience here -- there's a chance this can be improved.
Seems like most docs and defaults throughout the codebase refer to using /tmp/opensips_fifo. It's very easy to accidentally set everything up using /tmp/opensips_fifo.
Running
opensips-cli
with a module likeuser
will give unrelated errors about not being loaded, however if you're fortunate enough to use the-d
flag, you can see it's not being loaded because the cli can't access the mi fifo... but it's unclear why opensips-cli can't access it.Executing a command with the
mi
module seems to be the only codepath that will print this warning:This is hugely valuable -- put this everywhere anytime you fail to open the fifo. Also update the docs / config examples!
I'm happy to try to contribute changes to this if you're too busy and want a PR.
The text was updated successfully, but these errors were encountered: