-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Hardcoded Redis socket path #51
Comments
This is the workaround I'm currently using; I'm binary patching syncd, libsairedis etc. with this sed snippet: |
(NB: link-to-redis-socket.sock is the exact same length as the original string) |
I think the problem is still not solved. DEFAULT_UNIXSOCKET |
Agree. I will work on it later. |
…t-doc Add details about D-Bus architecture (container to host).
Hi,
While working on a SONiC snap, I hit the hardcoded path to the Redis unix socket. It's defined in header files at build time and ends up in a number of daemons (syncd etc.) and libs (libsairedis). This makes it impractical to relocate SONiC, to have multiple versions of it on the same box or to integrate into a different FS layout.
It would be nice to have a runtime override for the path, either an environment variable (SONIC_REDIS_URL?) or a command-line flag that would have to be passed to each program using Redis (--redis-url).
Thanks,
-- Loïc Minier
The text was updated successfully, but these errors were encountered: